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

Similar Messages

Reg: Exporting the data from the Physical Standby database system.

Hello all,
We have an oracle standard edition one 11gR1 environment, in which i need to export the data from the physical standby system.
So can anyone suggest me, How to do it safely (mount state).
Regards,
Konda.

Hi,
You can use "exp" utility to export the database from a read only database whereas you can't export the read only database using "expdp".
Since you are using version 11g, it is not advisable to use exp. You can convert your standby to snapshot database, open read, write and export the database using expdp and then again convert it to standby.
This is a very easy process which we follow in our company to do testing when required.
Follow note 11g Using Snapshot Standby Database. (Doc ID 443720.1) for converting and usage.
Thank you!!

Changing the dbid of the physical standby database...

hai...
i am new to dataguard.
can we change the dbid of the physical standby database?
and if it is possible what would be the effect on primary database at the time of sending archive log files.
why should we change the dbid of the logical standby database?and why shouldn't for physical standby?
please guide me...
v.s.srinivas potnuru

A physical standby is a bit for bit copy of the primary database. It is not opened read-write. It is the same identical database as your primary.
Consider a logical standby as an independent database that just happens to have transactions that emanate on the primary database applied to it, via SQL APPLY.
A logical standby can deviate quite markedly from the primary and you can skip tables from being updated on the standby. You can also create objects that exist solely within the logical standby (i.e. more indexes for reporting).
jason.
http://jarneil.wordpress.com

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.

RMAN backup on the physical standby database.

Hello,
11.2.0.3 EE database. Is it a requirement to open the database in read only mode in order to take a hot backup?
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER DATABASE OPEN READ ONLY;
I've initiated a rman backup without opening the db in read only and the following output is so far:
RMAN> backup format '/dbstor2/LTS/LTS_rman/%d_set%s_piece%p_%T_%U' check logical database plus archivelog;
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
I plan on taking this backup and using it to refresh our Dev and QA dbs. Do you see any issues with taking a backup without opening the db in ready only mode?
-SteveV

No we are not using Active Dataguard. An issue I am investigating is why can't I perform an archivelog backup from the standby?
RMAN> backup archivelog all format '/dbstor2/LTS/LTS_rman/arc.rman.bak';
Starting backup at 15-OCT-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=603 device type=DISK
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 15-OCT-12

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.
Thanks

damorgan, 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 full

With 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

AIR application performance is very bad(slow)

I have an AIR application developed using Flash CS3. The
issue is application performance is very bad(slow) when the OS
(Windows XP) display property setting is in 16 bit color mode. When
the display property setting is changed to 32 bit color mode
applications performance is good and faster.
Application has used lots of color gradients, tween
animations.
System Configuration:
Windows XP (SP2)
1 GB RAM
INTEL P4 , 1.5 GHz Processor Speed.
Can any one explain that is there any issue with Flash Player
or AIR runtime.

quote:
Originally posted by:
cyberKafka
I also understand that creating windows via AS (not MXML)
could help a bit (apparently a lot with memory allocation. have not
tested myself thou.)
Do you have a link for any more info on this? Sounds
interesting.

How to change the database character set on physical standby database?

Hi,
We have a database with character set WE8ISO8859P1 and migrated the character set to WE8MSWIN1252 using csscan/csalter scripts. This database has a physical standby database setup also and after the migration, the physical standby database is still showing the character set as WE8ISO8859P1. How can I change the characterset on the physical standby? I raised a Service Request with Oracle, and they said that recreating the standby database is the only supported way of changing the char set on the standby database. Is this true?
Thanks,
Sreekanth

Thank you, Robert, for your reply.
The standby is in sync with the primary.
see below
SYS@sisprod>select * from v$dataguard_stats;
NAME VALUE UNIT TIME_COMPUTED
apply finish time +00 00:00:00.0 day(2) to second(1) interval 12-NOV-2009 14:02:46
apply lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
estimated startup time 11 second 12-NOV-2009 14:02:46
standby has been open N 12-NOV-2009 14:02:46
transport lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
SYS@sisprod>
I am selecting from v$nls_parameters;
I don't know how to restore the controlfile from primary. Could you please tell me how to do it?
Thanks,
Sreekanth

