Recover standby database after primary failed

Hi,
I'm having 11g setup with 2 standby databases. My scenario is i'm doing failover on one standby[new primary] and converting old primary as a standby. Question is what is the status of another standby? have to create new standby or can recover using flash option?
regards,
jp

'11g' is not a version, it is a marketing label. You need to post your version in the format <x>.<x>.<x>.<x>
Yes, I know this is asked much.
Also your question sadly lacks on details, as in this version of Oracle you can cascade standby databases (standby 1 can cascade to standby 2)
This begs the simple question:
Did you try?
If so, what happened?
If you didn't try, why didn't you try? What can happen?
Sybrand Bakker
Senior Oracle DBA

Similar Messages

Use standby-database as standby-database after creating primary database

First I will tell what we have and what I did.
We have a standby database on server B that was not started. We did a cold copy to server A and opened the database on server A as primary database. Now we wonder if we can use the standby database on server B to apply archives without creating a new copy to server B. The standby database on server B is waiting for sequence 2900, while the database on server A started with a new sequence.
Is it possible somehow to start the recovery again on the standby databsae on server B without creating a new copy?
Forgot to mention: db-version is 9.2.0.7.0, OS is SunOS 5.10

Writing seperate code is not needed, Oracle will copy the files if the log_archive_dest is set to the right value.
However, it is solved!
What I did:
- create standby controlfile on the primary
- copy standby controlfile to standby database
- on standby: startup nomount / alter database mount standby database
- on primary: set log_archive_dest_2 to trigger the copying of archivelogs to the standby
Right now the standby database is recovering.

Error when trying to recover datafile from standby database to primary

hi friends,
getting problem with restoring datafile from backupset taken on standby database to primary database.
os: windows server 2003
db: oracle 11gR1(11.1.0.6)
i've configured standby database on two different hosts.
host1 - primary (db_uinque_name= prod)
host2 - standby (db_uniue_name= prodsby)
I've configure both database with recovery catalog. I take backup on standby database. users' datafile of primary database has been lost.i'm trying to restore from the backupsets taken on standby database.
with the help of - http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/rman.htm#BAJCEFEG
on primary
c:\>rman target sys/password catalog rcat/password
rman>list backup for db_unique_name prodsby;
display the backupsets
rman>restore datafile 4;
Starting restore at 06-NOV-08
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1051 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/06/2008 12:12:18
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
also use to tag to restore the datafile
rman>restore datafile 4 from tag='base0_prodsby';
Starting restore at 06-NOV-08
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/06/2008 11:27:21
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
i'm getting above errors when try to restore the datafile.
when i issue the following command.
BACKUP AS COPY DATAFILE 4 AUXILIARY FORMAT 'C:\app\Administrator\oradata\prod\USERS01.DBF';
Starting backup at 06-NOV-08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1068 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
15
ORA-17628: Oracle error 19505 returned by remote Oracle server
please friends, try to help me to solve the problem.
Thanks,
Vihang

hi.
Its not necessary its a otherway around to recover datafile from this backupset and apply archivelogs to make datafile consistent.
yes, it ain't the right way to restore backup to primary location.
so how would i connect to standby database with primary and recovery catalog.
i need to connect to recovery catalog and primary site because i need to restore to primary location and recovery catalog contain all metadata and backupsets related information.
i also tried the following steps from oracle documentation.
Connect to the standby database as the target database:
CONNECT TARGET sys@standby
You are prompted for a password:
target database Password: password
Connect to the primary database as the auxiliary database:
CONNECT AUXILIARY sys@primary
You are prompted for a password:
target database Password: password
Back up the datafile on the standby host across the network to a location on the primary host. For example, suppose that /disk1/df2.dbf is the name of datafile 2 on the standby host. Suppose that /disk8/datafile2.dbf is the name of datafile 2 on the primary host. The following command would copy datafile 2 over the network to /disk9/df2copy.dbf:
BACKUP AS COPY DATAFILE 2 AUXILIARY FORMAT '/disk9/df2copy.dbf';
Starting backup at 06-NOV-08
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1068 device type=DISK
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=C:\APP\ADMINISTRATOR\ORADATA\prod\USERS01.
DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/06/2008 12:49:
15
ORA-17628: Oracle error 19505 returned by remote Oracle server
getting this error.

