Standby stopped recovery

Hi everyone;
10.2.0.4 Standby database stopped recovery with the following error on alertlog.
Wed Jun 2 13:38:45 2010
RFS[4]: Archived Log: '/...../RCDB_2_1_720616127.arc'
RFS[4]: Physical Standby in the future of Branch(resetlogs_id) 720616127
RFS[4]: Standby database SCN: 2304:-276361630 Primary branch SCN: 2304:-1502231553
RFS[4]: New Archival REDO Branch(resetlogs_id): 720616127 Prior: 550946190
RFS[4]: Archival Activation ID: 0x5dfe4ed2 Current: 0x58adeb9a
RFS[4]: Effect of primary database OPEN RESETLOGS
Wed Jun 2 13:38:45 2010
There were no RESETLOGS operation on the primary side. What may be the cause of this error? Have any ideas?
Thanks..

After trying to start recovery again:
MRP0: Background Managed Standby Recovery process started (RCDB)
Managed Standby Recovery not using Real Time Apply
Warning: Recovery target destination is in a sibling branch
of the controlfile checkpoint. Recovery will only recover
changes to datafiles.
Datafile 1 (ckpscn 9899623255650) is orphaned on incarnation#=1
MRP0: Background Media Recovery terminated with error 19909
Wed Jun 2 13:55:57 2010
Errors in file /.../rcdb_mrp0_16180.trc:
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: '/.../system01.dbf'
Wed Jun 2 13:55:57 2010
Errors in file /.../rcdb_mrp0_16180.trc:
ORA-19909: datafile 1 belongs to an orphan incarnation
ORA-01110: data file 1: '/.../system01.dbf'
Wed Jun 2 13:55:57 2010
MRP0: Background Media Recovery process shutdown (RCDB)

Similar Messages

Standby database recovery problems....

