Standby database,Possible network disconnect with primary database

Hello
I have a database on linux with standby configured on different server with same os and database version.When i was about clone primary database through OEM,it stuck in the middle and popup for recovery. I restored and recover whole database. Then, the alert log on the standby database shows this error.
Possible network disconnect with primary database.
I checked standby databsase,listener is up & running. But archive files are getting into standby database.
What should i do now? Please anybody can put some light on this.
Thanks
Ariz

Is there anything in the primary alert log? Can you tnsping the standby instance from the primary server, and the primary instance from the standby server?

Similar Messages

FS[3988]: Possible network disconnect with primary database

Hi All,
In the standby database alert log I'm getting the below error:
Thu Feb 10 11:09:10 2011
RFS[3971]: Possible network disconnect with primary database
Thu Feb 10 11:10:11 2011
RFS[3976]: Possible network disconnect with primary database
Thu Feb 10 11:11:12 2011
RFS[3979]: Possible network disconnect with primary database
Thu Feb 10 11:12:13 2011
RFS[3982]: Possible network disconnect with primary database
Thu Feb 10 11:13:15 2011
RFS[3985]: Possible network disconnect with primary database
There is no error in the primary database regarding this.
And after this no archive logs are being pushed to the standby database.
In V$ARCHIVE_DEST_STATUS view the column synchronizaion_status says CHECK NETWORK for dest_name LOG_ARCHIVE_DEST_2
Please advice.
Thanks.
Regards,
Ashwani N.

Both messages look crystal clear to me.
Did you check the network?
If not, why not?
Your posting history here is a bit appalling
823436
     Newbie
Handle:      823436
Status Level:      Newbie
Registered:      Dec 24, 2010
Total Posts:      28
Total Questions:      9 (7 unresolved)
Sybrand Bakker
Senior Oracle DBA

RFS[2647]: Possible network disconnect with primary database

Hi Guys,
I am working as a L1 DBA in my project. We have a 3node RAC database 11.2.0.1.0 and the standby database was in sink with production till yesterday. Suddenly we realized that out primary and standby is not in sink.. Logs are shipped from primary but it is not applying in standby. While checking the alertlog I can see these errors.
RFS[2649]: Assigned to RFS process 23250
RFS[2649]: Identified database type as 'physical standby': Client is ARCH pid 16573
Mon Jul 23 11:55:42 2012
RFS[2647]: Possible network disconnect with primary database
I have performed a media recovery but still I am facing the above errors. I thought earlier that there might be some network issue but we can ping the service names from both the primary and standby.
Can you please suggest me the steps that I can go through and fix this issue.
Regards,
Arijit

937670 wrote:
Hi Guys,
I am working as a L1 DBA in my project. We have a 3node RAC database 11.2.0.1.0 and the standby database was in sink with production till yesterday. Suddenly we realized that out primary and standby is not in sink.. Logs are shipped from primary but it is not applying in standby. While checking the alertlog I can see these errors.
RFS[2649]: Assigned to RFS process 23250
RFS[2649]: Identified database type as 'physical standby': Client is ARCH pid 16573
Mon Jul 23 11:55:42 2012
RFS[2647]: Possible network disconnect with primary database
I have performed a media recovery but still I am facing the above errors. I thought earlier that there might be some network issue but we can ping the service names from both the primary and standby.
Can you please suggest me the steps that I can go through and fix this issue.
Regards,
ArijitLops may shipping of other node, can you check it is able to receive archives from all the nodes? May be you having issue from one node.
also there would be network disconnect for some time, its usually happens, if not can you query below output from primary
SQL> select message,error_code,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') from v$dataguard_status where dest_id=2;

ARCH: Possible network disconnect with primary database

Dear buddies,
My database has a primary database which has a few sub databases.
They are in different servers.
One of the sub database has this error in the alert log everyday during backup time.
But finally the backup is successful.
Is this a network problem?
Please guide me.
Thanks in advance.

