Automatically shutdown auxiliary after DUPLICATE complete

Question

This is in regards to 10.2.0.4
I am refreshing a Test system with Production data using the DUPLICATE command. I've searched via Google but haven't hit the right search phrase to find the answer to my question. Once the RMAN DUPLICATE command finishes, I would like for RMAN to shutdown the auxiliary database (Test) as there are DBMS_SCHEDULER entries and table data that I want to remove/update before those scheduler items start running.
To kick off the DUPLICATE, I will be using the following command
rman target sys@Production nocatalog auxiliary / cmdfile ='rman_dup.rcv' log=rman_duplicate.log where rman_dup.rcv will look like run {
set until time "to_date('2011-05-11 14:00:00','YYYY-MM-DD HH24:MI:SS')";
allocate auxiliary channel a1 device type disk;
allocate auxiliary channel a2 device type disk;
duplicate target database to Test
  NOFILENAMECHECK;
}I would do this as a script but the catch is I do not know the sys pasword for Production. The person who knows that will be typing it in at the appropriate time. (Long story, don't ask)
So is there a way for RMAN to shutdown the Test system and leave it down after the DUPLICATE is done but still also a user to type in the password for Production so that I don't have to sit there and stare and the screen and manually do the process as soon as I see that DUPLICATE is done?

Answer 1

You will be calling this RMAN from a shell.
So, you could put all of these in a shell script :
!/bin/sh
rman target sys@Production nocatalog auxiliary / cmdfile ='rman_dup.rcv' log=rman_duplicate.log
#the rman_dup.rcv completes and rman exits
# now set the "local" SID
ORACLE_SID=TEST;export ORACLE_SID
# connect to TEST without knowing the SYS password
# TEST can now be referenced as a "local" instance
sqlplus /nolog <<EOF
connect / as sysdba
shutdown immediate
EOF
#Hemant K Chitale
nb : Although I do agree that DUPLICATE doesn't make sense for duplicating production to test/development when you do not / should not have the production SYS password.
You should be creating TEST "as if" doing a D.R., using the Production backup copied over to the Test server.