HP-UX 11.23
oracle 10.2.0.2
I know that this has been discussed quite a bit. I've spent a number of hours on this forum alone today just reading through the search hits. I've tried some of the 'tricks' that have been described in the threads. But I'm still getting the same error....
My standby database lost connectivity with my primary, and stopped receiving logs. I got no notification, because my scripts were not set up to catch this event...
The retention policy on my primary is 30 days of archive logs. After that, they are deleted. (I don't agree with it, but not my call)
The standby got more than 30 days out of sync, so I decided to just refresh the whole standby.
Since cold backups are not an option, I did an alter system checkpoint to flush all archive logs. Then I issued a complete hot backup.
Once completed, I went ahead and created a fresh standby control file, as well as a fresh backup control file. In that exact order.
I transferred all db files, archive logs, and control files over to the standby.
I ran the commands:
startup nomount;
(SUCCESSFUL)
alter database mount standby database;
(SUCCESSFUL)
recover standby database;
I let it run through all the archive log files until it errored saying it couldn't find "X" file being the next sequence that wasn't in the directory. Which to my understanding, is normal...time to quit recovery.
When I entered cancel, I get the following error.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7313561157126 generated at 12/17/2008 19:01:02 needed for
thread 1
ORA-00289: suggestion : /oraarch/swesc/1_13729_640853326.arc
ORA-00280: change 7313561157126 for thread 1 is in sequence #13729
ORA-00278: log file '/oraarch/swesc/1_13728_640853326.arc' no longer needed for
this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
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: '/ora1/oradata/peregrine/system01.dbf'
So my understanding of this is that it means that you still need to apply logs.
So I grabbed the logs that had been auto created during the time that I was rebuilding everything and applied them.
Same errors.
I'm at a loss here. How can it still be out of sync? Is there a way to force it to a specific sequence so that I can successfully open it and then shut it down to complete the sequence?
Thanks.

Thanks OrionNet. Great info!!
Here is the response.
OrionNet wrote:
select * from v$archive_gap
NO ROWS SELECTED.
and all the logs got applied
select applied , count(*) from v$archived_log;
-- This should return 1 rows with "YES", number of logs applied.
I had to change change this as it complained about "not a single-group group function
I changed it by adding group by applied to the end...
NO ROWS SELECTED
Then you should try activating standby database
SQL> alter database force nomount pfile='....'; -- or without the pfile
SQL> alter database mount standby database;
-- If all the archived logs have been applied to your standby then stop recovery
SQL> alter database recover manated standby cancel;
-- Note if it fails on activating the database ;shutdown and mount it again and activate (skip stopping recovery step).
SQL> alter database activate standby database;
IF successfull, then perform followin
SQL> alter database open;Regards
OrionNet;
I thought that in a primary/standby scenario, thiat this action would automatically shut down the primary. I can't have that.
HOLDING OFF ON REST FOR RESPONSE...
Edited by: WillyB on Dec 17, 2008 9:40 PM

Logical standby stopped lastnight

Subject: Logical standby stopped lastnight
Author: raghavendra rao yella, United States
Date: Nov 14, 2007, 0 minutes ago
Os info: solaris 5.9
Oracle info: 10.2.0.3
Error info: ORA-16120: dependencies being computed for transaction at SC
N 0x0002.c8f6f182
Message: Our logical standby stopped last night. we tried to stop and start the standby but no help.
Below are some of the queries to get the status:
APPLIED_SCN LATEST_SCN MINING_SCN RESTART_SCN
11962328446 11981014649 11961580453 11961536228
APPLIED_TIME LATEST_TIME MINING_TIME RESTART_TIME
07-11-13 09:09:41 07-11-14 10:26:26 07-11-13 08:57:53 07-11-13 08:56:36
sys@RP06>SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR 1.1962E+10 ORA-16116: no work available
READER 1.1962E+10 ORA-16127: stalled waiting for additional transact
ions to be applied
BUILDER 1.1962E+10 ORA-16127: stalled waiting for additional transact
ions to be applied
PREPARER 1.1962E+10 ORA-16127: stalled waiting for additional transact
ions to be applied
ANALYZER 1.1962E+10 ORA-16120: dependencies being computed for transac
tion at SCN 0x0002.c8f6c002
APPLIER ORA-16116: no work available
APPLIER ORA-16116: no work available
APPLIER ORA-16116: no work available
APPLIER ORA-16116: no work available
APPLIER ORA-16116: no work available
10 rows selected.
Select PID,
TYPE,
STATUS
From
V$LOGSTDBY
Order by
HIGH_SCN; 2 3 4 5 6 7 8
PID TYPE STATUS
17896 ANALYZER ORA-16120: dependencies being computed for transaction at SC
N 0x0002.c8f6f182
17892 PREPARER ORA-16127: stalled waiting for additional transactions to be
applied
17890 BUILDER ORA-16243: paging out 8144 bytes of memory to disk
17888 READER ORA-16127: stalled waiting for additional transactions to be
applied
28523 COORDINATOR ORA-16116: no work available
17904 APPLIER ORA-16116: no work available
17906 APPLIER ORA-16116: no work available
17898 APPLIER ORA-16116: no work available
17900 APPLIER ORA-16116: no work available
17902 APPLIER ORA-16116: no work available
10 rows selected.
How can i get this transaction information, which log miner is looking for dependencies?
Let me know if you have any questions.
Thanks in advance.
Message was edited by:
raghu559

Hi reega,
Thanks for your reply, our logical stdby has '+RT06_DATA/RT06'
and primary has '+OT06_DATA/OT06TSG001'
so we are using db_file_name_convert init parameter but it doesn't work.
Is there any thing particular steps hiding to use this parameter? as i tried this parameter for rman cloning it din't work, as a workaround i used rman set new name command for clonning.
Let me know if you have any questions.
Thanks in advance.

Logical standby stopped when trying to create partitions on primary(Urgent

RDBMS Version: 10.2.0.3
Operating System and Version: Solaris 5.9
Error Number (if applicable): ORA-1119
Product (i.e. SQL*Loader, Import, etc.): Data Guard on RAC
Product Version: 10.2.0.3
logical standby stopped when trying to create partitions on primary(Urgent)
Primary is a 2node RAC ON ASM, we implemented partitions on primar.
Logical standby stopped appling logs.
Below is the alert.log for logical stdby:
Current log# 4 seq# 860 mem# 0: +RT06_DATA/rt06/onlinelog/group_4.477.635601281
Current log# 4 seq# 860 mem# 1: +RECO/rt06/onlinelog/group_4.280.635601287
Fri Oct 19 10:41:34 2007
create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL
Fri Oct 19 10:41:34 2007
ORA-1119 signalled during: create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL...
LOGSTDBY status: ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
LOGSTDBY Apply process P004 pid=49 OS id=16403 stopped
Fri Oct 19 10:41:34 2007
Errors in file /u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
Here is the trace file info:
/u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0
System name: SunOS
Node name: iscsv341.newbreed.com
Release: 5.9
Version: Generic_118558-28
Machine: sun4u
Instance name: RT06
Redo thread mounted by this instance: 1
Oracle process number: 16
Unix process pid: 16387, image: [email protected] (LSP0)
*** 2007-10-19 10:41:34.804
*** SERVICE NAME:(SYS$BACKGROUND) 2007-10-19 10:41:34.802
*** SESSION ID:(1614.205) 2007-10-19 10:41:34.802
knahcapplymain: encountered error=12801
*** 2007-10-19 10:41:34.804
ksedmp: internal or fatal error
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
KNACDMP: *******************************************************
KNACDMP: Dumping apply coordinator's context at 7fffd9e8
KNACDMP: Apply Engine # 0
KNACDMP: Apply Engine name
KNACDMP: Coordinator's Watermarks ------------------------------
KNACDMP: Apply High Watermark = 0x0000.0132b0bc
Sorry our primary database file structure is different from stdby, we used db_file_name_convert in the init.ora, it look like this:
*.db_file_multiblock_read_count=16
*.db_file_name_convert='+OT06_DATA/OT06TSG001/','+RT06_DATA/RT06/','+RECO/OT06TSG001','+RECO/RT06'
*.db_files=2000
*.db_name='OT06'
*.db_recovery_file_dest='+RECO'
Is there any thing wrong in this parameter.
I tried this parameter before for cloning using rman backup. This din't work.
What exactly must be done? for db_file_name_convert to work.
Even in this case i think this is the problem its not converting the location and the logical halts.
help me out.....
let me know if you have any questions.
Thanks Regards
Raghavendra rao Yella.

Hi reega,
Thanks for your reply, our logical stdby has '+RT06_DATA/RT06'
and primary has '+OT06_DATA/OT06TSG001'
so we are using db_file_name_convert init parameter but it doesn't work.
Is there any thing particular steps hiding to use this parameter? as i tried this parameter for rman cloning it din't work, as a workaround i used rman set new name command for clonning.
Let me know if you have any questions.
Thanks in advance.

How can i stop recovery. my phone is stuck in the middle

how can i stop recovery in my iphone 4s? i haven't backit up yet but due to wifi interruption it didn't go through. can i undo it?

No you cannot. If the phone is in recovery mode, all data on it are lost. However, I'm sure you've been making frequent backups as intended, so you should have minimal data loss.

HT201263 how do you stop recovery mode to prevent you loseing all your data on your device when you have to restore it?

How do you stop recovery mode to prevent you loseing all your data on your device when you have to restore it?

The thing is i did not start recovery mode, it did it automatically when i was updating to ios6 and an error occured.

Standby media recovery waiting for inactive thread

Hi,
Please let me know any idea on this scenario. Thanks.
Environment:
Oracle 11.2.0.2
primary: 3 node RAC
standby: 3 node RAC
Problem:
there is thread 5 (not registered instance or did not show in srvctl) that generates archivelog. but the lag apply stopped because of this when the instance (of thread 5) is shutdown.
question: somehow an instance is registered in the cluster but in srvctl only 3 instance is running. it should have 4 instance but 1 is not running. How can I remove the thread 5 so when someone startup then shutdown instance#4 it will not create archivelog that will stopped the apply of archivelog in standby.
note: this is perf environment server so someone and "other" DBA is accessing this environment which I am not aware what are they doing with the cluster.
looking in alert log file: - it is waiting for thread 5 sequence 510. But the instance is down so log is not shipped to standby database and this resulted to lag in other threads.
Sat Aug 03 18:54:47 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
   THREAD# LAST_SEQ_RECEIVED LAST_SEQ_APPLIED
         1             13745            13717
         2             17728            17664
         3             15527            15464
         5               509              509
what I did is:
1. primary (asm copy to file system)
2. scp primary to standby
3. standby (file system copy to asm)
4. rman target / -> catalog archivelog <thread 5 sequence 510)
5. then looking into alert log file; it performed media recovery
Sat Aug 03 23:03:13 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
Media Recovery Waiting for thread 5 sequence 510
Sat Aug 03 23:15:21 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_5_seq_510
Sat Aug 03 23:15:32 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15466.10925.822316315
Sat Aug 03 23:17:18 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17666.853.822333143
Sat Aug 03 23:18:39 2013
Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15467.834.822333553
Sat Aug 03 23:20:54 2013

in Standby, thread 4 and 5 are both UNUSED, and size is incorrect (not equal to other redo log). I want to recreate it but cannot drop redo log. I follow Doc ID 740675.1.
any idea what are the missing steps? thanks.
ORA-01624: needed for crash recovery of instance UNNAMED_INSTANCE_5 (thread 5)
select group#,thread#,archived,status,bytes from v$log;
primary DB:
    GROUP#    THREAD# ARC STATUS                BYTES
         1          1 YES INACTIVE         1073741824
         2          1 YES INACTIVE         1073741824
         3          2 NO CURRENT          1073741824
         4          2 YES INACTIVE         1073741824
         5          3 YES INACTIVE         1073741824
         6          3 YES INACTIVE         1073741824
         7          2 YES INACTIVE         1073741824
         8          1 NO CURRENT          1073741824
         9          3 NO CURRENT          1073741824
        10          4 YES INACTIVE         1073741824
        11          4 NO CURRENT          1073741824
    GROUP#    THREAD# ARC STATUS                BYTES
        12          4 YES INACTIVE         1073741824
        13          5 YES INACTIVE         1073741824
        14          5 YES INACTIVE         1073741824
        15          5 NO CURRENT          1073741824
standby DB:
    GROUP#    THREAD# ARC STATUS                BYTES
         1          1 YES INACTIVE         1073741824
         2          1 YES INACTIVE         1073741824
         3          2 NO CURRENT          1073741824
         4          2 YES INACTIVE         1073741824
         5          3 YES INACTIVE         1073741824
         6          3 YES INACTIVE         1073741824
         7          2 YES INACTIVE         1073741824
         8          1 NO CURRENT          1073741824
         9          3 NO CURRENT          1073741824
        10          4 YES INACTIVE         1073741824
        11          4 NO CURRENT          1073741824
    GROUP#    THREAD# ARC STATUS                BYTES
        12          4 YES INACTIVE         1073741824
        13          5 YES INACTIVE         1073741824
        14          5 YES INACTIVE         1073741824
        15          5 NO CURRENT          1073741824

Standby stop applying archivelogs

Hello,
yesterday, for the purpose of purgering flashback logs (it occupied a lot of FRA space) in standby, I dropped one 'restore point' in the standby database, and 'rm -r' one flashback log (because not very sure, so only rm one flashback log).
this is what I did
cc:
To remove uncessary Flashback Logs, you need to do the following:
1) drop any Guaranteed Restore Points that you don’t need (e.g. drop restore point ===> done in standby
2) set the init parameter DB_FLASHBACK_RETENTION_TARGET adequately ===> done in standby
3) Log in as root and run the following statements:
ls -lrt …/flashback|tail -100 =====> only 'rm' one flashback log (in asm )
prepare delete statement for each file you want to remove
(e.g. rm -f)
then this morning, I found last Applied log is stuck in yesterday afternoon. the stanby database won't apply archivelogs.
SYS> alter database recover managed standby database using current logfile disconnect;
alter database recover managed standby database using current logfile disconnect
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
Any idea to fix those problem?
thank you