user645399 wrote:
Dear SB:
THis is the error I come across once in a while in my alert log:
ARCH: Possible network disconnect with primary database
post
select FACILITY,SEVERITY,MESSAGE_NUM,ERROR_CODE,CALLOUT,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'),MESSAGE from v$dataguard_status where dest_id=2;
sample
SQL> select FACILITY,SEVERITY,MESSAGE_NUM,ERROR_CODE,CALLOUT,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'),MESSAGE from v$dataguard_status where dest_id=2;
FACILITY                 SEVERITY      MESSAGE_NUM ERROR_CODE CAL TO_CHAR(TIMESTAMP,'D MESSAGE
Log Transport Services   Error              312410       3135 YES 27-JUL-2011 05:01:51 NSA: Error 3135 archiving log 5 to 'stby'
Log Transport Services   Error              312539       3135 YES 27-JUL-2011 16:56:40 NSA: Error 3135 archiving log 7 to 'stby'
SQL>

Logical Standby Database Not Getting Sync With Primary Database

Hi All,
I am using a Primary DB and Logical Standby DB configuration in Oracle 10g:-
Version Name:-
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
We have build the logical standby last week and till date the Logical DB is not sync. I have checked the init parameters and I wont see any problems with it. Also archive log destinations are also fine enough.
We have a important table named "HPD_HELPDESK" where record count is growing gradually whereas in logical standby it's not growing. There are some 19K record difference in the both the tables.
I have checked the alert log but it is also not giving any error message. Please find the last few lines of the alert log in logical Database:-
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1703_790996778.arc] to LogMiner session id [1]
Tue Aug 28 14:56:52 GMT 2012
RFS[2853]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 14:56:58 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 14:57:00 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1704_790996778.arc] to LogMiner session id [1]
Tue Aug 28 15:06:40 GMT 2012
RFS[2854]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 15:06:47 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 15:06:49 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1705_790996778.arc] to LogMiner session id [1]
I am not able to trace the issue that why the records are not growing in logical DB. Please provide your inputs.
Regards,
Arijit

How do you know that there's such a gap between the tables?
If your standby db is a physical standby, then it is not open and you can't query your table without cancelling the recovery of the managed standby database.
What does it say if you execute this sql?
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;The ARCH processes should be connected and MRP waiting for a file.
If you query for the archive_gaps, do you get any hits?
select * from gv$archive_gapIf you're not working in a RAC environment you need to query v$archive_gap, instead!
Did you check whether the archives generated from the primary instance are transferred and present in the file system of your standby database?
I believe your standby is not in recovery_mode anymore or has an archive_gap, which is the reason why it doesn't catch up anymore.
Hope it helps a little,
Regards,
Sebastian
PS: I'm working on 11g, so unfortunately I'm not quite sure if the views are exist in 10gR2. It's worth a try though!
Edited by: skahlert on 31.08.2012 13:46

Standby database is not Sync with primary DB

Hi,
One week back I configured standby database and It was running fine.
But 2 days back(Saturday) somebody had down my standby database. Today when I mounted my database; I saw this is not sync with primary database.
Database Name :- pcs
Primary db_unique_name :- pcs
standby db_unique_name :- pcstd
Present scanerio is...
Status of Standby Database is...
SQL> startup mount;
ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2063792 bytes
Variable Size 301990480 bytes
Database Buffers 763363328 bytes
Redo Buffers 6324224 bytes
Database mounted.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
SQL> recover managed standby database disconnect from session;
Media recovery complete.
SQL> select GROUP# ,SEQUENCE# ,ACTIVE_AGENTS,STATUS from v$managed_standby;
GROUP# SEQUENCE# ACTIVE_AGENTS STATUS
N/A 0 0 CONNECTED
N/A 0 0 CONNECTED
N/A 130 0 WAIT_FOR_LOG
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /backup/bkpcs/
Oldest online log sequence 121
Next log sequence to archive 0
Current log sequence 126
Status of Primary database is..
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /data/pcs10g/archive/
Oldest online log sequence 129
Next log sequence to archive 131
Current log sequence 131
SQL>
Somebody can help me to resolve the following issues
(1). Why archive log list not showing exact log sequence number on Standby Database.
(2). How can I configure automatic archive logs apply from Live to Standby again.
Regards,

Problem has been resolved.

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,
Rakesh

HI 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>

Can we create standby database on same server as primary database

I have Oracle 10g Rel2, OS Windows server 2003. Can I create standby database on same server on which we have our primary database?