Auto specified any value after ran RECOVER STANDBY DATABASE;

Dear all,
When i ran the RECOVER STANDBY DATABASE command.It 's will prompt as
below :
SQL> RECOVER STANDBY DATABASE;
ORA-00279: change 302927 generated at 09/10/2007 14:08:24 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\DB817\ARCHIVE\DB817T001S00021.ARC
ORA-00280: change 302927 for thread 1 is in sequence #21
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Is there anyway to force specified "AUTO" automatically ?
Because i will to create a scripts file for run automatic .
Thanks for advance !
Chara

ORA-00289: suggestion : D:\ORACLE\ORADATA\DB817\ARCHIVE\DB817T001S00021.ARCFirst check if the required Archive / Redo log is present on your system under the directory "D:\ORACLE\ORADATA\DB817\ARCHIVE".
For automatic recovery use:
ALTER DATABASE RECOVER AUTOMATIC STANDBY DATABASE;
or
RECOVER AUTOMATIC STANDBY DATABASE;
Cheers!

Recover standby database

Our primary linux 10g db is in standard edition and we would like to manually create a standby database
After copying the control and datafiles from primary to standby database, started the standby instance ..
SQL> startup nomount pfile=/path/to/pfile/initSID.standby
SQL> alter database mount standby database;
SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log
'/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
How do I resolve this problem? Log sequence 833 is the current log on the primary db, archive log haven't been written yet. When I try to "alter database open read only" on the standby db, I get an error "ORA-01156: recovery in progress may need access to file".
I then went back to my primary database, which already had another log switch to 834, log 833 is now available, I then moved that archive log file to the standby db. Try to recover standby database again, but still got errors..
SQL> startup nomount pfile=/path/to/pfile/initSID.standby
SQL> alter database mount standby database;
SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
SQL> alter database open read only;
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
Would something please explain this to me? What am I doing wrong? Thanks in advance.

I copied the missing archive log over to standby db, still got the same error.
1) SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
I also tried..
2) SQL> recover standby database using backup controlfile until cancel;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
Edited by: user10427867 on Aug 28, 2009 5:56 AM

Recover Standby Database suggests wrong filename

Hi,
I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
The standby database is started this way :
startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
alter database mount standby database;
And the archives are applied this way :
recover standby database;
AUTO
(AUTO for the command to apply all available archive logs automatically, using the suggested paths and filenames)
My problem is that once in a while (maybe once every 2-3 weeks), the suggested filename does not have the same format as the rest of the time. I then have to manually specify the correct filename and it goes fine after that.
Example :
In this example, you will see that it is first looking for sequence 22907 (o1_mf_1_22907_5n3m1xrf_.arc), then 22908 (o1_mf_1_22908_5n3m4kf0_.arc) [Notice the format of the file name] and then tries to look for sequence 22909, but looks for filename ".o1_mf_1_22909_5n3md1h5_.arc.qXMz5s"
Mon Jan 4 06:22:01 2010
ALTER DATABASE RECOVER standby database
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
Mon Jan 4 06:22:02 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jan 4 06:22:02 2010
Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/o1_mf_1_22907_5n3m1xrf_.arc
Mon Jan 4 06:24:20 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jan 4 06:24:20 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jan 4 06:24:20 2010
Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/o1_mf_1_22908_5n3m4kf0_.arc
Mon Jan 4 06:24:46 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jan 4 06:24:46 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jan 4 06:24:46 2010
Media Recovery Log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/.o1_mf_1_22909_5n3md1h5_.arc.qXMz5s
Errors with log /oraarch/oracle/flash_recovery_area/GIGA10G/archivelog/2010_01_04/.o1_mf_1_22909_5n3md1h5_.arc.qXMz5s
ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jan 4 06:24:46 2010
ALTER DATABASE RECOVER CANCEL
Mon Jan 4 06:24:46 2010
Media Recovery Canceled
Completed: ALTER DATABASE RECOVER CANCEL
Can someone explain to me why is this happening please ?
Thanks a lot,
Mat