Hello,
thank you very much all.
when try to
alter database recover managed standby database cancel;
(...stuck here, no feedback, process running for 10 minutes without any feedback).
thank you
cc: alert log
NOTE: ASMB process exiting due to lack of ASM file activity
Thu Oct 25 12:19:22 2012
Stopping background process RBAL
Starting background process ASMB
ASMB started with pid=44, OS id=53739542
Starting background process RBAL
RBAL started with pid=50, OS id=15597628
Thu Oct 25 12:25:38 2012
SUCCESS: diskgroup RECOVER was mounted
SUCCESS: diskgroup RECOVER was dismounted
Thu Oct 25 12:25:39 2012
NOTE: ASMB process exiting due to lack of ASM file activity
Thu Oct 25 12:25:39 2012
Stopping background process RBAL
Thu Oct 25 12:32:49 2012
ORA-1013 signalled during: alter database recover managed standby database cancel...
Thu Oct 25 12:33:15 2012
alter database recover managed standby database cancel
(..hanging...)
Edited by: 951932 on Oct 25, 2012 10:40 AM

Logical standby stops deleting archives automatically

We are ruining 11.1.0.7 on windows 2008 64 bit
The issue I am facing is we have these settings implemented
log_auto_delete = true
log_auto_delete_retention_target = 5
Logical standby works fine and deletes the archive logs coming from primary but after some day it stops working. I have to stop and start the database in order to make it work. Does anybody has this kind of situation? Please help.

