Recovery is slow on physical standby
When delete stmts are issued on primary, resync/recovery process on standby side is very slow. Logs are shipped fine and fast , but recovery process is slow. Is there some configuration needs to be updated?
Normall all other dmls are fast in the resync process.
OS: RHEL5
Primary : RAC
Standby: Phy. standby on standalone
declare
vthread# NUMBER;
vsequence# NUMBER;
vfirst_time DATE;
vname VARCHAR2(513);
vapplied VARCHAR2(3);
vdest_id NUMBER;
vsysdate date := sysdate ;
cursor lgsarcchk is
select thread#,sequence#,first_time,name,applied from V$ARCHIVED_LOG
where trunc(first_time) >= trunc(sysdate-3)
and applied='YES'
order BY first_time ;
begin
for lgsarc in lgsarcchk
loop
if lgsarc.applied = 'YES' then
dbms_output.put_line('Thread#'||lgsarc.thread#||' sequence# '|| rpad(lgsarc.sequence#,45)||' Status => '||lgsarc.applied||' applied at '||lgsarc.first_time);
end if;
end loop;
end;
im using above cmd to check and also alert log of standby prints when it applies.
Alert log msg:
Media Recovery Log /MOUNTPOINT/DBNAME/ARCHIVELOGNUMBER.arc
Similar Messages
-
Recovery very very slow on the physical standby recently
The standby was running fine for over a year. But recently the recovery became very slow. It took over an hour to apply one archivelog causing the standby falling behind. What could be the cause and solution?
Thanks!Before I go further with my comment, I would recommend to open a SR with Oracle and have them help you to resolve the problem.
You said that the archive logs are being applied, however the apply rate is slow? Is this true?
Since you are applying the archive logs, it looks like your protection mode is set to ASYNC Maximum Performance.
Can you check if all the logs are being shipped to the standby without any problem?
There are couple of DG healthcheck scripts available on Metalink.
Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
Can you run those scripts? If you feel comfortable, publish the output of the scripts on this tread, otherwise review them. They may give you some clue on what might be going on.
Also check v$dataguard_status view.
select *
from v$dataguard_status
where severity in ('Error','Fatal')
order by timestamp; If you are not able to run the scripts due to database hanging state, as you described in your last post, try to determine why the database is hanging.
In this kind of situations I usually use HANGANALYZE that will generate trace files for all the running processes. It may take a while until you review these files. Especially pay attention to the RFS process.
SQL>oradebug setmypid
SQL>oradebug unlimit;
SQL>oradebug hanganalyze 266For more information on how to use HANGANALYZE refer to Metalink Notes: 175006.1, 452358.1 and 61552.1
However, if you haven't used oradebug before or don't feel comfortable using it, you better don't do that and wait on instructions from Oracle.
Also, as always, check the alert log file and the data guard log file (drc<sid>.log).
Cheers,
Edited by: tekicora on Dec 31, 2008 10:22 AM -
Corrupting the block to continue recovery in physical standby
Hi,
Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
DB Version: 11.1.0.7
Database Type: Data Warehouse
The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
Fri Feb 11 05:50:59 2011
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
Fri Feb 11 05:52:06 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
Fri Feb 11 05:52:10 2011
Trace dumping is performing id=[cdmp_20110211055210]
Fri Feb 11 05:52:14 2011
Sweep Incident[631460]: completed
Fri Feb 11 05:52:17 2011
Slave exiting with ORA-10562 exception
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
ORA-10564: tablespace <tablespace name>
ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
oracle@<server>:[~] $ cat dbv_file_36.log
DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
DBVERIFY - Verification complete
Total Pages Examined : 3840000
Total Pages Processed (Data) : 700644
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 417545
Total Pages Failing (Index): 0
Total Pages Processed (Other): 88910
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 2632901
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3811184883 (1.3811184883)
Any help is really appreciated. I hope to hear feedback from you.
Thanksdamorgan, i understand the opinion.
just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation -
Related to recovery in Physical standby database in RAC
In Physical Standby database all instance involved in recovery processes or any one instance will be their in in recovery mode
If is like this another instance will be for high availabily can any one in forum explain me it will be help fullWith your Primary database being RAC, the Physical Standby does not have to be RAC, although, obviously it would be preferred to have scalability as required at a DR site.
Whether your Standby is RAC or non-RAC, the automatic Recovery that is done at the Standby is done by one instance only. It would be applying the ArchiveLogs from all the threads (i.e. instances) of the Primary.
Database Recovery is always done by a single instance.
Hemant K Chitale
http://hemantoracledba.blogspot.com -
Physica standby recovery problem
Hi,
I am trying to recover physical standby database manually
I am getting below error:
alter database recover standby database parallel (degree 32);
alter database recover standby database parallel (degree 32)
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
I have tried to cancel managed recovery, but no managed recovery is active.
alter database recover managed standby database cancel;
alter database recover managed standby database cancel
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active
select distinct recovery_mode from v$archive_dest_status;
RECOVER
IDLE
Please help me to resolve this. Thanks in advance.
regards,
NarendraApparently this is bug 5084496, related to parallel recovery on 10.1 and below (ML note 361883.1). You may avoid this bug if you don't use parallel recovery. It looks like there are no one-off patches available, so you are stuck with either serial recovery or upgrade to 10.2 or higher :-(
Regards,
Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net -
Cancelling recovery on Physical standby.
Hi ALL,
recovery is cancel and i am looking following error in alert log file
how can solve this problem
database version 11gr2
aix 6.1 64 bit
physical standby datbase
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)You cancelled recovery or it is terminated?
Try to start once again, I have seen some listed bugs with the same error but those are applicable for 11gR1, but you are in 11gR2.
Refer ORA-03170: Deadlocked on Readable Physical Standby [ID 846324.1], better you submit an SR to Support.
Thanks. -
Error while trying to open physical standby database - (DATA GUARD)
Hi Everyone,
I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
Primary Database spec: (2 Node Rac on ASM)
Oracle Version : 10.2.0.3.0
O/s : HP-UX B.11.23
Standby Database spec: (Single Node)
Oracle Version : 10.2.0.3.0
O/s: HP-UX db01 B.11.23
Error:
alter database recover managed standby database cancel;
Database altered.
SQL> alter database open
2 ;
alter database open
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
Parameters :
log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=PROD
remote_archive_enable string true
fal_client string DPROD
fal_server string PROD1, PROD2
Steps tried so far:
Changed log_archive_dest_2 = DEFER on both the primary nodes
Standby :
startup nomount
alter database mount standby database;
alter database recover managed standby database disconnect;
alter database recover managed standby database cancel;
alter database open/readonly (tried both)
Same error.
On Primary:
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
55702
on Standby:
MAX(SEQUENCE#)
33289
Primary Database:
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
55700 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55702 13-JUN-11 13-JUN-11
60824 rows selected.
Standby Database:
SEQUENCE# FIRST_TIME NEXT_TIME
55698 13-JUN-11 13-JUN-11
55699 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
15206 rows selected.
Additional Information :
There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
Any help will be highly appreciated. Thanks in advance
SadiqHi,
Primary Database:
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
STATUS CHECKPOINT_COUNT
ONLINE 57717
ONLINE 57717
57 rows selected.
Standby Database;
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
STATUS CHECKPOINT_COUNT
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
STATUS CHECKPOINT_COUNT
ONLINE 30723
ONLINE 30723
57 rows selected.
Archieve log list :
Primary database:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 49111
Current log sequence 49111
Standby Database:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 0
Current log sequence 49111
I tried log switch multiple times in primary database i saw that its getting highlighted in standby database. -
Drop a datafile from physical standby's control file
Hi,
I am trying to create a physical standby database for my production...
1) I have taken cold backup of my primary database on 18-Nov-2013...
2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database...
When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
How to overcome this situation...
Can i delete the entry for the newly added datafile from the backup control file ?
When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be open..
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME TYPE VALUE
standby_file_management string AUTO
SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
System altered.
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME TYPE VALUE
standby_file_management string MANUAL
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
Regards,
JibuJibu wrote:
Hi,
I am trying to create a physical standby database for my production...
1) I have taken cold backup of my primary database on 18-Nov-2013...
2) I added a datafile on 19-nov-2013 ( 'O:\ORADATA\SFMS\SFMS_DATA4.DBF' )
3) Standby control file was generated on 20-ov-2013 (today) after shutting down and then mounting the primary database..
Hi,
What is your version?
If you added new datafile or created new tablespace, take backup again for restore new created standby database.
If your standby database running well, DG configuration success, then this datafile will create on standby side, too.
Set STANDBY_FILE_MANAGEMENT=AUTO best practice.
When i try to recover the newly setup standby using archive files, i am getting the following error (datafile added on 19th Nov is missing)
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ORA-01157: cannot identify/lock data file 39 - see DBWR trace file
ORA-01110: data file 39: 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
How to overcome this situation...
Can i delete the entry for the newly added datafile from the backup control file ?
Not need any delete datafile from standby side, you must recreate standby database, or you can take RMAN backup and restore to standby side again.
When i tried to delete datafile using "alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF';", it is showing that database should be open..
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME TYPE VALUE
standby_file_management string AUTO
SQL> alter system set STANDBY_FILE_MANAGEMENT=manual;
System altered.
SQL> show parameter STANDBY_FILE_MANAGEMENT
NAME TYPE VALUE
standby_file_management string MANUAL
SQL> alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
alter tablespace SFMS_BR_DATA drop datafile 'O:\ORADATA\SFMS\SFMS_DATA4.DBF'
ERROR at line 1:
ORA-01109: database not open
It is not logical, Physical standby must be bit-for-bit same with Primary database.
Regards
Mahir M. Quluzade -
Unable to open the physical standby in read only (10g)
Hi,
I m trying to create physical standby using RMAN to another server . But at the last step when trying to test Real Time Apply i m unable to open the standby in read only mode.Can Anyone please let me know whats the issue and how to resolve it
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/u01/app/oracle/product/10.2.0/oradata/test1/system.dbf'Hi,
This is a newly created standby. I created just now. Below the o/p requested
In Primary
SQL> set line 200
SQL> set pagesize 200
SQL> col message format a90
SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message from v$dataguard_status where dest_id=2;
SEVERITY ERROR_CODE TO_CHAR(TIMESTAMP,'D MESSAGE
Error 12541 04-MAR-2012 11:55:05 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error 12541 04-MAR-2012 12:00:12 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error 1034 04-MAR-2012 12:06:25 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning 3113 04-MAR-2012 13:21:24 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:21:24 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:21:24 PING[ARC1]: Error 3113 when pinging standby test1.
Warning 3113 04-MAR-2012 13:33:29 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:33:29 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:33:29 PING[ARC1]: Error 3113 when pinging standby test1.
Error 1034 04-MAR-2012 13:39:50 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Error 1034 04-MAR-2012 13:45:29 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning 3113 04-MAR-2012 13:57:56 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning 3113 04-MAR-2012 13:57:56 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3113 04-MAR-2012 13:57:56 PING[ARC1]: Error 3113 when pinging standby test1.
14 rows selected.
SQL> select ds.dest_id id
, ad.status
, ds.database_mode db_mode
, ad.archiver type
, ds.recovery_mode
, ds.protection_mode
, ds.standby_logfile_count "SRLs"
, ds.standby_logfile_active active
, ds.archived_seq#
from v$archive_dest_status ds
, v$archive_dest ad
where ds.dest_id = ad.dest_id
and ad.status != 'INACTIVE'
order by
ds.dest_id
/ 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 64
2 VALID UNKNOWN ARCH UNKNOWN MAXIMUM PERFORMANCE 3 0 64In standby
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 64
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 64
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 63
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
MESSAGE
RFS[1]: Assigned to RFS process 9880
RFS[1]: Identified database type as 'physical standby'
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_63_776981781.arc
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_64_776981781.arc
Media Recovery Waiting for thread 1 sequence 65
16 rows selected. -
Problems while creating a physical Standby
Hi,
I am trying to setup a physical standby database with oracle 10g.
I configured a specific log archive destination:
LOG_ARCHIVE_DEST_3 = 'SERVICE=ORAMPSEC REOPEN=60 MAX_FAILURE=3 LGWR SYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ORAMPSEC'
The service is reachable via network.
To establish the standby database I copied all datafiles from the primary database using scp. I also created a standby controlfile and a modified pfile. In addition I added a standby redo logfile which has the same size as the online redo log files on the primary database.
After starting the standby database in open read only mode I receive the following error message:
Database mounted.
ORA-16004: backup database requires recovery
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
I tried to recover using "recover standby database" I receive the following message:
ORA-00279: change 884348 generated at 07/18/2006 17:08:07 needed for thread 1
ORA-00289: suggestion : /oradata/ORAMPPRD/archive/1_30_595767954.dbf
ORA-00280: change 884348 for thread 1 is in sequence #30
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Although I transmitted all archived log files from the primary database the archived log file mentioned above is not available. After hitting RETURN I get this message:
ORA-00308: cannot open archived log
'/oradata/ORAMPPRD/archive/1_30_595767954.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oradata/ORAMPPRD/data/system01.dbf'
Here is a listing of all archived logfiles from the primary database:
bash-3.00$ ls -latr
total 494144
drwxr-xr-x 6 oracle oinstall 512 Jul 14 11:03 ..
-rw-r----- 1 oracle oinstall 20732928 Jul 17 11:47 1_6_595767954.dbf
-rw-r----- 1 oracle oinstall 86013440 Jul 17 13:56 1_7_595767954.dbf
-rw-r----- 1 oracle oinstall 214016 Jul 17 13:57 1_8_595767954.dbf
-rw-r----- 1 oracle oinstall 1986560 Jul 17 14:10 1_9_595767954.dbf
-rw-r----- 1 oracle oinstall 150016 Jul 17 14:10 1_10_595767954.dbf
-rw-r----- 1 oracle oinstall 504320 Jul 17 14:17 1_11_595767954.dbf
-rw-r----- 1 oracle oinstall 1807872 Jul 17 14:22 1_12_595767954.dbf
-rw-r----- 1 oracle oinstall 589824 Jul 17 14:25 1_13_595767954.dbf
-rw-r----- 1 oracle oinstall 1190912 Jul 17 14:37 1_14_595767954.dbf
-rw-r----- 1 oracle oinstall 584704 Jul 17 14:42 1_15_595767954.dbf
-rw-r----- 1 oracle oinstall 80896 Jul 17 14:45 1_16_595767954.dbf
-rw-r----- 1 oracle oinstall 6050816 Jul 17 15:08 1_17_595767954.dbf
-rw-r----- 1 oracle oinstall 4238848 Jul 17 16:04 1_18_595767954.dbf
-rw-r----- 1 oracle oinstall 4920832 Jul 17 17:21 1_19_595767954.dbf
-rw-r----- 1 oracle oinstall 1520128 Jul 17 17:30 1_20_595767954.dbf
-rw-r----- 1 oracle oinstall 360960 Jul 17 17:35 1_21_595767954.dbf
-rw-r----- 1 oracle oinstall 89186304 Jul 18 10:52
1_22_595767954.dbf
-rw-r----- 1 oracle oinstall 16216576 Jul 18 14:18
1_23_595767954.dbf
-rw-r----- 1 oracle oinstall 12288 Jul 18 14:18 1_24_595767954.dbf
-rw-r--r-- 1 oracle oinstall 2073 Jul 18 14:26 sqlnet.log
-rw-r----- 1 oracle oinstall 14387200 Jul 18 16:56
1_25_595767954.dbf
-rw-r----- 1 oracle oinstall 116736 Jul 18 16:58 1_26_595767954.dbf
-rw-r----- 1 oracle oinstall 1536000 Jul 18 17:04 1_27_595767954.dbf
-rw-r----- 1 oracle oinstall 156672 Jul 18 17:05 1_28_595767954.dbf
drwxr-xr-x 2 oracle oinstall 1024 Jul 18 17:08 .
-rw-r----- 1 oracle oinstall 65536 Jul 18 17:08 1_29_595767954.dbf
Nothing known about the *30*dbf file.
Although there still seems to be something wrong, the archived log file transmission seems to work since there is no error reported on the log archive destination:
SQL> select status, error from v$archive_dest where dest_id = 3;
STATUS ERROR
VALID
And after I manually force a log switch I see that archived redo logs were applied on the standby database:
select sequence#, applied from v$archived_log order by sequence#;
SEQUENCE# APPLIED
27 YES
28 NO
28 YES
29 NO
29 YES
Unfortunately because of the recovering problem I cannot open the database to see if the changes were applied. So my first question is, how can I get the standby database completely recovered ??
In addition to this I was expecting that the changes to the standby database were made immediately since I choosed LGWR sync but I have to manually force the logfile switch. As I already mentioned a standby redo log file is available as well.
Thanks for your help,
Philipp.Hi,
since it does not seem to work with just copying the datafiles I switched to RMAN. I created a full database backup from Enterprise Manager. Similiar to http://dizwell.com/main/content/view/81/122/1/1/ I tried to duplicate the database to the standby instance (running on a different server). But unfortunately I receive error messages that the files, previously created, cannot be found:
channel d1: starting datafile backupset restore channel d1: specifying datafile(s) to restore from backup set restoring datafile 00001 to /oradata/ORAMPPRD/data/1.dbf restoring datafile 00002 to /oradata/ORAMPPRD/data/2.dbf restoring datafile 00003 to /oradata/ORAMPPRD/data/3.dbf restoring datafile 00004 to /oradata/ORAMPPRD/data/4.dbf channel d1: reading from backup piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19870: error reading backup
piece /opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1
ORA-19505: failed to identify file
"/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1"
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory Additional information: 3 failover to previous backup
But when I crosscheck my backup inside RMAN it clearly shows the backup files:
RMAN> crosscheck backup;
backup piece
handle=/opt/oracle/ora10/product/10.2.0.1.0/dbs/0bhoiq60_1_1 recid=7
stamp=596207811
crosschecked backup piece: found to be 'AVAILABLE'
I already checked the file permissions, everybody on the system is able to access this file.
Do you know what is going wrong here ??
Cheers,
Philipp. -
Problem in recover physical standby database(Data Guard) by rman
Hello to all
I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
scenarios is follow
1- In rman I create a backup of standby database by this command:
backup database plus archivelog delete all input;
2- I run this comman in rman for recover standby database
run{
2> set until scn 1392701;
3> restore database;
4> recover database;
5> }
(1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
but RMAN result is like this:
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1
tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
unable to find archive log
archive log thread=1 sequence=118
RMAN-03002: failure of recover command at 12/13/2008 05:14:13
RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700
3- then I decline 1392701 to 1392700 and i run this command
run{
2> set until scn 1392700;
3> restore database ;
4> recover database;
5> }
executing command: SET until clause
Starting restore at 13-DEC-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from
backup set
restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
Finished restore at 13-DEC-08
Starting recover at 13-DEC-08
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 116 is already on disk as
file /u01/app/oracle/oradata/archive/1_116_666786084.arc
archive log thread 1 sequence 117 is already on disk as
file /u01/app/oracle/oradata/archive/1_117_666786084.arc
archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
sequence=116archive log
filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
thread=1 sequence=117Oracle 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/sari/system01.dbf'
media recovery complete, elapsed time: 00:00:10
Finished recover at 13-DEC-08
4- if I run
run{
restore database;
recover database;
I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700)
5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
do you know what is problem
thanks
Edited by: ARKH on Dec 12, 2008 11:06 PMhi
I myself have found the solution , when I recover the standby database
it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
seq 118 lowscn 1392700) but if I begain redo apply before open the database
and I wait till all redo apply process start and communication between the
standby database and the primary database start, then I can
open the standby database and no error will raise
but if befor restarting redo apply I open the database I'll recieve the
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
thanks -
Issue on physical standby database
Hi
I've a problem on standby database.
I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
I get following message in my alert log
WARNING! Recovering data file 88 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
how can I fix this now.
We keep physical standby database 2 day behind, and apply logs manually.
Physical standby database is maintained manually.
Could someone help me in getting out of this problem.
Oracle 9.2.0.7
solarisVersus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
Note:
If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
Specifying a Time Delay
You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
Canceling a Time Delay
You can cancel a specified delay interval as follows:
For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
For logical standby databases, specify the following SQL statement:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
Section 12.8, "Using a Physical Standby Database with a Time Lag"
Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement -
Issue with physical standby database not in sync with primary
Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
RakeshHI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL> -
Logical and Physical Standby Practice
Hello Gurus
I am now attempting to practice Oracle Data Guard and in this direction I understand since 10g we have logical standby server as well as a physical standby server. While I am gathering information and knowledge about the data guard as is and varisous modes and types possible with oracle 10g and 11g in specific, an attempt to upgrade my self and learn these set-ups and understand them in detail.. I come to you for some guidence..
I am referring to Oracle Documentation for these details. At the same time I also approach you to share your experiences .. may be a link apart from the documentation of oracle which you might want to refer me to use as a quick reference.. some thing that a person like me .. fairly new to this set-up understand it and then attempt to come up with one..
This is for my practise and learning purpose.
Sarat.Logical Standby was already introduced in 9i. It differs from physical standby in the way, the redo protocol, transmitted from the primary, gets used to actualize the standby. With logical standby, you have SQL APPLY - basically, we try to generate the same SQL that was done on the primary from the redo protocol that was written on behalf of that SQL on the primary. That SQL then is done on the OPEN instance at the logical standby.
In case of a physical standby, the redo protocol from the primary is used to do RECOVERY - called REDO APPLY - to actualize the standby.
Since 10g, the sames protection levels can be achieved with logical or physical standby.
Drawback of logical standby: Not all kinds of SQL and all datatypes are supported
Drawback of physical standby: It is mounted (versions before 11g) while being recoverd - or in 11g, REDO APPLY in READ ONLY status is possible but comes with an extra charge (ACTIVE DATA GUARD feature).
If you look on my Blog, I have some examples about creating physical & logical standby DBs
Kind regards
Uwe
http://uhesse.wordpress.com -
Is that possible to convert logical standby to physical standby ?
Hi guys,
My steps for testing as below:
1.create a primary database
2.duplicate a physical standby database;
3.turn on flashback on both databases.
4.record SCN xxx on physical standby database.
5.convert physical standby to logical standby (using keep identity statement)
6.flashback to logical standby to xxx
7.convert logical standby to physical standby
8.using real time apply
I got errors:
Fast Parallel Media Recovery enabled
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery waiting for new incarnation during transient logical upgrade procedure
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Managed Standby Recovery not using Real Time Apply
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Errors appears every 10 seconds. Seems MPR0 is waiting for new incarnation for a long time. So am I.
Standby database incarnation:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORA11GR1 3853851354 CURRENT 1 08/09/2013 01:02:18
2 2 ORA11GR1 3853851354 ORPHAN 2127877 08/28/2013 19:22:01 BGVHello;
Because of limitations for specific data types and objects with a logical database I going to say no.
Best Regards
mseberg
Maybe you are looking for
-
How do I set up automatic downloads so that i only get content from specific devices?
Hello! I was wondering if there was a way I could set up automatic downloads so I only get content purchased from certain devices. I have a MacBook Pro and a ipod touch. I share an apple id with my family for itunes but have my own apple id for iclou
-
Needs some Advice on How-to, Real time Price Quote Page?
I need to create a page that gives a real time price quote. I would like to be able to allow the end user to select the an option and in real time update the price and up date a running total. I have looked around for some extentions but have not
-
What really is an ADFContext?
I am using the ADFContext to get/put some session variables. I spent one whole day behind a problem I have in some circumstances. Apparently, even for session variables, there might be different Contexts according to which point you call ADFContext f
-
Webcenter Sites Installation fail during deployment
Hi I have been trying to do a proof of concerpt with Webcenter Site on Weblogic 10.3.6 on windows 7, it installs fine but failes with the following error during deployment An error occurred during activation of changes, please see the log for details
-
Can't find movies on sd card from Sony nex-5
Recently I've recorded some videos while on vacation and a lot of pictures on the same sd card using a Sony NEX-5. When I've got home and tryed to upload it to my iPad (3rd generation) the pictures jumped right out to upload, but, for Some reason I c