Standby database management quick notes

Looking for standby database management quick notes

Dataguard Broker or manually initiated failover.
Please stop asking people to abstract docs in order to get 'quick notes'.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

"database manager" does not show up after MaxDB install

We have about 5 MaxDB/LiveCache installations.
Some of them has the "start->all programs->my SQL MaxDB->database manager" , while
some of them do not have above item.
I think there is a PC command to bring above item visible or accessible. Could you help?
P.S. I have used dbmcli to confirm the livecache is running well.
Thanks!

> I go to SMP and check software download center->
> My Company's Application Components" MAXDB" MAXDB 7.5 , 7.6, 7.7"
>
> I see : "no data available" for all above.
>
> Do you know why? Thanks!
I cannot know, but I bet there are some license things your company has to check until you can access that area.
Maybe the contract of your company was bound to a different DBMS until now?
Meanwhile you can just download the software from SDN - it's the same software, it's just that it may not be the latest build.
regards,
Lars

Database manager do not reconize database

Hi community!
I have the oracle 10g installed on my server, but something went wrong. What I mean is when I run the dbca, it does not find the database i have working fine on the server and the EM does the same.
What should I do?
obs.: the database is on production.
Roderick Barros

user3912207 wrote:
Hi,
the OS is Red Hat 4.8 64bit and the Oracle is 10.2.0.4.0.
I mean, when I run the dbca it just give me the option to create a new one and not to configure one database that has been created. There are no error messages at all.
Roderick BarrosSounds like you don't have an entry for the db in your oratab file.

Step by step 10g Dataguard , physical standby database setup metalink notes

On metalink i saw this note, but unable to find now if someone can help....

Note:248382.1 Creating a 10g Data Guard Physical Standby on Linux

Failover To Physical Standby Database

We have 3 node RAC 11.2.0.3 Primary database data guarded to a 3 node RAC 11.2.0.3 Standby database. There is an activity scheduled to perform some of order extracts in the database which is going to result in a lot of changes. Currently the discussion is on whether what should be the quickest way to go back to a point in time before the extract process starts in case of any issues. The options that we are looking at are:
1) Create a guaranteed restore point on both the Primary and Standby and use this to flashback the database (Quick but we have had issues where in the guaranteed restore point still does not guarantee the availability of the flashback logs) - Tested
2) Use RMAN backup from a day before to restore and recover to point in time before the extract process began (Time consuming) - Tested
3) Use export backup to perform a redirected restore i.e import the data from before the extract process (Time consuming) - Tested
4) Create a guaranteed restore point on both Primary and Standby, stop the Redo Apply/Ship at the time we create the guaranteed restore point and at a point we face some issue and need to go back, simply failover to the physical standby database and then reinstate the new standby database - This has not been tested yet but seems a viable option
With regard to the point 4, note that we are not concerned about data loss as the whole point of stopping the redo apply is to prevent the standby to be caught up with Primary during the run of the extract process. The question is whether the dataguard broker will allow failover of the primary to standby, in a situation described in bullet point 4). Please advice.

HI,
Please check this link:
Physical Standby Database SWITCHOVER &amp; FAILOVER Operations | Talip Hakan Ozturk&#039;s ORACLE BLOG
Thank you

Implementing Oracle StandBy Database - Suggestion & Tips needed Pls.

Dear Sir,
With rerefence to high availability of our database, we would like to implement a standby database. Regarding this, i have few doubts and request all you expert to pls. help me out. This goes like this:
1. What is DataGuard.? Is it Separate product in Oracle or Part of Oracle Database Server - Enterprise Edition.?
2. Is standby database implemented / created ONLY using DataGaurd?
3. Do we need to buy another license for Oracle Database when i go for implementing StandBy Database.?
Basically we want if my main production server is down, it should automatically go to my StandBy database and does not stop my application. This is possible i feel by implementing Standby database. And we are thingking to do it. In that respect, we have above query.
I would request if somebody could be guide us and help.
Thanks.
Regards,
Kamesh Rastogi

you can get DATAGUARD in Oracle Database Enterprise Edition !!
this is script for Craeting Standby DB!!
               Creating Standby Database