Hello;
This might be worth a look:
Bug 13448652 - LOG_AUTO_DELETE setting reverts to FALSE on Logical Standby (Doc ID 13448652.8)
Best Regards
mseberg

Sql Apply on standby stops on error

hi all,
I have run into problem I can't figure out.
There are test and production databases, for both there are logical standby databases.
For example, when materialized view is created on primary database, I see error "ORA-16226: DDL skipped due to lack of support", which is ok.
When I try to create index on test database, I got message "ORA-16227: DDL skipped due to missing object", so far OK.
However, when I try to create index on this materialized view, on production database SQL Apply stops at this point, because materialized view does not exist on standby.
Any clues why SQL apply doesn't stop on one standby but on the another standby database it stops after the same statement?
Are there any parameters or smth for this?
Thanks

yes, they are both same version and compatible parameter is the same - 11.1.0, they should be created same way on both.
only difference - prod is on solaris, test is on linux.
Problem in this case is not with mviews, but in fact, that if we have some table which is skipped and some index or other object is added on primary, SQL apply stops on standby.
Anyway, what should be the default action if SQL apply encounters an error - is it stopping apply ?

Standby database recovery error

Dear All,
When Im trying to apply redologs for my standby database, the following error is coming up
ORA-00279: change 276067636 generated at 08/22/2010 05:03:25 needed for thread 1
ORA-00289: suggestion : /oracle/BWP/oraarch/BWParch1_30490_684267445.dbf
ORA-00280: change 276067636 for thread 1 is in sequence #30490
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 32769 change 276075175 time 08/22/2010 05:03:49
ORA-00334: archived log: '/oracle/BWP/oraarch/BWParch1_30490_684267445.dbf'
ORA-01112: media recovery not started
Could you please help out.
Thanks n Regards,
KK

