ADSM-L

Re: [ADSM-L] Separating the Oracle TDP Cfg - from the OS cfg ..

2009-06-23 16:55:34
Subject: Re: [ADSM-L] Separating the Oracle TDP Cfg - from the OS cfg ..
From: Neil Rasmussen <rasmussn AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 23 Jun 2009 13:53:32 -0700
Hello Charles,

DP Oracle relies on the dsm.sys file in the TSM API bin directory
(/usr/tivoli/tsm/client/api/bin64 on AIX, for instance). So the answer to
your question really depends on what you mean by "base dsm.sys"....if by
"base dsm.sys" you mean the BA Client, then yes, DP Oracle can use a
different dsm.sys file.


Regards,

Neil Rasmussen
Tivoli Storage Manager Client Development
IBM Corporation
Almaden Research Center
650 Harry Road
San Jose, CA 95120-6099
rasmussn AT us.ibm DOT com



From:
"Hart, Charles A" <charles_hart AT UHC DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
06/23/2009 12:47 PM
Subject:
Separating the Oracle TDP Cfg - from the OS cfg ..
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>




We are wondering if its possible to separate the TDP Oracle Cfg so it
uses its own dsm.sys instead of the base dsm.sys  The reason we ask is
our Oracle DBA's use TSM to clone DB's and not all our Unix team member
know how to cfg the TDP client and all the stanza's associated with DB
Cloning (Backup Restore)

I looked in the TDP Redbook, didn't really see a way.  Does anyone have
a good idea to have a dsm.sys just for OS Backup and Dsm.sys for the
Oracle folks?


Thank you all for being so helpful!

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

<Prev in Thread] Current Thread [Next in Thread>