Bharat Kaushik wrote:
I have VMware server s/w, do i need to create 2 virtual machines inside the one installation of VMware server? Or do i need to have 2 different installation of VMware server?You could think of VMWare Server in similar terms are Oracle Database Server.
The HOME: The VMWare Server s/w is put into a "VMWare Home" (I use VMWare Workstation, it goes into C:\Program Files\VMware\VMware Workstation)
The INSTANCE: WHen I create a VM Image, I specify the name (like a SID), configuration (like PFILE), and location (like ORACLE_BASE/oradata/ ...)
And just like Oracle with which I can have 2 or more instances running on the host (if there is sufficient memory and other resource), I can have 2 or more VM Images running on my host.
And just like Oracle, if I have insufficient resources, things get slow like molasses in the middle of winter.
Hope your desktop has at least 4GB of OS-addressible RAM and at least dual-core CPU. ALternately ... I hope you have lots of coin for the coffee machine.

Physical Standby Database Lags Far Behind the Primary Database scenario

Hi,
Have anyone successfully implemented described in the Oracle Documentation following
scenario?
For me it does not work at all.
After implementing all steps current_scn of standby database remains the same and when trying to push recovery using redo it asks for non-existing archived log which I can't restore on primary database as all backups containing that archived log already gone.
The only option is to recreate standby database from backup again.
Best Regards,
Alex

I already found the reason.
Just for your information:
Recovering a Standby database from a missing archivelog
Unfortunately documentation missed that important step of standby controlfile recreation.
To my luck I was copying the whole backup to the standby server when found this link.

Network security with Oracle Database Cloud Service

Does the Oracle Database Cloud service support SSL? Or, any form of network encryption/authentication between a client and the service across the Internet?

Thank you Rick. I'm intending to use Oracle Database Cloud Service as a "Database-as-a-Service", however I have read that it is actually more of a "Platform-as-a-Service" offering.
What I would like to do is to interact with the Oracle Database Cloud Service via a local JDBC client. However, from further reading, it looks like the only way to interact with the Oracle Database Cloud Service from a non-Oracle-cloud-based client is via its RESTful web services (which, as you said, support SSL).
That is to say, I cannot simply connect to the Oracle Database Cloud Service from a local client just through JDBC alone. It looks like I would have to configure my client to make the relevant RESTful web service calls instead, and likewise configure my settings on the Oracle Database Cloud Service to make the necessary translations (from REST to SQL).
Just to finally clarify, is my above understanding correct?

Standby database on same machine as primary database

hi,
I am testing the standby database and read all document on metalink also I am able to start the standby database in nomount mode nut when trying to mount the database I am getting following error
SQL> startup nomount
ORACLE instance started.
Total System Global Area 47679696 bytes
Fixed Size 731344 bytes
Variable Size 29360128 bytes
Database Buffers 16777216 bytes
Redo Buffers 811008 bytes
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01103: database name 'PRIMDB' in controlfile is not 'PRIMDBS'
I think the database name must be different on same machine. My os is Sun Solaris
Regards
Bhushan

When you need to have the standby database on the same server as the master, use lock_name_space in the init.ora.
This parameter permits this to occur without having to worry about changing the db_name.
http://www.oug-ottawa.org/pls/htmldb/f?p=103:21:729607614317189728::::P21_TIP_NUM:821

Data guard, network disconnect error

Hi All,
we have data guard two node cluster of oracle 9iR2 on Solaris 9 SPARC, initially there were too many error coming in both Primary and standby sites, but after resolving all those problems we are now just getting following error in Alert.log of standby database
RFS: possible network disconnect with primary database
while there is NO other error/message in alert logs, we are able to do tnsping from both sites !
what might be the possible cause of the above error?
TIA