Hi Stefan,
Oracle data guard is implemented by one of the expert on the same.
The following is result of the command you listed.
NAME                                 TYPE        VALUE
log_archive_dest                     string      /oracle/BWP/oraarch/BWParch
log_archive_dest_1                   string
log_archive_dest_10                  string
log_archive_dest_2                   string
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
log_archive_dest_7                   string
log_archive_dest_8                   string
log_archive_dest_9                   string
NAME                                 TYPE        VALUE
log_archive_dest_state_1             string      enable
log_archive_dest_state_10            string      enable
log_archive_dest_state_2             string      defer
log_archive_dest_state_3             string      enable
log_archive_dest_state_4             string      enable
log_archive_dest_state_5             string      enable
log_archive_dest_state_6             string      enable
log_archive_dest_state_7             string      enable
log_archive_dest_state_8             string      enable
log_archive_dest_state_9             string      enable
Thanks,
Anees

DG standby db recovery mode idle, and lag for days.

We have a RAC 2 node primary and 2 node RAC standby qa environment in redhat linux.
two nights ago, some maintenance caused primary down, and db failed over to standby. and now I found out by dgmgrl the following error:
DGMGRL> show configuration
Configuration - oraqa_dg
Protection Mode: MaxPerformance
Databases:
orasqa - Primary database
Error: ORA-16810: multiple errors or warnings detected for the database
oraqa - (*) Physical standby database
Warning: ORA-16829: fast-start failover configuration is lagging
Fast-Start Failover: ENABLED
Configuration Status:
ERROR
DGMGRL> failover to oraqa
Performing failover NOW, please wait...
Error: ORA-16600: not connected to target standby database for failover
Failed.
Unable to failover
DGMGRL> switchover to oraqa
Performing switchover NOW, please wait...
Error: ORA-16810: multiple errors or warnings detected for the database
Failed.
Unable to switchover, primary database is still "orasqa"
I started recover managed standby database using current logfile disconnect;
and see one one node MRP process running, but other node not.
and recover mode is idle ,and no media recovery based on alert logs.
LOGS TIME
Last applied : 21-FEB-13:01:16:34
Last received : 21-FEB-13:01:16:34
NAME VALUE UNIT
apply finish time day(2) to second(3) interval
apply lag day(2) to second(0) interval
estimated startup time 32 second
transport lag day(2) to second(0) interval
Time Computed: 02/22/2013 15:23:10
How do I get the media recovery started?
Another issue I found out through crsctl stat res, the db on standby shows intermedia status.
ora.oraqa.db
1 ONLINE INTERMEDIATE oracle02 Mounted (Closed)
2 ONLINE INTERMEDIATE oracle03 Mounted (Closed)
Please advice what I can do from this point.
Thanks in advance.

