Configuring both logical and physical standby databases.

Hi,
I am trying to set up one primary and two standby databases which are physical and logical. together. What I am wondering is if i tis posiible to set both log_archive_dest_n parameters in init.ora of primary db to 'LGWR ASYNC'.. I tried to do that but I noticed that while redo data goes the first remote log destination including LGWR statement properly but for the second it does not.
So my assumption is only one remote archive dest. can be set for the LGWR process. Is ıt right?
Regards
ALPER ONEY
email:[email protected]

Hi,
when I set remote archive dest _n parameter for logical standby database to the value like 'LGWR AYSNC' and for the phy. standby to 'ARCH', it is ok. But if I change both parameters to 'LGWR'. I can see that only one destination receives the redo data and this destination is also the first destination configured for receiving redodata . I am just wondering that LGWR process is able to serve two or more to destinations at the same time. If it is ok, I am wrong and I better to try harder to solve the problem. I read the Dataguard document for 10GR' and the example for the case I created (two standby databases),, it uses ARCH process to send redo data and so everything is ok in that example.
P.S I also configured standbys for real time apply.
Waiting for your comments.
Regards.
ALPER ONEY

Similar Messages

Logical and Physical Standby on same Node

Is it possible to have a logical and physical standby database for a primary database on the same node (i.e. primary on NodeA, logical and physical database of primary on NodeB)?
Will there be any conflicts with data guard broker with this configuration or any problems I may encounter?

From a technical point of view this is possible. Your standby node should be powerful enough to handle 2 instances. For even higher availability 3 dedicated nodes would be better. When Node B is down, both physical and logical standby are also down.
Werner

Downtime for logical or physical standby database

Hi ,
Are there any downtime required to refresh the data from the primary database to logical standby or physical standby database. What are the pros and cons of
using logical and physical standby database approach. which one is advisable to use in production environment.
Regards,
Richard

Hi Richard,
I'd suggest you read the documentation as a starting point, to answer your questions on here would be quite lengthy,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm
In a nutshell you dont need downtime to maintain a standby, you can create them from a hot backup of your primary and get them recovering whilst it is open, in terms of which type of standby to use (physical or logical) that depends on your requirements for the use of the standby ... as I said read the doco (chapter 2 has a section on the benefits of each type).
HTH
Paul

Logical and Physical Standby Practice

Hello Gurus
I am now attempting to practice Oracle Data Guard and in this direction I understand since 10g we have logical standby server as well as a physical standby server. While I am gathering information and knowledge about the data guard as is and varisous modes and types possible with oracle 10g and 11g in specific, an attempt to upgrade my self and learn these set-ups and understand them in detail.. I come to you for some guidence..
I am referring to Oracle Documentation for these details. At the same time I also approach you to share your experiences .. may be a link apart from the documentation of oracle which you might want to refer me to use as a quick reference.. some thing that a person like me .. fairly new to this set-up understand it and then attempt to come up with one..
This is for my practise and learning purpose.
Sarat.

Logical Standby was already introduced in 9i. It differs from physical standby in the way, the redo protocol, transmitted from the primary, gets used to actualize the standby. With logical standby, you have SQL APPLY - basically, we try to generate the same SQL that was done on the primary from the redo protocol that was written on behalf of that SQL on the primary. That SQL then is done on the OPEN instance at the logical standby.
In case of a physical standby, the redo protocol from the primary is used to do RECOVERY - called REDO APPLY - to actualize the standby.
Since 10g, the sames protection levels can be achieved with logical or physical standby.
Drawback of logical standby: Not all kinds of SQL and all datatypes are supported
Drawback of physical standby: It is mounted (versions before 11g) while being recoverd - or in 11g, REDO APPLY in READ ONLY status is possible but comes with an extra charge (ACTIVE DATA GUARD feature).
If you look on my Blog, I have some examples about creating physical & logical standby DBs
Kind regards
Uwe
http://uhesse.wordpress.com

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

Logica and Physical standby to the same Primary?

Hi,
I have a primary - standby setup operating in the production. i now have a requirement to configure a Logical standby to the primary server. Can I do that leaving the already existing physical standby intact?
Thanks,
Aswin.

Yes you can have both physical and logical standby from one primary. The logical standby will need to start as a second physical standby.

Primary and Physical Standby databases hanging on sqlplus shell command...

I am primarily a java developer that has had the task of oracle dba thrust upon me due to circumstances that are beyond my control. In the QA lab we have two oracle 10 g release 1 instances running. They set up in a dataguard configuration: one is the primary and the other is in a physical standby.
Last week I noticed that the disk space on the primary database was at 100%. After some investigation I discovered that a good deal of the files taking up space on the box were log files and the best solution that I could think of would be to delete all old archive files. So I deleted the old archive files that were at least two weeks old using RMAN.
During this week the database started to shutdown automatically. The QA associate restarted the database twice using the ‘STARTUP’ command from sqlplus. Additionally, the standby database began to have issues: when login in to sqlplus the application would just hang: no ‘SQL” prompt or anything. Finally today the primary database has also begun to hang in a similar manner.
I have looked at many of the trace files and alert logs but haven’t been able to really discern what the real problem is with the database and the proper rectification for the database. Does anyone have a clue into what is going on? If someone could even point me in the right direction it would be greatly appreciated.

Guessing that your flash recovery area is full, archiving is stopped so the instance appears to hang.
Do you see messages like so in the alert log:
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************

Flashback database and Physical Standby databases

