Physical standby database in RAC system

Hi EXperts,
We have a 4 nodes 11.2 cluster system. i will set a data guard as a disaster recovery mothods.
As a physical standby database set, does we need to configure same nodes (4 nodes) in other city as primary database cluster system?
Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?
Thanks explaining!
Jin

Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?Yes. You can setup 2 node RAC as physical standby and also with different memory parameters. But, the only issue is when DB failover from primary to standby, the applications connect to 2 node RAC in place of 4 node RAC and may be overloaded.

Similar Messages

Need advice regarding physical standby databases in rac environment on orac

need advice regarding physical standby databases in rac environment on oracle 10G r2
I like to have have a Primary ( 10 node RAC cluster ) shipping to a physical standby ( 3 node RAC cluster ) shipping using LGWR .
So I have a lot of questions
1) What will be the performance overhead on the Primay if we are using LGWR SYNC option .
2) Does the overhead depends on the physical distance between primary & physical
3)Do you recommend a seperate private network for shipping logs between primary and standby.
4) I know that DGMGRL supports RAC only from 10g. So are there any know issues are bugs using DGMGRL is RAC environments.
Thanks in advance
-Satish

Generally you should have same CPU architecture and same operating system but it's not mandatory to have the exactly the same CPU model, the same number of CPU, the same RAM size etc.
Actually starting with 11.1 you don't need to have the same hardware setup: it 's even possible to have primary and standby database on different platforms: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/standby.htm#i72053.

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

Recreating Physical Standby Database

HI
We have Oracle 11gr2 Primary database 2 node RAC using ASM Shared storage and physical standby database non rac using asm storage and data broker Unfortunately the standby site due to hardware failure the network link was down for a long period and huge log of archive waiting ?
We have required restore database and sync the primary to secondary database using data broker how will do it ?
Any help Highly appreciated
Thanks

Hi,
You can roll-forward you standby using incremental backup from primary .
If you use 'DataGuard Broker', then it should be stopped before starting with step 1) from below article and then started again when all steps finished.
Steps to perform for Rolling forward a standby database using RMAN Incremental Backup. (Doc ID 836986.1)
Thanks,
Renu

How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

Hi,
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5
RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
Thanks in Advance..

Hi;
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5I had similar issue, what i did
1. Used source oracle_home on standby server
2. Created new asm instance and use same naming
3. I took RMAN full backup on source and move it to target
4. I edit initora file remove RAC setting and restore db(also edited listener file)
Regard
Helios

Can I rename a physical Standby database without having to recreate?

Hi all,
One of my DBA's created a new standby database yesterday. He was supposed to create the standby database with a unique name from the primary system, but he didn't. So right now, DataGuard is running and replicating, and the standby has the exact same database name as primary.
I'd like to get this configured the way we had planned, to rename the standby database to something unique. I see Metalink Doc ID 15390.1, showing how to rename a database, but I'm not sure if this is possible in the standby environment? Has anyone ever done this? Anything different that needs to be accounted for, in the physical standby DB?
I'm on 10.2.0.3, on Windows 2003.
Any help/advice is appreciated!!
Thanks,
Brad

Dear TheBlakester,
You have to write it on the spfile and bounce the database. You should also have to change the log_archive_config parameter with the new standby db_unique_name.
From the online Oracle documentation;
For example, if the DB_UNIQUE_NAME parameter has not been defined on either database, the following SQL statements might be used to assign a unique name to each database.
Execute this SQL statement on the primary database:
SQL> ALTER SYSTEM SET DB_UNIQUE_NAME='CHICAGO' SCOPE=SPFILE;
Execute this SQL statement on the standby database:
SQL> ALTER SYSTEM SET DB_UNIQUE_NAME='BOSTON' SCOPE=SPFILE;
Step 4 Verify that the LOG_ARCHIVE_CONFIG database initialization parameter has been defined on the primary and standby database and that its value includes a DG_CONFIG list that includes the DB_UNIQUE_NAME of the primary and standby database.
For example, if the LOG_ARCHIVE_CONFIG parameter has not been defined on either database, the following SQL statement could be executed on each database to configure the LOG_ARCHIVE_CONFIG parameter:
SQL> ALTER SYSTEM SET
2> LOG_ARCHIVE_CONFIG='DG_CONFIG=(CHICAGO,BOSTON)';After than that it is better for you to check following items just in case;
v$archived_log
v$dataguard_status
Data Guard log file & Alert.log file.Hope That Helps.
Ogan

Error while creating physical standby database using Oracle Grid 10.2.0.5