@fjfranken
Yes. If I manually enter the name of the file for the sequence requested instead of passing the suggested fielname, it works fine.
And the log_archive_format is not defined, I am using the flash_recovery_area and let Oracle manage this automatically.
@Hemant K Chitale
Unfortunately, those sequences are not listed anymore in the V$ARCHIVED_LOG view.
Well, I think the the problem might be related to files that are being written to at some time...
Thanks,
Mat

Recover standby database error

Hi
here is the error message i got when i run this command
09:30:35 SYS@MOZAI> alter database recover standby database until cancel;
alter database recover standby database until cancel
ERROR at line 1:
ORA-00279: change 126425376421 generated at 02/26/2012 09:26:00 needed for thread 2
ORA-00289: suggestion : +ARCH
ORA-00280: change 126425376421 for thread 2 is in sequence #312362
Any suggestion is highly apprciated .
Thanks

Hello;
You probably started the recovery ( to apply redo from the Primary )
Cancel this before doing the command you trying :
alter database recover managed standby database cancel;Then issue your command again.
Best Regards
mseberg

What is command to bring back the standby database to primary database?

what is command to bring back the standby database to primary database?
Please reply soon....

Mariappan wrote:
no i am not using dgbroker...Please don't make me drag everything out of you. If you only answer one question at a time, this is going to take much longer and I'm going to find better things to do with my time.
One more time: Have you read the documentation - http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/role_management.htm#1033701

How to recover my database after lose some archivelogs?

How to recover my database after lose some archivelogs?
What should I do next?
When I make a point-in-time recovery, I get the following message:
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/rcatalog/system01.dbf'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 09/25/2008 16:41:19
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 17 lowscn 798237 found to restore
RMAN-06025: no backup of log thread 1 seq 16 lowscn 796977 found to restore
RMAN-06025: no backup of log thread 1 seq 15 lowscn 781378 found to restore
RMAN-06025: no backup of log thread 1 seq 14 lowscn 759019 found to restore
RMAN-06025: no backup of log thread 1 seq 13 lowscn 709039 found to restore
RMAN-06025: no backup of log thread 1 seq 12 lowscn 708479 found to restore
RMAN-06025: no backup of log thread 1 seq 11 lowscn 676234 found to restore
RMAN-06025: no backup of log thread 1 seq 10 lowscn 646686 found to restore
RMAN-06025: no backup of log thread 1 seq 9 lowscn 645207 found to restore
RMAN-06025: no backup of log thread 1 seq 8 lowscn 645199 found to restore
RMAN-06025: no backup of log thread 1 seq 7 lowscn 595363 found to restore
RMAN-06025: no backup of log thread 1 seq 6 lowscn 557197 found to restore
RMAN-06025: no backup of log thread 1 seq 5 lowscn 519102 found to restore
RMAN-06025: no backup of log thread 1 seq 4 lowscn 519053 found to restore
RMAN-06025: no backup of log thread 1 seq 3 lowscn 492824 found to restore
RMAN-06025: no backup of log thread 1 seq 2 lowscn 476888 found to restore

Mixing thread
yours recovery asking a lot of archivelog ,you are in the situation now like you are in no archive mode recovery..which requires last cold backup.
What you can do is restore yours old backup with its old controlfile and then recover till before that miissing log by using recover database using backup controlfile.
Khurram

Failover from standby database to primary database

Hi,
Can anyone suggest me, How to do " Standby DataGuard database to primary database (dataguard)".
Kindly Give me steps.
Thanks,
Shweta

