Permissions error when starting archivelog recovery during active dup

Question

I am doing an active duplication from one linux server to another. The ASM system on the auxiliary server has two data groups. I just ran this same job to create a database to one of the datagroups a few days ago - no problem. Now, running the same job I got an error once the duplication got to the recovery step. The archivelogs had been laid down and do exist on the auxiliary server's asm diskgroup.
Here is the job I am running from the target(source) server:
$ORACLE_HOME/bin/rman <<EOF>> stagenew-2011-04-06.out
connect auxiliary sys/abcdefg@stagenew
connect target sys/abcdefg@xcede
run
allocate channel c1 device type DISK;
allocate channel c2 device type DISK;
allocate channel c3 device type DISK;
allocate channel c4 device type DISK;
allocate auxiliary channel x5 device type DISK;
allocate auxiliary channel x6 device type DISK;
allocate auxiliary channel x7 device type DISK;
allocate auxiliary channel x8 device type DISK;
duplicate target database to stage from active database NOFILENAMECHECK;
EOF
echo "finished"
exit
And here is the error:
archived log for thread 1 with sequence 181831 is already on disk as file +DATA01/stage/archivelog/2011_04_05/thread_1_seq_181831.1615.747682059
archived log for thread 1 with sequence 181832 is already on disk as file +DATA01/stage/archivelog/2011_04_05/thread_1_seq_181832.1614.747682059
archived log for thread 1 with sequence 181833 is already on disk as file +DATA01/stage/archivelog/2011_04_05/thread_1_seq_181833.1645.747682067
archived log file name=+DATA01/stage/archivelog/2011_04_05/thread_1_seq_181816.914.747681987 thread=1 sequence=181816
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: x5
released channel: x6
released channel: x7
released channel: x8
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/05/2011 17:31:24
RMAN-03015: error occurred in stored script Memory Script
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DATA01/stage/archivelog/2011_04_05/thread_1_seq_181816.914.747681987'
ORA-00308: cannot open archived log '+DATA01/stage/archivelog/2011_04_05/thread_1_seq_181816.914.747681987'
ORA-17503: ksfdopn:2 Failed to open file +DATA01/stage/archivelog/2011_04_05/thread_1_seq_181816.914.747681987
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
RMAN>
Recovery Manager complete.
******* The only difference besides the name of the database being created between the duplication that was successful and this one is that the other created the database on one diskgroup and this job is using the other but as far as I can tell there is no difference between the two other than name. As I said earlier, the logs are there. Here they are:
ASMCMD> cd data01/stage/archivelog
ASMCMD> cd 2011_04_05/
ASMCMD> ls
thread_1_seq_181816.914.747681987
thread_1_seq_181817.789.747681987
thread_1_seq_181818.1637.747681987
thread_1_seq_181819.1626.747681987
thread_1_seq_181820.1622.747681995
thread_1_seq_181821.1621.747681995
thread_1_seq_181822.1620.747682009
thread_1_seq_181823.1619.747682013
thread_1_seq_181824.1612.747682015
thread_1_seq_181825.1613.747682029
thread_1_seq_181826.1617.747682029
thread_1_seq_181827.1618.747682029
thread_1_seq_181828.1611.747682037
thread_1_seq_181829.1616.747682051
thread_1_seq_181830.1610.747682053
thread_1_seq_181831.1615.747682059
thread_1_seq_181832.1614.747682059
thread_1_seq_181833.1645.747682067
So I would think that recovery would be running as 'SYS' and that 'SYS' does not have the permissions it needs....but ran same job for different db and no such issue. Any thoughts?

Answer 1

Have you created password file and check parameter remote_login_passwordfile for asm and database home on auxiliary node.
or
run the command from the auxiliary node