below are steps to configure TDP oracle on AIX but on Solaris it should be same steps with different file

system path this steps can be used on rac also if you have rac cluster on two different server's you need to configure tdp on both server with same settings, as per my knowledge the service will be running on only one server, or you can configure sched start and stop script under rac app as well 1. 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. 2. Install Data Protection for Oracle. 3. 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/rdbms/ as the first entry: LD_LIBRARY_PATH=/oracle/rdbms/lib b. Shut down all Oracle instances that use /oracle/rdbms/ c. Go to the /oracle/rdbms/directory. d. Symbolically link the library file to libobk.a ln -s /usr/lib/libobk64.a /oracle/rdbms/lib/libobk.a e. Start the Oracle instances. 4. Make sure the following link exists: /oracle/rdbms/lib/libobk.a -> /usr/lib/libobk64.a 5. Edit the /usr/tivoli/tsm/client/oracle/bin64/tdpo.opt file to include these options DSMI_ORC_CONFIG /usr/tivoli/tsm/client/oracle/bin64/dsm.opt DSMI_LOG /usr/tivoli/tsm/client/oracle/bin64/ TDPO_FS adsmorc TDPO_NODE PROD1_ORADB TDPO_OWNER PROD1_ORADB TDPO_PSWDPATH /usr/tivoli/tsm/client/oracle/bin64 6. In this same directory (/usr/tivoli/tsm/client/oracle/bin64/), create a dsm.opt file. Edit the dsm.opt file to include the following server stanza: SErvername TDPORA 7. Edit usr/tivoli/tsm/client/ba/bin/dsm.sys file to include another server stanza with the following options

SErvername TDPORA PASSWORDACCESS prompt NODENAME PROD1_ORADB COMMmethod TCPip TCPPort 1500 TCPServeraddress 172.16.101.26 Schedlogname /usr/tivoli/tsm/client/oracle/bin64/ora_dsmsched.log Errorlogname /usr/tivoli/tsm/client/oracle/bin64/ora_dsmerror.log

8. Change to the /usr/tivoli/tsm/client/api/bin64 directory and create a symbolic link /usr/tivoli/tsm/client/ba/bin/dsm.sys. ln -s /usr/tivoli/tsm/client/ba/bin/dsm.sys /usr/tivoli/tsm/client/api/bin64/dsm.sys

Change to the /usr/tivoli/tsm/client/oracle/bin64 directory and run the

tdpoconf passwordcommand to generate the password file

Run the tdpoconf showenvironmentcommand to confirm proper configuration. Make sure the proper permissions on tsm dir .

----------------------------------------------------------------------------------------------------------------TDP for Oracle and RMAN Oracle RMAN initiates a backup or restore, TDP for Oracle acts as the interface to the TSM server TDP for Oracle provides the following actions and operations: Full backup function for the following while online or offline: - Databases - Tablespaces - Datafiles - Archive log files - Control files Full database restore while offline Tablespace and datafile restore while online or offline Change of TDP client password The TDP for Oracle application client provides a command line interface for performing backups and restores. The application client commands are issued from a command prompt

There are three basic steps that must take place before you can use the TSM server. These steps will be covered in greater detail in subsequent chapters: 1. Register a node with the TSM server. 2. Install the TSM client (backup-archive client, TDP or API client). 3. Configure the TSM client When the node is registered, it is given six key values that play an important role for performing backups and restores. NODENAME, PASSWORD,DOMAIN, ARCHDELETE, BACKDELETE, MAXNUMMP.

Configuring the TSM client

Must perform the following tasks: Set the environment variables, create and specify options in the client options file, set up the scheduler, and perform configuration tasks specific to the TDP product being used. All products that interface with the TSM server through the TSM API use a different set of environment variables. The environment variables that are used are DSMI_CONFIG, DSMI_DIR, and DSMI_LOG If these environment values are not set, default values are used that are different than the default values that the TSM backup-archive client uses. TDP for Oracle stores database and tablespace backups as backup objects on TSM storage. For backup objects, you can run the command, select * from backups. For archive objects you use the command, select * from archives. Both commands are run using the TSM Administrative command line program (dsmadmc). After taking the backup we ran the SQL query
select * from backups where node_name=JAMAICA_ORACLE. The entry in the quotes is case sensitive and must be upper case. The output of this command tells us that the backup object was sent by a client program (TDP Oracle) that authenticated with the TSM server as node JAMAICA_ORACLE

TDP for Oraclefor Windows uses \adsmorc as the FILESPACE_NAME when sending the object to the TSM server. Management class for oracle Oracle assigns unique names to every database backup. The settings that pertain to multiple versions do not apply. The following retention settings should be used for the management class that will be bound to the Oracle backups. VEREXISTS=1 Keeps only one version of the backup file as the name of the backup is unique. (There will not be a newer version of the backup image with the same name). VERDELETED=0 If the backup file has been deleted then TSM should not keep an inactive version of this file. RETEXTRA=0 (the same value as RETONLY) This parameter will never be used as you will never have more than one version of the backup file. To prevent confusion set this parameter to the same value as RETONLY. RETONLY=0 When a backup image file becomes inactive it will be purged from the TSM server at the next expiration.

Choosing a password
This password will be used with the aobpswd command to encrypt the password for future use when PASSWORDACCESS is set to GENERATE with TDP for Oracle for Windows. With TDP for Oracle for UNIX, PASSWORDACCESS is set to PROMPT; however, the aobpswd command generates an encrypted password in the TDP directory, which accomplishes the same purpose.

Choosing a nodename
The TSM backup-archive client defaults the nodename to be the hostname of the machine. We chose to register separate nodes for the Oracle backups, and we used the naming convention of
hostname_oracle.

Setting the BACKDELETE option

The node that is used to backup the database objects to TSM must be able to manually delete the backup objects. To do so specify BACKDELETE=YES when registering the node. You can update a node that has this value set to NO and set it to YES with the update node command. If this value is set to NO, RMAN will not be able to manually inactivate the Oracle backup objects, and they will reside in TSM storage forever.

Setting the MAXNUMMP

The MAXNUMMP must not be set to a value greater than the actual number of physical drives defined to the TSM server.

Starting SQL and RDBMS services