Idp Oracle
Idp Oracle
Idp Oracle
protect the data stored in Oracle databases. Data Protection for Oracle performs online or offline
backups of Oracle 11g databases to Tivoli Storage Manager server storage. This TDP for Oracle
is integrated with the RMAN Media Management API and maximizes the protection of data, thus
providing a comprehensive storage management solution. Data Protection for Oracle interfaces
with the Oracle Recovery Manager (RMAN) to send backup versions of Oracle databases to the
Tivoli
Storage
Manager
server.
Databases
Tablespaces
Datafiles
Control files
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.
Prerequisites for using IBM Tivoli Data Protection For Oracle 6.3
To use this TDP Oracle you should also install supporting Tivoli Storage Manager API
Version. The required version of the Tivoli Storage Manager API is included in the Data
Protection for Oracle product media.
Existing backups created using previous versions of Data Protection for Oracle are
restorable using Data Protection for Oracle 6.3.
Backups created with Data Protection for Oracle 6.3 cannot be restored using previous
versions of Data Protection for Oracle.
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.
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.
A user with administrative authority must install Data Protection for Oracle on a Windows
server where the target database resides.
If Data Protection for Oracle was not previously installed on your system, you can install
Data Protection for Oracle into the Tivoli Storage Manager base directory of your choice.
On Windows Data Protection for Oracle 32-bit installs to the \AgentOBA directory and
Data Protection for Oracle 64-bit installs to the \AgentOBA64 directory under this base
default directory.
On Unix, Data Protection for Oracle 32-bit installs to the /oracle/bin directory and Data
Protection for Oracle 64-bit installs to the /oracle/bin64 directory under this base default
directory
A new query command is available to query information about backed up files With
the tdposync query command, you can query the Tivoli Storage Manager server for
information about database objects that have been backed up. You can obtain statistics
that indicate whether a backup object was encrypted, compressed, or deduplicated.
The tdposync utility can work with backup history information in the Oracle control file.
The tdposync syncdb command can use the backup history information stored in the
Oracle control file to synchronize the Tivoli Storage Manager database with the Oracle
Recovery Manager (RMAN) backup history. Synchronization can be done with either a
control file or the Oracle catalog.
Use the send command to send additional parameters to the Tivoli Storage Manager
API.
You can use the Oracle RMAN send command in an RMAN script to specify any
supported Tivoli Storage Manager options, such as TCPport and TCPServeraddress, to
the Tivoli Storage Manager API. Any option that is sent by using the send command
takes precedence over the option specified in the options files for Data Protection for
Oracle or Tivoli Storage Manager API.
UTF-8 is added for the language locales that are already supported by Data Protection
for Oracle.
The Data Protection for Oracle Version 6.3 message catalogs are encoded in UTF-8. If
you are installing the Data Protection for Oracle message catalogs for languages other
than English, you must also have the appropriate iconv UTF-8 converters installed on
your system. If the appropriate iconv UTF-8 converters are not installed, all Data
Protection for Oracle messages are displayed in English.
Tivoli Data Protection for Oracle is not upgraded to version 6.4 but upgraded to version 7.1. To
know the software and hardware requirements of TDP for Oracle version 7.1 visit this link
- See more at: http://www.tsmtutorials.com/2013/11/what-is-the-use-of-TDP-oforacle.html#sthash.MSMllsA3.dpuf
Before installing IBM Tivoli Data Protection for Oracle on Windows or Unix systems make sure
you meet the required Software and Hardware Requirements. In this post we will see the
Hardware and Software Requirements for installing TDP for Oracle and Installation procedures.
Supported Oracle Database levels
Any Tivoli Storage Manager server in support that is compatible with the Tivoli Storage
Manager API used in your environment.
For Linux x86, Tivoli Storage Manager API Version 6.2.2, and later mod levels and fix
packs.
For all other UNIX and Linux platforms, either of the following Tivoli Storage Manager API
versions
Tivoli Storage Manager API Version 6.2.2, and later mod levels and fix packs
Tivoli Storage Manager API Version 6.3.0, and later mod levels and fix packs
TCP/IP
Shared memory
Data Protection for Oracle and the Tivoli Storage Manager server must be installed on the same
machine in order for shared memory to work. Use TCP/IP as the following communication
method for Linux on x86, Linux x86_64 and Linux on System z
Virtualization Environment Requirements
For requirements installing TDP for Oracle on Virtualization Environments check this IBM
document.
IBM system p OR
IBM system i OR any compatible hardware supported by the operating system and
Oracle.
A minimum of 25MB of disk space, and optionally at least 15MB of disk space for each
Language Pack to be installed (there are a total of 13 available).
By using SMITTY INSTALLP command select and highlight all the Data Protection for
Oracle supported packages including License Agreement and press F7.
tivoli.tsm.client.oracle.aix.64bit
tivoli.tsm.client.oracle.tools.aix.64bit
tivoli.tsm.client.api.aix.64bit
tivoli.tsm.client.oracle.msg.aix.64bit.xx_XX
tivoli.tsm.loc.client.oracle.aix.64bit.ela
In Install and Update from LATEST Available Software window, press ENTER.
Software Requirements
Set the appropriate permission to the directory where the software package
is located.
chmod 755 /setupfiles
Issue this command to install the Tivoli Storage Manager API. The default language is
English.
$ swinstall -v -s /setupfiles/oracle/hpuxia/api/TIVsmCapi64
Now change to the TDPO installable directory and 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
If the installable file was downloaded from the FTP site, the filename might be different than
TDPOracle64.bin.
If you want to install Data Protection for Oracle in a language other than 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
$ 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.
A minimum of 80MB of disk space, and optionally at least 25MB disk space for
prerequisites included in the installation package.
Software Requirements
The following operating systems are supported for the 32-bit Windows x32 platform.
32-bit Windows Server 2003, or later Service Pack levels: Standard or Enterprise
editions.
32-bit Windows Server 2003 R2, or later Service Pack levels: Standard or Enterprise
editions.
32-bit Windows Server 2008, or later Service Pack levels: Standard or Enterprise editions
The following operating systems are supported for the 64-bit Windows x64 platform.
64-bit Windows Server 2003, or later Service Pack levels: Standard x64 or Enterprise
x64 editions.
64-bit Windows Server 2003 R2, or later Service Pack levels: Standard x64 or Enterprise
x64 editions.
64-bit Windows Server 2008, or later Service Pack levels: Standard x64 or Enterprise
x64 editions.
64-bit Windows Server 2008 R2, or later Service Pack levels: Standard x64 or Enterprise
x64 editions
You can also silently install Data Protection for Oracle by using the Microsoft Installer
program, also known as MSI (msiexec.exe).
Alternatively,
you
can
double-
You must install Data Protection for Oracle from an account that is a member of the local
Administrators group for the computer on which the Oracle server is running.
- See more at: http://www.tsmtutorials.com/2013/11/TDP-oracle-requirements-and-installationprocedure.html#sthash.hvOhlwst.dpuf
If you want to configure IBM Tivoli Data Protection for Oracle to protect your Oracle database,
TDP for Oracle must be first installed on your system and a Tivoli Storage Manager server must
be available to communicate with 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.
You must first register the Oracle machine as a client node in Tivoli Storage Manager Server with
appropriate policy settings. The you need to configure the important TDPO configuration files
such as tdpo.opt, dsm.opt and dsm.sys files in the Client side in order to start protecting the
backup. In this post we will see how to register and define policy settings for TDP oracle node on
TSM server end and then see how to configure those important configuration files from client
end.
the Tivoli Storage Manager backup storage pool have unique file names, they never expire on
the Tivoli Storage Manager server.
While defining copy group parameters for TDP Oracle node, the recommended values
for verdeleted and retonly is 0 because 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.
The tdposync utility is used to remove unwanted backup objects from the Tivoli Storage
Manager server. Remember that the inactive backup object cannot be restored through RMAN
using the Data Protection for Oracle interface.
The following backup copy group options are not applicable to Data Protection for Oracle. Data
Protection for Oracle accepts default values for these options.
frequency
verexists
retextra
mode
serialization
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. It is recommended
to define a new policy for TDP for oracle backup.
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).
Note that the Tivoli Storage Manager client user options file (dsm.opt by default) that 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.
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.
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.
You can also include other Tivoli Storage Manager client options when configuring Data
Protection for Oracle like compression, reduplication and enablelanfree parameters.
Remember that The enablelanfree and deduplication options are mutually exclusive.
Therefore, you can only use either one option or the other, but not both options together.
Go to this directory /usr/tivoli/tsm/client/oracle/bin64 and edit the dsm.opt file to include the
server stanza as shown below
servername tsmserv
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 tsmserv
COMMMethod TCPip
TCPServeraddress x.x.x.x
PASSWORDAccess generate
passworddir /home/<oracle user>
nodename TDPONodeName
Make sure the Oracle user has the following permissions
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.
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. If the tdpo_pswdpath option is specified in the tdpo.opt file, it is
ignored.
Change to the /usr/tivoli/tsm/client/oracle/bin64 directory and run the tdpoconf password
command as Oracle user to generate the password file.
tdpoconf password
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.
Run the tdpoconf showenvironment command to confirm proper configuration.
tdpoconf show environment
5.3) To restore a backup, As Oracle user, run your RMAN restore script with the
ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)
run
{
allocate channel t1 type sbt_tape parms
ENV=(TDPO_OPTFILE=/home/oracle/tdpo.opt);
allocate channel t2 type sbt_tape parms
ENV=(TDPO_OPTFILE=/home/oracle/tdpo.opt);
restore database;
recover database;
alter database open;
}
On windows
Instead of /usr/tivoli/tsm/client/oracle/bin64/tdpo.opt use
C:\Program Files\Tivoli\TSM\AgentOBA\tdpo.opt
- See more at: http://www.tsmtutorials.com/2013/11/backup-and-restore-oracle-database-usingtdp-for-oracle.html#sthash.Ak3ZKcjI.dpuf
IBM Tivoli Data Protection for Oracle provides 3 utilities to troubleshoot the problems or issues
faced during oracle backup/restore processes. You can use these utilities to configure and and
also maintain Data Protection for Oracle. These utilities are located in the directory where Data
Protection for Oracle is installed.
Use the tdpoconf (password & showenvironment) utility for password maintenance and
general Data Protection for Oracle setup and maintenance.
Use the tdposync utility to delete the Oracle backups on the Tivoli Storage Manager
server, which are not in the RMAN catalog or Oracle control file. You can use this utility
when backups have not been deleted from the Tivoli Storage Manager server for
various reasons.
Use the tdposync query utility to query backed up objects on the Tivoli Storage
Manager server.
1) Tdpoconf password
When you have password related issues you can create a new password or change an existing
password on the Tivoli Storage Manager server by using this utility.
tdpoconf password
2) Tdpoconf showenvironment
Use the showenvironment command to query the Tivoli Storage Manager server using the
options set in TDPO_OPTFILE. If 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.
tdpoconf showenvironment
3) Tdposync
The tdposync utility checks for items on the Tivoli Storage Manager server that are not in the
RMAN catalog or Oracle control file. With this utility, you can repair these discrepancies between
the Tivoli Storage Manager server and the RMAN catalog or Oracle control file. Running this
command will open a "pick window" where you can select the database objects for deletion
manually.
Syncdb command
This command synchronizes Oracle catalog databases or the Oracle control file with the Tivoli
Storage Manager server.
tdposync syncdb
Query command
Use this command to query the Tivoli Storage Manager server for information about objects that
have been backed up. You can obtain information such as whether an object has been
compressed, encrypted, or deduplicated by the client during a backup operation.
tdposync query
All these utilities requires the options set in the -TDPO_OPTFILE parameter, the tdpo.opt file in
the default installation directory, or the default values set by Data Protection for Oracle to query
the Tivoli Storage Manager server.
If the above command ran successfully, check its output to see if the setup worked as
expected.
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.
Fix the problem shown in those log files and run the tdpoconf utility again.
The most common problems are password authentication issues, important configuration
files read/write permissions and error log read/write permissions to the authorized user.
From the TSM server end, check the activity log for more information. Change in the
client node mount point definition settings can also lead to client backup failures.
If you still dont know how to troubleshoot it, raise the IBM PMR support request by
gathering all the required information.