Next log sequence to archive in Standby Database (RAC Dataguard Issue)

Hi All,
I just had implemented Data Guard in our server. My primary Database is RAC configured, but it is only single node. The other Instance was removed and converted it to Developement Instance. For the reason I kept the primary as RAC is when I will implement dataguard, my Primary Database is RAC with 7 nodes.
The first test is successful, and I was able to "switchover" from my primary to standby. I failed in the 'FAILOVER" test.
I restore my primary server and redo the setup.
BTW, my standby DB is physical standby.
When I try to switchover again and issue archive log list, below is my output.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 0*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
MOUNTED PHYSICAL STANDBY
===============================================
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
*Next log sequence to archive 38*
Current log sequence 38
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ WRITE PRIMARY
In my first attempt to switchover before I failed in "FAILOVER" test, I also issue +archive log list+ in both primary and standby database, and if I remember it right, next log sequence on both should be identical. Am I right on this?
Thanks in Advance.
Jay A

Or Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence?

Similar Messages

Next log sequence to archive is different

Hi,
I have doubt on standby (DR) concept.
I can see that in my standby database next log sequence to archive shows 0.
Is this ok or something is wrong?
PRODUCTION
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 2631
Current log sequence 2631
STANDBY
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u006/app/archive/XXPROD/arch
Oldest online log sequence 2627
Next log sequence to archive 0
Current log sequence 2631

