From: "MacGregor, Ian A." <ian@slac.stanford.edu>
To: Oracle-L Freelists <oracle-l@freelists.org>
Date: Thu, 3 Mar 2011 15:35:45 -0800
Subject: Rman  "Duplicate target"   Using TDPO
Thread-Topic: Rman  "Duplicate target"   Using TDPO
Message-ID: <618DFC39-AD73-4E09-8CE7-0A0C36825772@slac.stanford.edu>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: ian@slac.stanford.edu

The password for TDPO  can be stored  using the old method which produced a file named  something like

TDPO.<node1>-rman.  To duplicate a database using RMAN backups to say  node2.   You have to copy the password file,
TDPO.<node1>-rman, to node2.   This works well.

However, TDPO has "new" method of storing a password which is written to a file called TSM.PWD.   The people who are responsible for Tivoli are happy with this new method,  because they  do not need to change the password manually.  It will be machine-generated periodically.

The problem is that you cannot simply copy  the file from one server to another.  You can name it differently, but the  problem , at least my best guess at it, is that the new method of storing the password includes the name of the node on which the fie was created.

The old  method of storing passwords still works, but again is not liked by our storage group.   We are doing more and more duplications.   Has anyone figured out how to use the TSM.PWD  style password file with  the rman duplicate target command.

Ian MacGregor
SLAC National Accelerator Laboratory--
http://www.freelists.org/webpage/oracle-l