Rebuild standby database

Question

Good morning,
I am stuck with my rebuild standby now. I am not sure what is wrong with what I am doing. My production database is 2 nodes RAC database and the db version is 10.2.0.4 using ASM (10.2.0.4) on Sun servers SunOS 5.10. The standby is in SunOS 5.10 and single node database. In this server we also have 3 other databases so all 4 databases share the same ASM in this server. Recently we upgraded the ASM home and other databases home from 10.2.0.4 to 10.2.0.5. Only this standby home stays in 10.2.0.4. We also use OMF and all database files are in ASM and archive logs are in ASM as well. The backups are in files system. After I upgrade the ASM I forgot bring up the standby instance/listener so it falls behind on the archive logs applying process. I am now trying to rebuild this standby. The first two times failed due to diskgroup space exhausted. So I deleted old standby data files from ASM. Then I got ORA-15055: unable to connect to ASM instance & ORA-00020: maximum number of processes () exceeded. I increased the processes parameter for ASM from 40 to 85. The last time refresh I got the following errors and I googled these errors online but have not got any useful info yet. Have anybody experienced this before?
RMAN-00571: ===========================================================
RMAN-10035: exception raised in RPC:
RMAN-10031: RPC Error: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
RMAN-10035: exception raised in RPC:
RMAN-10031: RPC Error: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
RMAN-10035: exception raised in RPC:
RMAN-10031: RPC Error: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
RMAN-03002: failure of Duplicate Db command at 11/01/2010 15:25:30
RMAN-03015: error occurred in stored script Memory Script
RMAN-10038: database session for channel ORA_AUX_DISK_1 terminated unexpectedly
The rman script for dup is:
run {
Duplicate target database for standby dorecover;
Thanks a lot in advance for your help!
Shirley

Answer 1

I do believe the version could be causing your issue. I have always used the exact same version without issue.
I setup my standby for dup as follows:
Same directory structure including the flash area.
I copy the primary password file to the same directory on the standby.
I defer the primary :
alter system set log_archive_dest_state_2=defer;
I create a temp int file for the standby with these set (I'm using Oracle 11)
db_name
control_files
db_recovery_file_dest
db_recovery_file_dest_size
compatible
db_block_size
undo_tablespace
undo_management
undo_retention
I backup the primary using
RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
I move the current days archive and this backup to the standby
I start the standby use the temp init
startup nomount pfile='/u01/app/oracle/admin/PRIMARY/pfile/init.ora';
And I dupicate as follows:
rman target sys/password@PRIMARY auxiliary /
run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
Assuming this flys I copy a pfile version of the primary init over and change it for standby and then create a new spfile if needed.
Finally I enable
alter system set log_archive_dest_state_2=enable;
And start redo apply on the standby and test