Hello;
Short answer no nothing is wrong.
Its the same on mine :
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     5069
Next log sequence to archive   0
Current log sequence           5071
SQL> I use v$archived_log to check mine standby :
SELECT name as STANDBY, SEQUENCE#, applied, completion_time from v$archived_log WHERE DEST_ID = 2 AND NEXT_TIME > SYSDATE -1;Against my Primary I get the last log :
select max(sequence#) from v$archived_log where NEXT_TIME > sysdate -1;Data Guard has a set of v$ views to check results, 8archive log list8 isn't so good since with Data Guard you have two copies of the same database in different roles.
Another query I like is : (Run on the standby)
select process, status, sequence#, block# from v$managed_standby;The Oracle doc E10700-02 has several example in chapter 9 "Monitoring Primary, Physical Standby, and Snapshot Standby Databases"
Also section "3.2.7 Verify the Physical Standby Database Is Performing Properly"
Best Regards
mseberg

Logs are not archived at Standby site on same server

Hello all,
I am using 11gR2 on Redhat Linux 5
i have a testing to do in which i have created my standby database through rman duplicate command
i have my standby db on the same machine.
my primary database is : prod
standby database is : std
on primary site:
SQL> select database_role,open_mode,name from v$database;
DATABASE_ROLE OPEN_MODE NAME
PRIMARY READ WRITE PROD
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 53
Next log sequence to archive 55
Current log sequence 55
but the archiving is not being done on standby site it shows the following:
/*SQL> select database_role,open_mode,name,db_unique_name from v$database;
DATABASE_ROLE OPEN_MODE NAME DB_UNIQUE_NAME
PHYSICAL STANDBY MOUNTED PROD std
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 0
Next log sequence to archive 0
Current log sequence 0
and in alert logfile os standby database its shoing follwoing error
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.25.217.137)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=prod)(CID=(PROGRAM=oracle)(HOST=sm-alpha)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
Time: 10-DEC-2012 10:51:10
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=10.25.217.137)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=prod)(CID=(PROGRAM=oracle)(HOST=sm-alpha)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
Time: 10-DEC-2012 10:51:14
Tracing not turned on.
Tns error struct:
ns main err code: 12543
TNS-12543: TNS:destination host unreachable
ns secondary err code: 12560
nt main err code: 513
TNS-00513: Destination host unreachable
nt secondary err code: 113
nt OS err code: 0
Error 12543 received logging on to the standby
FAL[client, MRP0]: Error 12543 connecting to toprod for fetching gap sequence
here is my /etc/hosts
[root@sm-alpha ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.25.217.137 sm-alpha
and when i ping to sm-alpha
it gives
PING sm-alpha (10.25.217.137) 56(84) bytes of data.
From 10.25.205.117 icmp_seq=1 Destination Host Unreachable
From 10.25.205.117 icmp_seq=2 Destination Host Unreachable
From 10.25.205.117 icmp_seq=3 Destination Host Unreachable
From 10.25.205.117 icmp_seq=4 Destination Host Unreachable
From 10.25.205.117 icmp_seq=5 Destination Host Unreachable
would any one have a kind look at my problem.
thanks

Hi;
You are at wrong forum site. I suggest close your issue here as answered than move your issue Forum Home » High Availability » DATAGUARD which is DG dedicated forum site.
Regard
Helios

Next log sequence

The archive log list gives the following output:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination f:\ora9i\oradata\db01\archive
Oldest online log sequence 26
Next log sequence to archive 28
Current log sequence 28
My question is if the oldest online log sequence is 26, then the next and current log sequence should be 27. But why it is 28?
Regards,
Aqueel.

Generally speaking, if the archiver (ARCn) is up-to-date with archiving, ARCn will begin archiving log 1 as soon as (within a second or so) LGWR switches to log 2. There are no guarantees that this will always happen.
For example, if you have 3 redo logs, and it takes ARCn 15 seconds to write each log off to the archive destination, and somebody submits a large update that fills each log in 3 seconds, then you have a situation like this:
T + 0 Update submitted
T + 3 Log 1 filled switch to log 2
T + 4 ARCn begins archiving log 1
T + 6 Log 2 filled switch to log 3
T + 9 log 3 filled try to switch to log 1
But it is not archived yet so wait - no transactions can happen in the database at all until ARCn is finished.
t + 14 ARCn finishes archiving log 1 LGWR can write and transactions are allowed again
HTH
John

Log sequence in archive filename wrapped

Hi Friends,
I am on 11.5.10.2 windows 2003 server running on 10g Database, recently we are getting below warning message in alert log file, please help to resove this issue.
Warning Message:
ARC1: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
Thanks
Raghu

Hi Raghu,
Check your set value for log_archive_format .
Make sure the format has %s (sequence#)and %t (thread #) , capitalize them and the format will be padded to the left with zeros.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96536/ch195.htm#REFRN10089
Thanks
Rajkiran

ARC0: Warning. Log sequence in archive filename wrapped

Hi,
I am having my production database(Oracle 11gR1) in windows 2003 server.
I am often getting below archive warnings in alert logs.
ARC0: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
1.Could any one tell the reason and how to resolve this?
2.Also i want to know the limitations of %s and %S in LOG_ARCHIVE_FORMAT?
my log_archive_format is set to string ARC%S_%R.%T

Vikash Jain (DBA Trainee) wrote:
Hi,
I am having my production database(Oracle 11gR1) in windows 2003 server.
I am often getting below archive warnings in alert logs.
ARC0: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
1.Could any one tell the reason and how to resolve this?
2.Also i want to know the limitations of %s and %S in LOG_ARCHIVE_FORMAT?
my log_archive_format is set to string ARC%S_%R.%T
Change log archive format to small(s) *%s* instead of *%S*
%S Specifies the log sequence number. This number is padded to the left by
zeroes. The default value is one with a range of up to five characters.
%s Specifies the log sequence number. The number is not padded. The default
value is one with no range limit on characters. also refer this link http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams103.htm

ARC1: Warning. Log sequence in archive filename wrapped

Hi
we are using oracle10g 10.2.0.3 on windows 2000 server
we are getting ARC1: Warning. Log sequence in archive filename wrapped messages in alerlog
full messages is ARC1: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
what could be the reason?
Thanks
OH

user3308982 wrote:
Hi
we are using ARC%S_%R.%T
and we didn't change format
last few days we are getting this warning message
Thanks
With Regards
OHinstead of %S with %s on LOG_ARCHIVE_FORMAT,Then try again

How I can log Sequence File version number to database?

Hi,
As in the subject.
How I can log Sequence File version number to database?
There is nothing like that under Logging object.

Do you need it in a separate field in the databse?
One option is to just add it as an additional result in a step in your sequence file.
RunState.SequenceFile.AsPropertyObjectFile.Version
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

How to create physical standby database without dataguard

Hi,
Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
Please find the specifications of my server :
Database : Oracle 10.2.0.1(Standard Edition)
Server : Linux 4.0(32 bit machine)
As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
Thanks in advance.
Regards,
Farooq

Hello,
I hope this link helps you out...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA
Edited by: Pratik.L on Dec 31, 2009 12:03 PM

What is Media Recovery Log ..? Physical Standby Database

Hello All,
In my physical stdby database alert log I could see the below message, I'm not sure what id Media Recovery Log and why it is dumping ORACLE_HOME Directory..?
Could any one please help on this..? I need to house keep ORACLE_HOME directory.
Oracle 11gR2 / RHEL5
RFS[164]: No standby redo logfiles available for thread 2
RFS[164]: Opened log for thread 2 sequence 1995 dbid 287450012 branch 760028574
Fri Nov 11 19:39:05 2011
Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1992_760028574.dbf
Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1993_760028574.dbf
Media Recovery Waiting for thread 1 sequence 5568 (in transit)
Fri Nov 11 19:39:53 2011
Archived Log entry 948 added for thread 2 sequence 1994 rlc 760028574 ID 0x1122a1
FYI : The primary and standby database are in sync.

Hello;
The alert log is providing you with information. If you want more run this query :
select process,status,client_process,sequence# from v$managed_standby;You should see processes like ARCH, RFS and MRP0.
MRP will tell you if its applying log(s), waiting for a log, or if it thinks there's a gap.
PROCESS   STATUS       CLIENT_P SEQUENCE#
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
ARCH      CONNECTED    ARCH              0
MRP0      APPLYING_LOG N/A            5051
RFS       IDLE         N/A               0
RFS       IDLE         UNKNOWN           0There's a tiny amount of information about this under "9.3.1 Adding a Datafile or Creating a Tablespace" in Oracle document E10700-02.
If you find this helpful please click the "helpful" button.
Best Regards
mseberg

How to apply archive in Standby Database?

Hello,
My Database are running in linux plateform. I am seeing that archives which are generating are not copying to standby server & not applying.
Can anybody suggest me how to copy archive from primary database(ASM file system) to standby Database & apply those archives?
Thanks

Hi,
I am having similar problem. The primary logs are shipping on to standby but are not getting applied.
Here are the outputs:
From primary
SQL > select thread#,max(sequence#) from v$archived_log where archived='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 27908
2 28476
3 31643
select max(sequence#) from gv$archived_log;
MAX(SEQUENCE#)
31643
From Standby
SQL > select thread#,max(sequence#) from v$archived_log where applied ='YES' group by thread#;
THREAD# MAX(SEQUENCE#)
1 26862
2 27580
3 30874
select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
31643
Any help is appreciated.
Thanks in advance.

Error archiving to standby database

Hi
I get the following error from tyhe primary db when trying to archive to a standby database.
(tnsping is successfull)
*** 2007-02-12 11:24:54.263
RFS network connection lost at host 'test9isb'
Error 3113 attaching RFS server to standby instance at host 'test9isb'
Error 3113 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'test9isb'
Heartbeat failed to connect to standby 'test9isb'. Error is 3113.
*** 2007-02-12 11:24:54.263
kcrrfail: dest:2 err:3113 force:0
ORA-03113: end-of-file on communication channel
Watching the standby listaner log file, it doesnt seem to get that far, so the problem is probably on the primary/outgoing side ....
Can anyone suggest where my problem is ?
Cheers
Ian
Message was edited by:
user553552

Hi
I found a problem on the standby hosts listener.ora
But now I cant really see any errors anywhere, but logs aren't being transferred ....
Standby query "SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;" is giving output:
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MRP0 WAIT_FOR_LOG 1 187 0 0
RFS RECEIVING 0 0 0 0
primary trace file says:
Connecting to destination LOG_ARCHIVE_DEST_2 standby host 'test9isb'
Attaching RFS server to standby instance at 'test9isb'
Standby database restarted; old mount ID 0x8c27e216 now 0x8c28adf9
Any advice pls ?!?

Force logging at tablespace level for standby database

Hi
Can we create a standby database by enabling force logging at tablespace level instead of enabling it at database level.I want to out the tablespace containing indexes in nologging mode so that when I rebuild the indexes no logs will be generated.

Technically, you can create a Standby without having set FORCELOGGING at the Primary database.
You can also then selectively FORCELOGGING for all your important tablespaces (beginning with SYSTEM, SYSAUX, UNDO ....)
However, for a Physical Standby Redo Apply will mark the blocks (e.g. those populated by the CREATE INDEX .. NOLOGGING) as "corrupt". You will get Read Errors (ORA-1578 and ORA-26040) when you attempt to read the index (e.g. for a Table query).
So you have to monitor your NOLOGGING operations and the datafiles where NOLOGGING is applied. You can take Incremental RMAN Backups of such datafiles and restore them to the Standby immediately after the NOLOGGING operations.
Hemant K Chitale

StandBy database Create/Export Issue

We have database ABC and standby database ABCSTD and they are working properly. (Archives are properly applied), They were created from the database ABC_OLD.
Issue is that the ABC_OLD database has some more changes and users continued to work on that. We didnt switch the users to the ABC. And now the ABC database has become obsolete. its around one month old database.
I just want to know. Do I need to recreate the ABC database and Standby again from ABC_OLD cold backup Or Can I take full Database Export froom ABC_OLD and Import it on the the ABC Live.
Are there any other ways.??
Regards,
Rakesh Soni.

Or Am i just overthinking on this?
Is dataguard only looking for the current and oldest log sequence?

Test physical standby database in dataguard

Hi all,
I had a successfull dataguard implementation for oracle 9r2.
Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
Now i want to test physical standby database with applications tier but don't want to disturb origional primary database.
as these are the normal switchover steps
1) at primary db
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
2) at standby
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
3) at primary, now this will be the stand by database
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
4) at standby, now this will be the primary database
SHUTDOWN IMMEDIATE;
STARTUP
My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
Regards,
Ken

To avoid touching the primary production DB, you may try to use the following command on your standby database side:
alter database activate standby database;
This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

Next log sequence to archive in Standby Database (RAC Dataguard Issue)

Similar Messages

Maybe you are looking for