Hi,
the primary database is a Production database that is open and running.
here are the alert logs from them:
Primary Database:
Thu Jan 29 09:18:55 2009
Thread 1 advanced to log sequence 16629
Current log# 1 seq# 16629 mem# 0: /dev/vx/rdsk/SIDdata_dg/SID_log1_a
Current log# 1 seq# 16629 mem# 1: /dev/vx/rdsk/SIDdata_dg/SID_log1_b
Thu Jan 29 09:18:55 2009
ARCH: Evaluating archive   log 4 thread 1 sequence 16628
ARCH: Beginning to archive log 4 thread 1 sequence 16628
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/archive/SID/arch_SID_1_16628.arc'
Thu Jan 29 09:18:55 2009
ARC3: Evaluating archive   log 4 thread 1 sequence 16628
ARC3: Unable to archive log 4 thread 1 sequence 16628
Log actively being archived by another process
Thu Jan 29 09:18:55 2009
ARCH: Completed archiving log 4 thread 1 sequence 16628
Thu Jan 29 09:19:29 2009
Thread 1 advanced to log sequence 16630
Current log# 2 seq# 16630 mem# 0: /dev/vx/rdsk/SIDdata_dg/SID_log2_a
Current log# 2 seq# 16630 mem# 1: /dev/vx/rdsk/SIDdata_dg/SID_log2_b
Thu Jan 29 09:19:29 2009
ARC0: Evaluating archive   log 1 thread 1 sequence 16629
ARC0: Beginning to archive log 1 thread 1 sequence 16629
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/archive/SID/arch_SID_1_16629.arc'
ARC0: Completed archiving log 1 thread 1 sequence 16629
Thu Jan 29 09:19:44 2009
Thread 1 advanced to log sequence 16631
Current log# 3 seq# 16631 mem# 0: /dev/vx/rdsk/SIDdata_dg/SID_log3_a
Current log# 3 seq# 16631 mem# 1: /dev/vx/rdsk/SIDdata_dg/SID_log3_b
Thu Jan 29 09:19:44 2009
ARC2: Evaluating archive   log 2 thread 1 sequence 16630
ARC2: Beginning to archive log 2 thread 1 sequence 16630
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/archive/SID/arch_SID_1_16630.arc'
ARC2: Completed archiving log 2 thread 1 sequence 16630
Thu Jan 29 09:22:24 2009
ARC1: Begin FAL archive (thread 1 sequence 16628 destination SIDdr)
Creating archive destination LOG_ARCHIVE_DEST_2: 'SIDdr'
ARC1: Complete FAL archive (thread 1 sequence 16628 destination SIDdr)
ARC1: Begin FAL archive (thread 1 sequence 16629 destination SIDdr)
Creating archive destination LOG_ARCHIVE_DEST_2: 'SIDdr'
Thu Jan 29 10:39:35 2009
ARC3: Evaluating archive   log 3 thread 1 sequence 16631
ARC3: Unable to archive log 3 thread 1 sequence 16631
Log actively being archived by another process
Thu Jan 29 10:39:35 2009
Creating archive destination LOG_ARCHIVE_DEST_1: '/global/archive/SID/arch_SID_1_16631.arc'
ARCH: Completed archiving log 3 thread 1 sequence 16631
Standby database:
Thu Jan 29 03:00:37 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:11:26 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:22:39 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:31:29 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:33:40 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:41:30 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:44:41 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 03:54:43 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 04:05:44 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 04:22:36 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 04:33:37 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 04:37:48 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 04:43:38 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 05:13:41 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 05:45:46 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 05:49:58 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 06:00:00 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 06:05:48 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 06:31:03 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 06:36:52 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 06:47:53 2009
RFS: Possible network disconnect with primary database
Thu Jan 29 07:03:07 2009
regards,

Primary Database and Standby Database sync

How to know that standby database is in sync with primary database?

Query the V$LOG_HISTORY view on the standby database, which records the latest log sequence number that has been applied. For example, issue the following query:
SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
2> FROM V$LOG_HISTORY
3> GROUP BY THREAD#;
THREAD# LAST_APPLIED_LOG
1 967In this example, the archived redo log with log sequence number 967 is the most recently applied log.
You can also use the APPLIED column in the V$ARCHIVED_LOG fixed view on the standby database to find out which log is applied on the standby database. The column displays YES for the log that has been applied. For example:
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
THREAD# SEQUENCE# APP
1 2 YES
1 3 YES
1 4 YES
1 5 YES
1 6 YES
1 7 YES
1 8 YES
1 9 YES
1 10 YES
1 11 NO

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

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

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

Why do we need standby redo log on Primary database.

Hi Gurus,
I was going through the document in OBE,
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I have two queries:
1) I noticed the statement -
"Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
Why do we have to create standby redo log on a primary database?
2) There is another statement --
"It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
Why do we need one additional standby redo log group than in Primary database.
Could anyone please explain to me in simple words.
Thanks
Cherrish Vaidiyan

Hi,
1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
Regards
Anudeep

Standby database,Possible network disconnect with primary database

Similar Messages

Maybe you are looking for