Hi,
We are thinking about the following scenario in our Production Standby databases. We are trying to do this to avoid number database cloning situations.
When we require live data to test data fixes :-
1. Switchover/failover the standby database.
2. opened this database in read write mode.
3. Apply the fix and test.
4. Flashing back the database prior to the SCN which did the switchover/failover.
5. Activate the standby again using a new standby controlfile.
Would you experts please comment on this idea?
Is this is possible? If so, would you please guide through the steps/some documentation.
Thanks in advance

This will not work according to me,
1)U can give previous SCN in rollback and gets the data till that SCN, but it will not become standby unless u make it a standby again manually by creating standy controlfile etc(may be this will be succesfull and limited up to check the data fixes).
2)Iif your first step succesfull then what about the fixes u test by applying patches using opatch and patchsets that cannot be rollbacked using flashback because they are copying new version files and adding some more configuration files to oracle home?.
There are lots of pitfalls and loop holes needed to be checked
Regards
Kaunain

Clarification on creating a Physical Standby Database

I'm practicing with data guard with Oracle 10.2.0.1.0 on two Windows 2003 servers.
I'm in the process of creating a physical standby database by following the steps outlined in the guide http://www.filibeto.org/sun/lib/nonsun/oracle/10.2.0.1.0/B19306_01/server.102/b14239/create_ps.htm
I've created the primary database and did a cold backup of all the datafiles and copied them to the standby server using OS commands. I've created a pfile from the spile in primary database and changed the needed parameters for the standby database.
What I don't understand is this statement I think is creating a control file for the standby database: SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tamp/standby.ctl'
Exactly what I don't understand is what to do with this control file. I'm thinking that if I try to use it as the controlfile for the standby database, the standby database will refuse to open since the database name in the control file wont match the one the server expects.
I don't want to proceed until this becomes clear. So my question is what to do with the output of the above statement that seems to create a control file for the standby database.
Any help would be appreciated.
Dula

>
You're thinking wrong.
Please clarify the difference between db_name and
db_unique_name.
Db_unique_name needs to be identical for both primary
AND standby database.
If db_unique_name differs, you'll get errors.
Sybrand,
Perhaps, you meant DB_NAME has to be identical for both databases.
DB_NAME name has to be the same for both primary and physical standby database.
DB_UNIQUE_NAME should be unique for each database in the standby configuration.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i68626
If you configure Logical Standby Database, DB_NAME may be different.
For the original poster: Chapter 3 - Creating a Physical Standby Database of Oracle® Data Guard Concepts and Administration has all the steps you have to do in order to configure a physical standby database.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
Cheers,

RE logical/physical standby database

1. Why logical standby database is SQL apply, and Physical standby database is redo apply? What ‘s the meaning/objective for that? (pls don’t tell me what is SQL/redo apply)
2. As we know, a logical standby database can be used for reporting and querying if primary database is down, why we still need a physical standby database (it can’t do that during recovering process, it just a same copy of primary database)? Why not just go ahead to set up only a perfect logical standby database? (just because logical one can’t accommodate all kinds of data type???)
3. Combined with Real time Apply and maximum protection, we can achieve a zero data loss, but could we achieve a zero downtime? Why or why not?

Go Through Below link
>>>Can you convert a Logical standby to a Physical Standby?

OEM for physical standby database

Hello All,
I am using Oracle 11.2.0.3. My enterprise manager is db console 11.2
I have Oracle Enterprise manager dbcnsole for my RAC primary database and I have created through sqlplus command line a physical standby database.
My questions
Can I use the RAC primary dbconsole to monitor my physical standby database? if yes what the steps?
Is it mandatory to use grid control in that case? if yes, what steps are needed to implement grid control ?
Regards,

Hi,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
Using EM cloud control 12c is best available option to monitor your standby databases
For install docs refer to
http://docs.oracle.com/cd/E24628_01/install.121/e22624/toc.htm
For Software download link
http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html
Regards,
Rahul

Physical standby database fail-over

Hi,
I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
Primary:
alter system set log_archive_dest_state_2='DEFER';
alter system switch logfile;
Standby:
alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
Standby:
alter database activate physical standby database;
alter database open;
shutdown immediate;
startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
2) Are all the old backups marked unusable after a fail-over is performed?
FYI... flashback database was not used in this case as it did not server our purpose.
Any information or documentation links would be greatly appreciated.
Thanks,
Harris.

Thanks for the reply.
The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
Anyhow, we got the issue resolved. Below is the resolution path.
1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
Thanks,
Harris.
Edited by: user11971589 on Nov 18, 2010 2:55 PM

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

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

Logical standby database to physical standby database

I already start my logical standby database and I want to return it again to physical standby database. So what should I do?

>
The "may be" is because I have tested flashback of a physical standby to before resetlogs, but not a logical standby.
>
A physical standby keeps the DBID of the primary - a logical standby does not. That is exactly the problem that restricts the reconversion into physical from logical, and you did not encounter that problem.
>
I haven't used "keep identity" but from what I read it relates to "convert to physical" not "flashback database".
>
Exactly. And that is what the OP wants to do: convert to physical (from logical).
You mentioned that this might be possible with flashback.
Problem: During the conversion from physical to logical, the DBID gets changed unless you specify (in 11g) KEEP IDENTITY. This would make it possible to reconvert into phyiscal from logical.
In short: If there is no solution for the changed DBID of the logical standby in order to flashback it into physical as you suggested, then it is not possible .
When I saw your first answer, I thought that you might have a solution in mind in order to solve that obvious problem. Sorry for having bothered you.
Kind regards
Uwe
http://uhesse.wordpress.com

Configuring both logical and physical standby databases.

Similar Messages

Maybe you are looking for