We have a RAC 2 node primary and 2 node RAC standby qa environment in redhat linux.
two nights ago, some maintenance caused primary down, and db failed over to standby. and now I found out by dgmgrl the following error:Here failover initiated and now standby(oraqa) become new primary.
Have you configured flashback on primary database?
SQL> select flashback_on from v$database;
If you configured Flashback, Then reinstate the failed primary database as a standby database of the new primary database.
Startup failed primary to MOUNT status and
DGMGRL> REINSTATE DATABASE 'orasqa';
DGMGRL> failover to oraqa
Performing failover NOW, please wait...
Error: ORA-16600: not connected to target standby database for failover
Failed.
Unable to failoverWhen you try to perform failover, you have to check the database_role and resetlogs_change# from v$database (and) you must check broker log file for errors what happened exactly.
DGMGRL> switchover to oraqa
Performing switchover NOW, please wait...
Error: ORA-16810: multiple errors or warnings detected for the database
Failed.
Unable to switchover, primary database is still "orasqa"To perform failover, They both were sync?
they both are same resetlogs_change#? because FSFO initiated and there is no standby database to perform switchover.
I started recover managed standby database using current logfile disconnect;
and see one one node MRP process running, but other node not. I suggest you to gather below information from primary and standby.
SQL> select db_unique_name,database_role,resetlogs_change# from v$database;
From primary:
http://www.oracle-ckpt.com/script-to-monitor-primary-and-standby-databases/

Bootmgr is missing message after stopping recovery disk

I have an HP G72 series laptop with Windows 7. I took the laptop in for service and was told the hard drive was bad. They replaced the hard drive and gave me the information to order the recovery disk from HP. I put in disk 1 and it started out OK. It got to the second check mark at around 33% complete and stated 0 minutes remaining on the time. It sat there and did not move for hours. It kept making beeping noises.I got an error something about E ....... not finding C..... (or something i don't remember now). It had only one button to choice and it was OK to retry. I did that 3 times. I tried to do the next button and cancel button but system wouldn't do anything. The disk would not even eject out of laptop. I had to do a hard shut down by pressing the on/off key. When i turned it back on I am now getting BOOTMGR is missing, press Ctrl+Alt+Del to restart. I did that and it is just a continous loop. I have read other articles about doing all the F keys and none of them work. When I turn it back on and hold down the keys nothing happens and the BOOTMGR message comes back up. I tried putting in the disk 1 again and it doesn't do anything either. PLEASE HELP!! Is there an error in the service centers installation of the hard drive? What else can I try?

Hi
1) Start you system keep tapping F10 or F2 this will take to Bios page or F2 diagnosis page there you will find HDD test check if HDD is getting detected.
2) If not detected please reseat the HDD then check if you have the same issue then you need to replace the MB as HDD controller is bad.
3) If HDD test detected and test passed reseat the HDD once again and then try to reinstall OS back using Recovery disc still does not work order for a set of RCD again.
As per my knowledge this is best solution provided.
Regards
Manjunath
Let us know how it goes!
"I work for HP."
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****
Regards
Manjunath

Standby DB recovery in case of block corruption

Hi all,
I have a question,can we recover the physical standby database if we take rman backup of rpimary db and restore it to the standby db.Please suggest me...

I have checked it through rman on the primary db and not found any block corruption....
run {
       allocate channel d1 type disk;
       allocate channel d2 type disk;
       backup check logical validate database;
       release channel d1;
       release channel d2;
       }but i want ot forst test it on the test server but i don't know how to corrupt the block corruption i have opened the datafile and entered some character but i am getting other error not block corruption actually i want to test the sam scenario so that i will be confident while resotring the primary database to standby database.....
Edited by: user00726 on Feb 20, 2009 12:10 AM

Logical Standby Stops Applying Up to a Point 10GR2

Hi, I'm running a standby on 10.2.0.2
There are no sequence gaps. I registered all the datafiles so it sees the ones before and after, yet in OEM it shows this:
Log     Status                                      ResetLogs ID # First Change # (SCN) Last Change # (SCN) Size (KB)
35334 Committed Transactions Applied 688864038     4819403033                 4819404135               10782
35335 Partially Applied                         688864038     4819404135                4819404151                92
35336 Not Applied                                688864038     4819404151                4819404179                87
Alert log:
ora-01281 scn range specified is invalid.
I have tried doing a recover until scn # to no avail.

Hello;
I believe i would review and follow this Oracle document:
(UNREGISTER logfile On Logical Standby (Doc ID 1416433.1))
Best Regards
mseberg

Standby stopped recovery

Similar Messages

Maybe you are looking for