Hi
Follow these steps
Oracle switchover operation:
1.     Check and verify the role parameter on the v$parameters both primary and standby
On Primary
Log_archive_dest_1=”this is the local archive destination”
+Log_archive_dest_2=”This is the Service [TNS ENTRY]”+
Log_archive_dest_state_1=Enable
Log_archive_dest_state_2=Enable
Fal_server=”this should have the tns entry for the standby
Fal_Client=”this should have the tns entry for the primary
Standby_archive_dest=”This should have the Location where the archive located”
Standby_File_Management=AUTO
On Standby
Log_archive_dest_1=”this is the local archive destination”
+Log_archive_dest_2=”This is the Service [TNS ENTRY]”+
Log_archive_dest_state_1=Enable
Log_archive_dest_state_2=DEfer
Fal_server=”this should have the tns entry for the primary
Fal_Client=”this should have the tns entry for the standby
Standby_archive_dest=”This should have the Location where the archive located”
Standby_File_Management=AUTO
2.     Down all the applications connects to the database
3.     Shutdown both primary and standby databases
4.     For RAC Keep Only one primary and One standby up and all other nodes should be down
5.     Check the Primary database on Open mode and the Standby database on mount stage
6.     On Primary
SQL>select switchover_status from v$database;Sessions Active or To standby will be appearing on the result
SQL> alter database commit to switchover to standby with session shutdown;
SQL> shutdown Immediate;
SQL>startup nomount;
SQL>alter database mount standby database;
SQL>Alter system set log_Archive_dest_state_2=defer;7.     On Standby
SQL>select switchover_status from v$database;it is acceptable to have Sessions Active or To Primary
SQL>alter database commit to switchover to primary with session shutdown;
SQL>shutdown immediate;
SQL>Startup;
SQL.>Alter system set log_archive_dest_state_2=enable;8.     On Primary
start the managed recovery
SQL>Alter database recover managed standby database disconnect from session;9.     Check the log shipment is working from New Primary to New Standby Using
SQL>Alter system switch logfile; ---- On New Primary.check the alert log on both Primary and Standby for the log shipment and Media recovery.
10.     If the switch over fail issue the following statement on standby (ORACLE 9i)
SQL> alter database recover managed standby database finish skip standby logfile ┘
SQL> alter database commit to switchover to primary┘
SQL> shutdown immediate;
SQL> Startup;11.     If this don’t work please issue the below statement
SQL> alter database activate standby database skip standby logfile;12.     If the switch over fail issue the following statement on standby (ORACLE 10g and above)
SQL> alter database recover managed standby database finish force;
SQL> alter database commit to switchover to primary;
SQL> alter database open;
SQL> shutdown Immediate;
SQL> startup;13. Added the temp file to your temp tablespace
If you follow the steps (10,11 & 12 ) you have to recreate the standby again. those steps are actually fail over steps. Hope this will be helpful
Cheers
Kanchana

Restored standby database from primary; now no logs are shipped

Hi
We recently had a major network/SAN issue and had to restore our standby database from a backup of the primary. To do this, we restored the database to the standby, created a standby controlfile on the primary, copied this across to the control file locations and started in standby recover and applied the logs manually/registered to get it back up to speed.
However, no new logs are being shipped across from the primary.
Have we missed a step somewhere?
One thing we've noticed is that there is no RFS process running on the standby:
SQL> SELECT PROCESS, CLIENT_PROCESS, SEQUENCE#, STATUS FROM V$MANAGED_STANDBY;
PROCESS CLIENT_P SEQUENCE# STATUS
ARCH ARCH 0 CONNECTED
ARCH ARCH 0 CONNECTED
MRP0 N/A 100057 WAIT_FOR_LOG
How do we start this? Or will it only show if the arc1 process on the primary is sending files?
The arc1 process is showing at OS level on the primary but I'm wondering if its faulty somehow?
There are NO errors in the alert logs in the primary or the standby. There's not even the normal FAL gap sequence type error - in the standby it's just saying 'waiting for log' and a number from ages ago. It's like the primary isn't even talking to the standby. The listener is up and running ok though...
What else can we check/do?
If we manually copy across files and do an 'alter database register' then they are applied to the standby without issue; there's just no automatic log shipping going on...
Thanks
Ross

