| Duplicate database for standby returns error ORA-19625: error identifying file /home/oracle/stdbyctr [message #594483] |
Thu, 29 August 2013 02:03  |
 |
n2fontenay
Messages: 15
Registered: December 2011
Location: San Diego, CA
|
Junior Member |
|
|
I'm working on creating duplication scripts for standby purposes. and it's constantly failing even though the backups are located in the exact same folder. DB structure is identical and spfile is already configured for standby. and it results in this.
channel aux1: restoring control file
ORA-19625: error identifying file /home/oracle/stdbyctrl.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/home/oracle/stdbyctrl.ctl)
ORA-19601: output file is control file (/opt/oracle/oradata/vcas/control01.ctl)
failover to previous backup
I have been searching a solution for a few days now and I think I need the help of the community. It does work if I take the backup in the flash recovery area, but i need this method because it will be applied on a cluster to cluster replication using ASM on both clusters. Thank you in advance:
Details below:
This is the procedure I'm using: From my primary server: I perform the backup.
rman target sys/verimatrix@to_primary auxiliary sys/verimatrix@to_standby catalog rman/cat@to_primary << EOF
> RUN {
> allocate channel d1 type disk;
> backup format '/home/oracle/ForStandby_%U.bkp' database;
> sql 'alter system archive log current';
> backup format '/home/oracle/ForStandby_arc_%U.bkp' archivelog all;
> backup current controlfile for standby format '/home/oracle/ForStandbyCTRL.bkp';
> release channel d1;
> }
> EOF
Then I copy them to the standby in the oracle home as well:
$scp ForStandby* vmx@192.168.1.149:/home/vmx
ForStandby_0qoib29b_1_1.bkp 100% 545MB 23.7MB/s 00:23
ForStandby_0roib29i_1_1.bkp 100% 6976KB 6.8MB/s 00:00
ForStandby_arc_0soib29n_1_1.bkp 100% 49MB 24.6MB/s 00:02
ForStandbyCTRL.bkp 100% 6944KB 6.8MB/s 00:00
On standby server:
[oracle@standby ~]$ ll
total 622716
-rw------- 1 oracle dba 571039744 Aug 27 13:51 ForStandby_0qoib29b_1_1.bkp
-rw------- 1 oracle dba 7143424 Aug 27 13:51 ForStandby_0roib29i_1_1.bkp
-rw------- 1 oracle dba 51538432 Aug 27 13:51 ForStandby_arc_0soib29n_1_1.bkp
-rw------- 1 oracle dba 7110656 Aug 27 13:51 ForStandbyCTRL.bkp
Then I execute the duplicate command from the primary:
[oracle@primary ~]$ rman target sys/verimatrix@to_primary auxiliary sys/verimatrix@to_standby catalog rman/cat@to_primary << EOF
> RUN
> {
> ALLOCATE CHANNEL C1 type disk;
> ALLOCATE AUXILIARY CHANNEL aux1 TYPE DISK;
> DUPLICATE TARGET DATABASE FOR STANDBY NOFILENAMECHECK DORECOVER;
> RELEASE CHANNEL C1;
> RELEASE CHANNEL aux1;
> }
> EOF
Which fails like this invariably:
Recovery Manager: Release 10.2.0.5.0 - Production on Tue Aug 27 07:59:02 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: VCAS (DBID=3516284596)
connected to recovery catalog database
connected to auxiliary database: VCAS (not mounted)
RMAN> 2> 3> 4> 5> 6>
allocated channel: C1
channel C1: sid=139 devtype=DISK
allocated channel: aux1
channel aux1: sid=152 devtype=DISK
Starting Duplicate Db at 27-AUG-13
contents of Memory Script:
{
set until scn 429183;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
}
executing Memory Script
executing command: SET until clause
Starting restore at 27-AUG-13
channel aux1: restoring control file
ORA-19625: error identifying file /home/oracle/stdbyctrl.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/home/oracle/stdbyctrl.ctl)
ORA-19601: output file is control file (/opt/oracle/oradata/vcas/control01.ctl)
failover to previous backup |
|
|
|
|
|
| Re: Duplicate database for standby returns error ORA-19625: error identifying file /home/oracle/stdbyctr [message #594485 is a reply to message #594483] |
Thu, 29 August 2013 02:18  |
|
n2fontenay
Messages: 15
Registered: December 2011
Location: San Diego, CA
|
Junior Member |
|
|
Hello,
Thanks for the quick reply. vmx is only the user which allows ssh.
They are in the /home/oracle folder if you look at the command immediately after.
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
37 Full 535.35M DISK 00:00:04 27-AUG-13
BP Key: 37 Status: AVAILABLE Compressed: NO Tag: TAG20130827T085707
Piece Name: /home/oracle/ForStandby_16oib633_1_1.bkp
List of Datafiles in backup set 37
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
1 Full 431212 27-AUG-13 /opt/oracle/oradata/vcas/system01.dbf
2 Full 431212 27-AUG-13 /opt/oracle/oradata/vcas/undotbs01.dbf
3 Full 431212 27-AUG-13 /opt/oracle/oradata/vcas/sysaux01.dbf
4 Full 431212 27-AUG-13 /opt/oracle/oradata/vcas/users01.dbf
5 Full 431212 27-AUG-13 /opt/oracle/oradata/vcas/rman_catalog01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
38 Full 6.80M DISK 00:00:00 27-AUG-13
BP Key: 38 Status: AVAILABLE Compressed: NO Tag: TAG20130827T085707
Piece Name: /home/oracle/ForStandby_17oib63a_1_1.bkp
Control File Included: Ckp SCN: 431214 Ckp time: 27-AUG-13
SPFILE Included: Modification time: 27-AUG-13
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
39 52.36M DISK 00:00:01 27-AUG-13
BP Key: 39 Status: AVAILABLE Compressed: NO Tag: TAG20130827T085716
Piece Name: /home/oracle/ForStandby_arc_18oib63c_1_1.bkp
List of Archived Logs in backup set 39
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 2 393574 27-AUG-13 421242 27-AUG-13
1 3 421242 27-AUG-13 423289 27-AUG-13
1 4 423289 27-AUG-13 423304 27-AUG-13
1 5 423304 27-AUG-13 427263 27-AUG-13
1 6 427263 27-AUG-13 427304 27-AUG-13
1 7 427304 27-AUG-13 427495 27-AUG-13
1 8 427495 27-AUG-13 427532 27-AUG-13
1 9 427532 27-AUG-13 427603 27-AUG-13
1 10 427603 27-AUG-13 427639 27-AUG-13
1 11 427639 27-AUG-13 428450 27-AUG-13
1 12 428450 27-AUG-13 428455 27-AUG-13
1 13 428455 27-AUG-13 428613 27-AUG-13
1 14 428613 27-AUG-13 428618 27-AUG-13
1 15 428618 27-AUG-13 429165 27-AUG-13
1 16 429165 27-AUG-13 429183 27-AUG-13
1 17 429183 27-AUG-13 430692 27-AUG-13
1 18 430692 27-AUG-13 430709 27-AUG-13
1 19 430709 27-AUG-13 430877 27-AUG-13
1 20 430877 27-AUG-13 430893 27-AUG-13
1 21 430893 27-AUG-13 431226 27-AUG-13
1 22 431226 27-AUG-13 431231 27-AUG-13
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
40 Full 6.77M DISK 00:00:00 27-AUG-13
BP Key: 40 Status: AVAILABLE Compressed: NO Tag: TAG20130827T085719
Piece Name: /home/oracle/ForStandbyCTRL.bkp
Standby Control File Included: Ckp SCN: 431242 Ckp time: 27-AUG-13
And on the standby, by popular demand of 1: 
[oracle@standby ~]$ ll
total 616384
-rw------- 1 oracle dba 561364992 Aug 27 14:54 ForStandby_16oib633_1_1.bkp
-rw------- 1 oracle dba 7143424 Aug 27 14:54 ForStandby_17oib63a_1_1.bkp
-rw------- 1 oracle dba 54908928 Aug 27 14:54 ForStandby_arc_18oib63c_1_1.bkp
-rw------- 1 oracle dba 7110656 Aug 27 14:54 ForStandbyCTRL.bkp
drwxr-xr-x 2 oracle dba 4096 Aug 27 11:47 scripts
I also read that controlfile autobackup makes implicit crosschecks and would expire the backup set. Here's my configuration:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/product/10.2.0/db_1/dbs/snapcf_vcas.f'; # default [Updated on: Thu, 29 August 2013 02:34] Report message to a moderator |
|
|
|
|
|
| Re: Duplicate database for standby returns error ORA-19625: error identifying file /home/oracle/stdbyctr [message #594499 is a reply to message #594494] |
Thu, 29 August 2013 04:06 |
|
n2fontenay
Messages: 15
Registered: December 2011
Location: San Diego, CA
|
Junior Member |
|
|
John,
I didn't mean to laugh at your expense.
I said by popular demand and only you responded and that's what I thought was funny.
I appreciate your help.
I have been busy trying things out.
While I haven't been able to use the duplicate command, the following procedure does work from the exact same location on the standby!
1) RMAN> restore controlfile from '/home/oracle/ForStandbyCTRL.bkp'
2) RMAN> restore database;
3) RMAN> recover database;
Following which it will recover the database until it can't find any more archive logs and spit an ORA- message saying it's looking for an archive seq X.
4) SQL> alter database recover managed standby database disconnect;
Tada 
While I believe this should help me resolve my DB replication for standby purposes, I still have no clue why the duplicate command can't work :/
Note: Since the redo logs are auto managed, the alert log will spit a number of errors relating to that until it decides to just drop them and create new ones. It's self healing.
[Updated on: Thu, 29 August 2013 04:08] Report message to a moderator |
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