Implementation of ORACLE9i RMAN physical standby database`

Sir's,
How to implement RMAN in the physical standby database

Hi Ashu Goel,
Can u let me know any thing abot the prerequistw of implementation with the configuration settings of the above said.If I understand you correctly you want to use rman to backup an already existing dataguard setup.
Doing this would be very similar as a normal rman backup with the limitation you have to stop the recovery during the backup window and run the backup in mount mode.
To make a consistent backup of the standby database, make sure that the last shutdown of the standby database was clean and that it was not placed in recovery mode after that time, and then mount the control file. For example:
sqlplus SYS/oracle@sbdb1 <<EOF
SHUTDOWN IMMEDIATE
STARTUP NOMMOUNT PFILE=initSTANDBY.ora
ALTER DATABASE MOUNT STANDBY DATABASE;
EOF
You can back up the standby database when it is in any other mode, but the backups will be inconsistent.
Start RMAN and connect to the standby database with the TARGET keyword (not the AUXILIARY keyword) and the recovery catalog database. You must be connected to the recovery catalog. For example, enter:
% rman TARGET SYS/oracle@sbdb1 CATALOG rman/cat@catdb
If do not have automatic channels configured, then manually allocate one or more channels of type DISK or sbt. Note that you are connected to the standby host, so the backups are made by server sessions on the standby (not the primary) host.
This example backs up all the standby datafiles as well as the control file and archived logs by using automatic channels:
BACKUP DATABASE PLUS ARCHIVELOG;
Regards,
Tycho

Data Guard - MRP stuck issues on a physical standby database

Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?

Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

Log apply was not sync in physical standby

Hi Gurus,
I am very new to Data Guard , here are few questions , please answer , so that my understanding about DR could be very clear?
This is physical standby database running maximum performance mode , with ARCH as transport service
1.explain below in detail ( standby)
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 60099
Next log sequence to archive 0
Current log sequence 60178
2.where this information is picked from , how it will be updated in stand by before the archived log reached this standby site ?
3.Why there will be more than 1 entry for sequence in v$archived_log (primary) ?
4. One scenario ,
select registrar , sequnce# from v$archived_log ; (primary)
ARCH 60109
ARCH 60171
LGWR 60172
60172 entered the standby site even before the archived logs 600109-601171 reach standby, because REGISTRAR is LGWR
5.Log apply is taking to long time( in-memory ) i.e .sequence is not changing for long time ? How to resolve this?
Please feel free to revert , if any question is unclear
Thanks,
Uday

Hello;
1.explain below in detail ( standby)
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 60099
Next log sequence to archive 0
Current log sequence 60178Not sure how to comment. Try query in question 2.
2.where this information is picked from , how it will be updated in stand by before the archived log reached this standby site ?Would use something else. Try this query :
http://www.visi.com/~mseberg/monitor_data_guard_transport.html
3.Why there will be more than 1 entry for sequence in v$archived_log (primary) ?Because with Data Guard you have more than one destination for Archive so v$archived_log accounts for them all.
4. One scenario ,
select registrar , sequnce# from v$archived_log ; (primary)
ARCH 60109
ARCH 60171
LGWR 60172
60172 entered the standby site even before the archived logs 600109-601171 reach standby, because REGISTRAR is LGWRNot sure how to comment, what are you trying to do?
5.Log apply is taking to long time( in-memory ) i.e .sequence is not changing for long time ? How to resolve this?
Please feel free to revert , if any question is unclearWhat is a long time? If you force a few log switches on the Primary does it take a long time for each one? Or longer?
Best Regards
mseberg

How to check data in physical standby database?

Hi!
I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
thankS

I hope the following will help
Verifying the Physical Standby Database
==========================================
Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
Step 1 Identify the existing archived redo logs.
On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
3 rows selected.
Step 2 Archiving the current log.
On the primary database, archive the current log using the following SQL statement:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Step 3 Verify that the new archived redo log was received.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
4 rows selected.
The logs are now available for log apply services to apply redo data to the standby database.
Step 4 Verify that the new archived redo log was applied.
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
2 ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.

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
Sadiq

Hi,
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.

Physical standby database implementation

Hi!
I am trying to implement a Physical standby database, I have already done it with both the primary and secondary in the same server and successfully shipped the logs and have it configured using Data Guard.
But Now I am trying to implement the Physical standby in a separate server, but the logs are not getting shipped, I am using Oracle 9i Enterprise edition. I have checked all the steps, but not able to find the reason, why the logs are not getting shipped to the standby.
Also I am not able to discover the Primary node from the Standby and I have Windows 2003 server in my standby and Windows XP Prof. in the Primary, Is this the reason, why my logs are not getting shipped?
Please help. Thanks in Advance.
Radhika

Hi!,
Thanks for ur response, I am posting my alert log here... can u please help me... I probably think it is the OS issue too... Your inputs are greatly appreciated...
Thanks
Radhika
Fri Feb 10 18:21:19 2006
Errors in file d:\oracle\admin\bsnl\bdump\bsnl_arc0_1668.trc:
ORA-12535: TNS:operation timed out
Dump file d:\oracle\admin\bsnl\bdump\alert_bsnl.log
Mon Feb 13 11:04:59 2006
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 1, CPU type 586
Mon Feb 13 11:04:59 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 50331648
large_pool_size = 8388608
java_pool_size = 33554432
control_files = D:\oracle\oradata\BSNL\CONTROL01.CTL, D:\oracle\oradata\BSNL\CONTROL02.CTL, D:\oracle\oradata\BSNL\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 25165824
compatible = 9.2.0.0.0
log_archive_start = TRUE
log_archive_dest_1 = location=D:\oracle\oradata\BSNL_LOG mandatory
log_archive_dest_2 = service=dbabsnl
log_archive_dest_state_2 = ENABLE
db_file_multiblock_read_count= 16
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 10800
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = BSNL
dispatchers = (PROTOCOL=TCP) (SERVICE=BSNLXDB)
job_queue_processes = 10
hash_join_enabled = TRUE
background_dump_dest = D:\oracle\admin\BSNL\bdump
user_dump_dest = D:\oracle\admin\BSNL\udump
core_dump_dest = D:\oracle\admin\BSNL\cdump
sort_area_size = 524288
db_name = BSNL
open_cursors = 300
star_transformation_enabled= FALSE
query_rewrite_enabled = FALSE
pga_aggregate_target = 25165824
aq_tm_processes = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
QMN0 started with pid=9
Mon Feb 13 11:05:07 2006
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
Mon Feb 13 11:05:08 2006
ARC1: Archival started
Mon Feb 13 11:05:09 2006
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC1: Thread not mounted
Mon Feb 13 11:05:09 2006
ARC0: Thread not mounted
Mon Feb 13 11:05:10 2006
alter database mount exclusive
Mon Feb 13 11:05:16 2006
Successful mount of redo thread 1, with mount id 1399936614.
Mon Feb 13 11:05:16 2006
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Feb 13 11:05:16 2006
alter database open
Mon Feb 13 11:05:18 2006
Beginning crash recovery of 1 threads
Mon Feb 13 11:05:19 2006
Started first pass scan
Mon Feb 13 11:05:21 2006
Completed first pass scan
3956 redo blocks read, 68 data blocks need recovery
Mon Feb 13 11:05:21 2006
Started recovery at
Thread 1: logseq 18, block 9151, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 18 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\ORADATA\BSNL\REDO02.LOG
Mon Feb 13 11:05:23 2006
Ended recovery at
Thread 1: logseq 18, block 13107, scn 0.967486
68 data blocks read, 68 data blocks written, 3956 redo blocks read
Crash recovery completed successfully
Mon Feb 13 11:05:28 2006
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 advanced to log sequence 19
Thread 1 opened at log sequence 19
Current log# 3 seq# 19 mem# 0: D:\ORACLE\ORADATA\BSNL\REDO03.LOG
Successful open of redo thread 1.
Mon Feb 13 11:05:33 2006
SMON: enabling cache recovery
Mon Feb 13 11:05:33 2006
ARC0: Evaluating archive log 2 thread 1 sequence 18
ARC0: Beginning to archive log 2 thread 1 sequence 18
Creating archive destination LOG_ARCHIVE_DEST_2: 'dbabsnl'
Mon Feb 13 11:05:36 2006
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Mon Feb 13 11:05:36 2006
SMON: enabling tx recovery
Mon Feb 13 11:05:36 2006
Database Characterset is WE8MSWIN1252
Mon Feb 13 11:05:47 2006
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Mon Feb 13 11:05:55 2006
ARC0: Error 12535 Creating archive log file to 'dbabsnl'
Mon Feb 13 11:05:56 2006
Errors in file d:\oracle\admin\bsnl\bdump\bsnl_arc0_1596.trc:
ORA-12535: TNS:operation timed out
Creating archive destination LOG_ARCHIVE_DEST_1: 'D:\ORACLE\ORADATA\BSNL_LOG\ARC00018.001'
ARC0: Completed archiving log 2 thread 1 sequence 18

Recovery very very slow on the physical standby recently

Similar Messages

Maybe you are looking for