Hi all
Many thanks for all the responses.
The database is 10.2.0.2.0, on AIX 6.
I believe the password files are ok; we've had issues previously and this is always flagged in the alert log on the primary - not the case here.
Not set to DEFER on primary; log_archive_dest_2 is set to service="STBY_PHP" optional delay=720 reopen=30 and log_archive_dest_state_2 is set to ENABLE.
I ran those troubleshooting scripts, info from standby:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_PHP
fal_server PHP
local_listener
log_archive_config
log_archive_dest_2 service=STBY_PHP optional delay=30 reopen=30
log_archive_dest_state_2 DEFER
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE
PHP PHP MAXIMUM PERFORM PHYSICAL S MOUNTED
ANCE TANDBY
THREAD# MAX(SEQUENCE#)
1 100149
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
MRP0 WAIT_FOR_LOG 1 100150
NAME VALUE UNIT TIME_COMPUTED
apply finish time day(2) to second(1) interval
apply lag day(2) to second(0) interval
estimated startup time 8 second
standby has been open N
transport lag day(2) to second(0) interval
NAME Size MB Used MB
0 0
On the primary, the script has froze!! How long should it take? Got as far as this:
SQL> @troubleshoot
NAME DISPLAY_VALUE
db_file_name_convert
db_name PHP
db_unique_name PHP
dg_broker_config_file1 /oracle/PHP/102_64/dbs/dr1PHP.dat
dg_broker_config_file2 /oracle/PHP/102_64/dbs/dr2PHP.dat
dg_broker_start FALSE
fal_client STBY_R1P
fal_server R1P
local_listener
log_archive_config
log_archive_dest_2 service="STBY_PHP" optional delay=720 reopen=30
log_archive_dest_state_2 ENABLE
log_archive_max_processes 2
log_file_name_convert
remote_login_passwordfile EXCLUSIVE
standby_archive_dest /oracle/PHP/oraarch/PHParch
standby_file_management AUTO
NAME DB_UNIQUE_NAME PROTECTION_MODE DATABASE_R OPEN_MODE SWITCHOVER_STATUS
PHP PHP MAXIMUM PERFORMANCE PRIMARY READ WRITE SESSIONS ACTIVE
THREAD# MAX(SEQUENCE#)
1 100206
NOW - before you say it - :) - yes, I'm aware that fal_client as STBY_R1P and fal_server as R1P are incorrect - should be PHP - but it looks like it's always been this way! Well, as least for the last 4 years where it's worked fine, as I found an old SP file and it still has R1P set in there...?!?
Any ideas?
Ross

Can Grid Control 10gR2 create a standby database when primary db uses ASM?

Does anyone know if Grid Control 10gR2 will be able to create a standby database when the primary database uses ASM for data files, redo log files, and archive log files but the standby database will use mounted disks? If it can, would it matter that the primary db will be a RAC cluster and the standby will be a single instance db?

I appreciate your reply and hope you are correct. Have you had a look at the 10gR2 Grid Control to confirm this or are you only going on published statements? The reason I ask is because previous versions of Grid Control claimed to support ASM but they would only allow you to work with them AFTER you had created a standby database manually but you couldn't actually use Grid Control to create a standby database from a primary database that had its log files on ASM disks.

SECURITY PATCH ON STANDBY DATABASE AND PRIMARY DATABASE

I have a question on applying CPU on standby and primary database
I have a standby database on machine2 and primary on machine1
I applied a CPU patch on the Oracle Home of Standby database and
did not run the catcpu.sql as standbydatabase is in mount state.
Now i am going to apply the CPU patch on primary database.
What i need to confirm is that after i apply the patch on primary database oracle home
and run the cat cpu.sql on that do i have to do anything on the standby database
for instance rebuilding it or something or the change would be shipped to the standby
server automatically.
The purpose is to have the primary and standby database on the same patch level
in case of a failover
Please let me know asap

Any one has any idea on this. Any ideas would be appreciated

Relocating datafiles on standby database after mount point on stanby is ful

Hi,
We have a physical standby database.
The location of datafiles on primary database are at /oracle/oradata/ and the location of datafiles on standby database are at /oracle/oradata/
Now we are facing a situation of mount mount getting full on standby database so we need to move some tablespaces to another location on standby.
Say old location is /oracle/oradata/ and new location is /oradata_new/ and the tablespaces to be relocated are say tab1 and tab2.
Can anybody tell me whether following steps are correct.
1. Stop managed recovery on standby database
alter database recover managed standby database cancel;
2. Shutdown standby database
shutdown immediate;
3. Open standby database in mount stage
startup mount;
4. Copy the datafiles to new location say /oradata_new/ using os level command
4. Rename the datafile
alter database rename file
'/oracle/oradata/tab1.123451.dbf', '/oracle/oradata/tab1.123452.dbf','/oracle/oradata/tab2.123451.dbf',''/oracle/oradata/tab2.123452.dbf'
to '/oradata_new/tab1.123451.dbf', '/oradata_new/tab1.123452.dbf','/oradata_new/tab2.123451.dbf',''/oradata_new/tab2.123452.dbf';
5. Edit the parameter db_file_name_convert
alter system set db_file_name_convert='/oracle/oradata/tab1','/oradata_new/tab1','/oracle/oradata/tab2','/oradata_new/tab2'
6. Start a managed recovery on standby database
alter database recover managed standby database disconnect from session;
I am littelbit confused in step 5 as we want to relocate only two tablespaces and not all tablespaces so we have used.
Can we use db_file_name_convert like this i.e. does this work for only two tablespaces tab1 and tab2.
Thanks & Regards
GirishA