Hi All,
I am setting up data guard using oracle grid.
Primary database version: - 10.2.0.4
Standby database version: - 10.2.0.4
Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
Fatal NI connect error 12533, connecting to:
(DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 10.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 17-AUG-2010 02:40:07
Tracing not turned on.
Tns error struct:
    ns main err code: 12533
    TNS-12533: TNS:illegal ADDRESS parameters
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0As we can see, address_list is empty.
Can anyone suggest what could be the reason behind this?

Dear user13295317,
Here is the error explanation;
Oracle Error :: TNS-12533
TNS:illegal ADDRESS parameters
Cause
An illegal set of protocol adapter parameters was specified.
In some cases, this error is returned when a connection cannot be made to the protocol transport.
Action
Verify that the destination can be reached using the specified protocol.
Check the parameters within the ADDRESS section of TNSNAMES.ORA.
Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
Ogan

Differences in creating a Standby database in RAC

Hi All
   SO...: Solaris 11 SPARC 64
   DB...: 11.2.0.3.6 (64 bits)
   My experience regarding creating Physical Standby Databases is restricted in only single instances to single instances. I am reading the book "Oracle Database 11g Release 2 High Availability", but, in parallel, i would like to hear from the experienced DBAs here some opinions and recomendations in how to implement a RAC to RAC solution. Below are my doubts:
   1) In single instance, using RMAN Backup to create the Physical Standby, i have to create manually a static Listener Entry. But in a RAC env, the listener is a resource, so, i have to create that resource in the Clusterware manually, or there is other approach?
   2) I have to create a pfile and start the instance in NOMOUNT mode, but in RAC, i have to start all the nodes in NOMOUNT, or just one node is sufficient?
   3) The archives will be replicated from FRA to FRA. Is this the best approach?
   My main concern is with the Listener and SCAN questions... If you have any considerations, they will be most welcome.
   Thanks in advance.

Following link might be helpful
http://www.oracledba.org/11gR2/dr/11gR2_dataguard_RAC_to_RAC.html

CREATING A SINGLE INSTANCE PHYSICAL STANDBY FOR A RAC PRIMARY

Hi
Creating a single instance physical standby database for a RAC Primary.
Getting this error.
sql statement: alter database mount standby database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/17/2008 23:05:38
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 01/17/2008 23:05:38
RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database
ORA-01103: database name 'PROD' in control file is not 'DPROD'
Any help on this.
Regards
Satish

The problem here is probably with your standby init.ora file.
When you create a standby database, the db_name parameter must NOT change. It has to match the primary database. So in your case, db_name ='PROD' and your db_unique_name='DPROD'...
-peter

Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

DB link for physical standby database

Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpful

976422 wrote:
Hi All ,
I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
SQL> create database link synct connect to system identified by 123 using 'stdby';
Database link created.
SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
select max(sequence#) from v$archived_log@synct where applied='YES'
ERROR at line 1:
ORA-02068: following severe error from SYNCT
ORA-01033: ORACLE initialization or shutdown in progress
Post Standby/DataGuard/ADG all questions further in Oracle Discussion Forums » High Availability » Data Guard
If you try to connect any users other than SYS in standby the error is very much expected. Of course you can connect with other users if you open database in OPEN READ ONLY mode, from 11gRx you can connect with other users even MRP is running if you are using ADG(active Data Guard licensed) .
I like to know, what you want to achieve by creating DB Link on physical standby database? Which is not allowed.
Database version is 10.2 standard edition
My requirement is i need to get max(sequence#) of standby database from primary database using db link.
what i was trying to do is
on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
Any suggestions will be really helpfulNote:- Standard edition, Data Guard not enabled.
To use this you should use Oracle Net Service, you no need of DB Links.
Ex:- sqlplus sys/****@standby as sysdba
Here standby refers to Oracle net service, Where you will have entries in $ORACLE_HOME/network/admin/tnsnames.ora file.
Edited by: CKPT on Dec 12, 2012 2:01 PM

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

Physical Standby database Vs. Logical Standby database

I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??

1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin

Steps To Create Physical Standby Database In Windows 7

Hi All,
I want to create a physical standby database in my windows 7 system. I have created one service stdby in my machine with all your help and now I need your help to configure standby configuration.
I am using Oracle 10G version 10.2.0.1.0.
Please suggest.
Regards,
Arijit

[on primary]
step-1 check if archiving is enable
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /PGHProdDB/archive/paceview/
Oldest online log sequence     52
Next log sequence to archive   54
Current log sequence           54
step-2
sqlplus> ALTER DATABASE force logging;step-3
connect to rman
take an full backup
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
step-4
now copying initpfile,pwdfile on appropriate destination and rename it.
step 5
now create listener on standby db side::
and restart it by ----
lsnrctl reload
and login to primary db and register listener information in tnsfile.ora---
standby=
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.13)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = standby)Step 6 Startup the standby
SQL> startup nomount pfile='/u01/app/oracle/admin/PRIMARY/pfile/init.ora';step 7
though our primary db is ready to connect with standby db
[oracle@PGH-DB ~]$ rman target / auxiliary sys/tiger@standby
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Aug 6 12:16:08 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: primary (DBID=2092349485)
connected to auxiliary database (not started)
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}When this completes
Make sure you shutdown the database and then switch the ORACLE_SID=STANDBY
when you perform that much let me know :)
Edited by: abdul_ora on Sep 12, 2012 11:37 AM

Standby Database in RAC

Hi,
We have two nodes RAC environment on the AIX 6.1
Our requirement is to have a database for the reporting purpose in one of the node and replicate the data from source to target. Is it possible to create physical standby database in one of the node and do log shipping to another database within the node.
Any other suggestions also appreciated.
Thanks.

I would first say if you are planning to create the standby for report it is for off loading the report from production database. If you create the reporting instance on the same hardware you would still e sharing if the primary service is active on the node that the reporting instance is running on. You would also be sharing the storage unless you separate the storage. If this is SAN storage you would be using the same HBA card.
It is possible to create the physical standby on another node in the cluster you just need to make sure to give the standby a different name. You would also need to make sure that the datfiles ,controlfile, redologs and archivelogs are not in the same location as the primary. One more thing to remember this will double you storage if you plan to use the same storage where the primary is located.

Physical standby database in RAC system

Similar Messages

Maybe you are looking for