Primary Server Configuration
1.In the TNSNAMES.ORA of Primary DB add the entry of the Standby DB
IRCSSTDB(This is the service name in Primary DB to connect to Standby DB) =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1512))
(CONNECT_DATA =
(SERVICE_NAME = IRCS(This is the actual INSTANCE name of Running DB on Standby DB)
2. There is no need to Make any Changes in the Listener.ora of PRIMARY DB
Keep LISTENER.ORA of Primary as it is
Copy Listener.ora from Primary DB to Standby DB and make following changes
Delete All the Extra Existing listeners.
(These Modifications are for the STANDBY DB)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1521))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /ora01/app/oracle/product/9.2.0)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = IRCS)
(ORACLE_HOME = /ora01/app/oracle/product/9.2.0))
3.In the INIT.ORA of Primary DB add Following…
log_archive_dest_2 = "service=STBY optional/Mandatory scope=BOTH"
log_archive_dest_2 = Enable
log_archive_min_succeed_dest = 2
We can skip this & Dynamically add with the SQL*PLUS..
Standby DB Server Configuration
1.In the TNSNAMES.ORA of Standby DB add the entry of the Primary DB
primary1(ISSL)(This is the service name in Standby DB to connect to Primary DB)=
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (PORT=1521) (HOST=PRIMARY MACHINE NAME))
(CONNECT_DATA=(SERVICE_NAME=IRCS(This is the actual INSTANCE name of Running DB on Primary DB)
2.Copy Listener.ora from Primary DB to Standby DB and make following changes
Same as Above
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1521))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /ora01/app/oracle/product/9.2.0)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = IRCS)
(ORACLE_HOME = /ora01/app/oracle/product/9.2.0))
3. Connecting to an Idle instance..
1.C:\ oradim –NEW –SID ircs –INTPWD pwdfilename –STARTMODE auto –pfile E:\oracle\oradata\pfile\init.ora
2.     C:\ set oracle_sid=IRCS
3.     C:\ sqlplus /nolog
4.     SQL:>connect sys/ircl as SYSDBA
5.     SQL:>startup nomount pfile= E:\oracle\oradata\pfile\init.ora
6.     SQL:> alter database mount standby database;
7. SQL :> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
4. we can also add these parameter in INIT.ORA of Standby DB
1.standby_archive_dest= /u00/app/oracle/admin/sec/arch (Same path as in
(log_archive_dest_1) in init.ora
2. Fal_client=standby1 (Service Name)
3. Fal_server=primary1 (Service Name)
Troubleshooting….
1. Check Init.ora of Primary DB
2. Try to open Standby Database in normal mode try to connect it with normal user from different Machine.
3.check *.logs file on Standby Database
4.Check v$archive_dest on Primary DB
5. lsnrctl services <listener name>….For Checking Listener, for service

Standby database instance parameters in OEM repository

Hello all,
I am just wondering if someone using mgmt$db_init_params view to get information
about init parameters for standby databases in OEM (11.1.0.1)
I had problems for one of standby databases and after creation of SR was told that
dbconfig metric is not gathering that information for standby databases
Using Management Repository Views
However I have ~40 standby databases in OEM and 25 of them got entries in the view - how they got there?
And if there are any other ways to get init params for standby databases which do not
have that information in the view
Thank you,
Andrey

How are you monitoring the standby targets with sys account or dbsnmp?

How to delete the foreign archivelogs in a Logical Standby database

How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?

OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923

SECURITY PATCH ON STANDBY DATABASE AND PRIMARY DATABASE

I have a question on applying CPU on standby and primary database
I have a standby database on machine2 and primary on machine1
I applied a CPU patch on the Oracle Home of Standby database and
did not run the catcpu.sql as standbydatabase is in mount state.
Now i am going to apply the CPU patch on primary database.
What i need to confirm is that after i apply the patch on primary database oracle home
and run the cat cpu.sql on that do i have to do anything on the standby database
for instance rebuilding it or something or the change would be shipped to the standby
server automatically.
The purpose is to have the primary and standby database on the same patch level
in case of a failover
Please let me know asap

Any one has any idea on this. Any ideas would be appreciated

How to apply archivelog with gap on standby database

Hi All,
Oracle Database version : 9.2.0.6
Following is my sequence of commands on standby database.
SQL>alter database mount standby database;
SQL> RECOVER AUTOMATIC STANDBY DATABASE UNTIL CHANGE n;
ORA-00279: change 809120216 generated at 07/24/2006 09:55:03 needed for thread
1
ORA-00289: suggestion : D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC
ORA-00280: change 809120216 for thread 1 is in sequence #19921
ORA-00278: log file 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' no longer
needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
I have check the last sequence# on standby database which is 19921. And I have archivelog starting from sequence# 20672 onwards. When I am trying to apply archive log starting from sequence# 20672 , it is searching for 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' file and cancel the recovery. Please note that I don't have those missing archive on Primary server as well. So How can I apply the remaining archive log which I do have from 20672 onwards.
I hope I am not creating any confusion.
Thx in advance.

Hi Aijaz,
Thx for your answer. But my scenario is bit complex. I have checked my standby database status which is not running in recovery mode. I have tried to find archive_gap which is 0 on standby server. I am copying all archived log from primary to standby thru the script every 2 hour and appying them on standby. After applying, the script is removing all applied log files from primary as well as standby. So it is something like I have archivelog from 1,2,3,7,8,9,10. So 4,5 and 6 archivelog are missing which is required when I am trying to recover standby database. Also note that I want to apply 7,8,9,10. I will loose some data from those missing archive but I have cold back any way. I don't have those missing archivelog files(4,5 and 6) anywhere at all. So how can I recover standby database. I am using standby just for the backup purpose.
I hope my question is clear now.
Thx in advance
- Mehul

Package in a standby database

Hi,
How to know that all objects like sequences and packages in the standby database are updated even if there is a change in the primary database.
Is the query ALTER DATABASE OPEN READ ONLY;
can query the standby database and do not affect the primary database and how to leave this read only mode
Tovohery

Check this out.
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96653/manage_ps.htm#1017113

Create multiple standby databases of primary database

Hi,
I have to create 2 standby databases of a single primary database,
where can i get the stpe for the same?
Thanks

user10745179 wrote:
What about FAL_CLIENT parameters in primary?
how to set the values of the above parameter in priamry for second standby database.?
Thanks,In your case do need setting FAL_CLIENT/SERVER in primary database,set these parameter correctly in your standby database.Refer below note
*FAL_SERVER And FAL_CLIENT Settings For Cascaded Standby [ID 358767.1]*

Standby database or replication??

I need to setup two identical database, one for primary and one
for backup purpose (in case primary crash). Should I setup
standby database or setup replication?? which one is better and
easier??? Thanks...

I used both replicate and standby database.
I think depend on your decision.
standby database is easy.
replicate database is not hard.
you can monitor standby database (test) but you can test in read-
only mode. and If you active standby database, you can not go
back to standby mode and you have to re-create standby database
again.
when you master db fail, you can not auto switch to standby db.
dba have to manual or prepare application to start standby.
About data loss after fail-over. You may loss last data in last
archive-log in master database, if master server fail or disk
fail or you can not alter database swicth log files. So If you
redo log file is very big, you will loss many data.
replicate- You have to monitor snapshot database that work
everyday because they use job concept. So sometime job process
fail, you snapshot database doesn't sync.
But It is very easy to switch app. to snapshot db. when primari
database fail over.
Kitti U.

Logs are not getting applied in the standby database

Hello,
I have created a physical standby database and in it the logs are not getting applied..
following is an extract of the standby alert log
Wed Sep 05 07:53:59 2012
Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
Attempting refetch
Media Recovery Waiting for thread 1 sequence 37638
Fetching gap sequence in thread 1, gap sequence 37638-37643
Wed Sep 05 07:53:59 2012
RFS[46]: Assigned to RFS process 3081
RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
Wed Sep 05 07:55:34 2012
RFS[42]: Possible network disconnect with primary database
However, the archived files are getting copied to the standby server.
I tried registering and recovering the logs but it also failed..
Follows some of the information,
Primary
Oralce 11R2 EE
SQL> select max(sequence#) from v$log where archived='YES';
MAX(SEQUENCE#)
37668
SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
Standby
Oralce 11R2 EE
SQL> select max(sequence#) from v$archived_log where applied='YES';
MAX(SEQUENCE#)
37637
SQL> select * from v$archive_gap;
no rows selected
SQL> select open_mode, database_role from v$database;
OPEN_MODE DATABASE_ROLE
READ ONLY WITH APPLY PHYSICAL STANDBY
Please help me to troubleshoot this and get the standby in sync..
Thanks a lot..

the results are as follows..
SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
PROCESS STATUS GROUP# THREAD# SEQUENCE#
ARCH CLOSING 1 1 37644
ARCH CLOSING 1 1 37659
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
ARCH CONNECTED N/A 0 0
MRP0 WAIT_FOR_GAP N/A 1 37638
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS IDLE N/A 0 0
RFS RECEIVING N/A 1 37638
RFS RECEIVING N/A 1 37639
RFS RECEIVING N/A 1 37640
RFS RECEIVING N/A 1 37641
RFS RECEIVING N/A 1 37642
RFS RECEIVING N/A 1 37655
RFS RECEIVING N/A 1 37673
RFS RECEIVING N/A 1 37675
42 rows selected.
SQL>
SQL> select name,value, time_computed from v$dataguard_stats;
NAME VALUE TIME_COMPUTED
transport lag +00 02:44:33 09/05/2012 09:25:58
apply lag +00 03:14:30 09/05/2012 09:25:58
apply finish time +00 00:01:09.974 09/05/2012 09:25:58
estimated startup time 12 09/05/2012 09:25:58
SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database

Standby Database - from READ-ONLY to Managed Recovery

We have a standby database set up for our production environment.
We are able to switch logfile on production and perform the managed recovery and then switch over to READ-ONLY mode. However, when the database is in READ-ONLY mode...I cannot close it if there are active connections.
There are 2 ways I can attempt to close the database...either by "shutdown immediate" or by issuing an "alter system kill session (##,##);"
If I issue the "shutdown immediate", then the RFS process does not transmit any more files...saying the connection to host is not there. Therefore this is not a valid solution.
I can use an alter system kill...to kill all active connections...but it would require to know what other connections are there.
Does anybody know how to best do this...to close the database by forcing all connections to end (except your current one) so you can "alter database close" and switch over to managed recovery?
Please HELP!
Thanks.
-Nicolas

u just shutdown the server and restart in standby mode. it will apply all pending archive autometically.

Standby database management quick notes

Similar Messages

Maybe you are looking for