http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010428
8.3.4 Renaming a Datafile in the Primary Database
When you rename one or more datafiles in the primary database, the change is not propagated to the standby database. Therefore, if you want to rename the same datafiles on the standby database, you must manually make the equivalent modifications on the standby database because the modifications are not performed automatically, even if the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
The following steps describe how to rename a datafile in the primary database and manually propagate the changes to the standby database.
To rename the datafile in the primary database, take the tablespace offline:
SQL> ALTER TABLESPACE tbs_4 OFFLINE;
Exit from the SQL prompt and issue an operating system command, such as the following UNIX mv command, to rename the datafile on the primary system:
% mv /disk1/oracle/oradata/payroll/tbs_4.dbf
/disk1/oracle/oradata/payroll/tbs_x.dbf
Rename the datafile in the primary database and bring the tablespace back online:
SQL> ALTER TABLESPACE tbs_4 RENAME DATAFILE 2> '/disk1/oracle/oradata/payroll/tbs_4.dbf'
3> TO '/disk1/oracle/oradata/payroll/tbs_x.dbf';
SQL> ALTER TABLESPACE tbs_4 ONLINE;
Connect to the standby database, query the V$ARCHIVED_LOG view to verify all of the archived redo log files are applied, and then stop Redo Apply:
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Shut down the standby database:
SQL> SHUTDOWN;
Rename the datafile at the standby site using an operating system command, such as the UNIX mv command:
% mv /disk1/oracle/oradata/payroll/tbs_4.dbf /disk1/oracle/oradata/payroll/tbs_x.dbf
Start and mount the standby database:
SQL> STARTUP MOUNT;
Rename the datafile in the standby control file. Note that the STANDBY_FILE_MANAGEMENT initialization parameter must be set to MANUAL.
SQL> ALTER DATABASE RENAME FILE '/disk1/oracle/oradata/payroll/tbs_4.dbf'
2> TO '/disk1/oracle/oradata/payroll/tbs_x.dbf';
On the standby database, restart Redo Apply:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> DISCONNECT FROM SESSION;
If you do not rename the corresponding datafile at the standby system, and then try to refresh the standby database control file, the standby database will attempt to use the renamed datafile, but it will not find it. Consequently, you will see error messages similar to the following in the alert log:
ORA-00283: recovery session canceled due to errors
ORA-01157: cannot identify/lock datafile 4 - see DBWR trace file
ORA-01110: datafile 4: '/Disk1/oracle/oradata/payroll/tbs_x.dbf'

Recovered standby database, still it is looking for gap sequence

I have lost archive logs in both primary and standby database(deleted due to low space).
So folloed the below steps.
1.Identified minimum SCN from standby database.
2.Took inremental backup from primary database according this SCN(nnnnn)
3.Transfer this backup file to standby side
4. Cataloged database backups and recovered the database.
But medial recovery is searching for missing archived logs. Please advice.

957905 wrote:
I have lost archive logs in both primary and standby database(deleted due to low space).
So folloed the below steps.
1.Identified minimum SCN from standby database.
2.Took inremental backup from primary database according this SCN(nnnnn)
3.Transfer this backup file to standby side
4. Cataloged database backups and recovered the database.
But medial recovery is searching for missing archived logs. Please advice.Probably you have not restored new standby controlfile before performing recovery.

Recover standby database after primary failed

Similar Messages

Maybe you are looking for