Forward physical standby archivelog files to a logical standby database

Hi,
We have a production database (1) and we have a physical standby database (2) for it.
Is it possible to forward the archivelogs files from (2) to a logical standby database (3). We want to use the (3) as a UAT - Ad Hoc read only Database.
Thanks.

Hi,
The following Data Guard configurations using cascaded destinations are supported.
A. Primary Database > Physical Standby Database with cascaded destination > Physical Standby Database
B. Primary Database > Physical Standby Database with cascaded destination > Logical Standby Database
A physical standby database can support a maximum of nine (30 as of Version 11.2) remote destinations.
Physical Standby Forwarding Redo to a Logical Standby :
Advantages :
1. Users can connect to Logical Standby database and they can access
2. Instead of querying primary database they can use logical standby database.
3. without any additional overhead on your primary system, and without consuming any additional transatlantic bandwidth.
Disadvantages :
The following data types will not support in Logical standby database just check your application before implementing logical standby
a. BFILE
b. Collections (including VARRAYS and nested tables)
c. Multimedia data types (including Spatial, Image, and Oracle Text)
d. ROWID, UROWID
e. User-defined types
f. LOBs stored as SecureFiles
g. XMLType stored as Object Relational
h. Binary XML
Thanks
LaserSoft

Similar Messages

Can a physical standby propagate data to a logical standby?

Here is my situation. I have a RAC database that currently has a physical standby (also RAC cluster) for disaster recovery (DR) and I am about to create an additional logical standby for real-time reporting. My customer is asking if I can also create a logical standby for reporting that resides in the DR environment that would be available in a disaster. My question is can a physical standby propagate data to a logical standby? Is there any special configuration that would be required and what might it be if this is possible?
Thanks.

Hi,
Welcome. Yes it's possible, example in 11.2 :
A cascading standby database can cascade primary database redo to up to 30 cascaded destinations, each of which can be a physical, logical, or snapshot standby database.
http://download.oracle.com/docs/cd/E11882_01/server.112/e17022/log_transport.htm#SBYDB5122
Best regards
Phil

Primary Archivelog Management When Using Logical Standby

I was wondering if anyone has seen or created a script to do archivelog management when using standby databases. We recently had an experience where our standby database and primary database got out of sync and we had to recreate the standby....I had hope to advoid this but it was easier than trying to recall tapes to retrieve the backups of the archivelogs from the primary.
Management on the logical side is fine. I know of the ability to delete log files on the logcial standby after they have been applied to the database. However, this does not address the issue of the management of archivelogs on the primary site. Does anyone have a script that only deletes the archivelogs from the primary site after they have been applied to the logical standby? Now this is a LOGICAL standby not a physical standby....RMAN has the capability of doing this for a physical standby but I don't know of any commands ro setup to allow it to do it for a logical standby.
Regards
Tim

Even with 1 TB of space I only have room enough for about 3 days worth of archivelogs. Working in the environment that I do, there is another group in charge of the ESAN which serves many different systems. They were wanting detail reasoning and justification why I needed 3 days worth of space when I requested it.
It is not truly a problem, there are always work arounds. I can restore from the backups, I can put in scripts to send out email notification when the standby falls to far behind the OE. However even with all that, I wanted to write a script that someone could run without having to check the system to delete the archivelogs if space becomes an issue on the production side.
I was just hoping to see if anyone had a script to do it already.
Thanks for all the input.
Regards
Tim

Data Guard: standby archivelog files not the same as the primary archivelog

From reading the Data Guard doco, one gets the impression that that the standby redo archive logs are just a mirror of those from the primary, that the shipped and applied archived redo logs from the primary are what end up in the standby archive directories.
However I have noted that the files are not the same (md5sum is different), which is concerning as using Oracle's archive log naming recommendation, the files have identical names.
Does this mean that the Standbys redologs can not be used as a source of redo logs if one had to restore using a backup of the primary database?
i.e. Can you recover using an RMAN backup of the primary, and redo logs from the standby?

Hi MSK, I agree, that's exactly what I thought. I'm confused though why the logs do not match. Perhaps it is just metadata in the log that has changed, not redo data.
Anyone have any knowledge on why the archivelogs are different on the standby to those on the primary?

How to find archivelog files required during FLASHBACK a database?

Environment: 11.1.0.7
Requirement : Flashback on Standby side from SQL PLUS
We are taking backup of db&arch using Tivoli TAPE backup system from primary side. we do not have license for Tivoli on Standby side so there are no archivelog backups on standby side. Also we are not keeping archived log files shipped from primary to standby not more than 1 day in disk. So any archivedlog files required beyond 1 day need to be restore on primary side and to be moved.
While we do flashback from sqlplus we encounter below error ...
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38761: redo log sequence 6 in thread 2, incarnation 6 could not be accessed
if we restore Seq#6 from thread#2, then again it will ask for another archivedlog file.
So is there a way to find all required archviedlog file for my flashback and restore all at one time ?

Hi,
It's a good question but even note 560686.1 is not very precise about it.
The flashback logs are used to rollback quickly and "approximately" then the archivelog files are applied in complement to recover the database at the exact SCN. All archivelog files won't be required but a few ones having completion time around the desired time and you have to provide them. Which ones exactly ? I don't know but the simplest would be to have your archivelog files or their backup accessible cause RMAN is able to restore the archivelog files it needs automatically (no need to restore them manually)
Best regards
Phil
Edited by: Philippe Florent on Aug 29, 2010 9:45 PM
Edited by: Philippe Florent on Aug 29, 2010 9:49 PM

Creating a standby control file for cloning a standby database

Hi
I am in the process of trying to document the cloning of a standby database. I am trying to amalgamate three different documents - one for a normal clone, one for the creation of a SB database, and the other a formal Oracle document - the Business Continuity doc.
Among the several things that confuse me, is the issue of creating (or not) a standby control file.
I am not doing any kind of data file deletion / copying from source to target, as the SB database is updated all day with data file changes. I am doing a complete copying over of the APPL_TOP and techstacks.
My question then, is this: should I be worried about creating a standby control file? I am told by our Senior here that "you can get away with not doing it", which sounds like too much of a risk to me.
I am under a bit of pressure for this and I am not 100% sure about certain issues (see my other post for knowing how many DATA_TOPS we have on the SB, for instance).
Thanks for listening.
AIX 5.2.
Oracle 10g.
DA

Do you already have a Standby running ? (then it may be using a standby controlfile).
Yes. And there is already a standby control file there. It seems to me, that if the data (logs) transfers are done each minute or whatever between source and SB, and the SB is a copy of the db, then we dont need to worry about any kind of data files, since they should be identical. The only things I will need to change are the configuration files like the ifile in both dbs and tns_names, listener, tnsnames.ora, and the init.ora.
b. Are you creating a document about the process of creating standby from production ? If you plan to use DataGuard, you will need a standby controlfile. Otherwise , it depends on how you configure the standby.
No. I am creating a doc for how to clone from Production to a SB environment. A reason behind this is that the Apps side of the SB is about 9 patches behind the Production box, and we need to update it. I believe this is the main reason for doing this.
c. Just to check : You are NOT using Storage Mirroring -- ie D.R. ?
No, no DR on this environment.
Thanks.
DA

Is that possible to convert logical standby to physical standby ?

Hi guys,
My steps for testing as below:
1.create a primary database
2.duplicate a physical standby database;
3.turn on flashback on both databases.
4.record SCN xxx on physical standby database.
5.convert physical standby to logical standby (using keep identity statement)
6.flashback to logical standby to xxx
7.convert logical standby to physical standby
8.using real time apply
I got errors:
Fast Parallel Media Recovery enabled
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery waiting for new incarnation during transient logical upgrade procedure
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Managed Standby Recovery not using Real Time Apply
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Errors appears every 10 seconds. Seems MPR0 is waiting for new incarnation for a long time. So am I.
Standby database incarnation:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORA11GR1 3853851354 CURRENT 1 08/09/2013 01:02:18
2 2 ORA11GR1 3853851354 ORPHAN 2127877 08/28/2013 19:22:01 BGV

Hello;
Because of limitations for specific data types and objects with a logical database I going to say no.
Best Regards
mseberg

Do I need ASM for logical standby server?

I am using ASM in production, when I created physical standby for it, system asked me create ASM file system on it else it is not possible. My question is do I need ASM file system for logical standby too.?
Thanks

You can have the primary database on ASM and the standby on filesystem if you want.
You just need to set db_file_name_convert and standby_file_management. I have tested this will physical, but not logical standby.

Creating triggers in a logical standby database

Does anyone know if its possible to create and enable a trigger in a logical standby database on a 'guarded' table? I've been able to create the trigger (as an after insert trigger) and it appears to be valid but it never seems to fire, despite inserts taking place. Are there any other steps involved to activate this, or is it just plain not possible in a logical standby? My primary and logical standby databases are 10.2.0.3

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Second logical standby

Hello,
i've this architecture: 1 production database, 1 physical standby, and 2 logical standby. One of the logical standby must now be rebuild, and my question is: i have already play the DBMS_LOGSTDBY.BUILD procedure for the old logical standby that i have to rebuild, do i have to replay this procedure in my rebuild script?
Thanks for suggestion

In the new script most of the primary related issues you can avoid as they are set during the first logical standby creation.

Enable Archivelog Mode On 2 Node RAC DATABASE

hi,
We are having 2 Node Rac 10g Database Installed on Windows.
Currently the Database is in Non Archivelog Mode.
I want to convert it to Archivelog Mode.
I come to know the steps to convert cluster database to Archivelog mode.
i.e.
set archive parameters like Disk Location and Archivelog File format.
then Convert the database in Exclusive Mode
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
then
C:\> srvctl stop database -d <Global_DB_SID>
then enable Archivelog Mode.
SQL> STARTUP MOUNT;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE
C:\> srvctl start database -d <Global_DB_SID>
But I am confuse with Do i need to RUN this commands in both the nodes seperatly or only on any one node.
Please Reply,

comments embeddedf
Node 1: OSERP1
Log on to OSERP1 Server
C:\> sqlplus sys/oracle@racdb2 as sysdba
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile ; -- this needs to be database wide
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP1\archive$\ERP1 ' SCOPE=spfile sid ='ERP1'; -- required quotes added
-- not required
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
not required to connect to other node
-- not required
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile sid =ERP2;
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP2\archive$\ERP2 ' SCOPE=spfile sid ='ERP2'; -- quotes added
-- not required, and database wide setting
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
Then following commands will be run connecting any of the instance
-- database has to be stopped first, if you stick to switching it to a non-cluster database
C:\> set ORACLE_SID=<local_instance_id>
C:\> sqlplus / as sysdba
SQL> STARTUP MOUNT;
-- wrong sequence of commands
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
-- not required (see previous steps)
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE;
6. Start the cluster database.
C:\> srvctl start database -d <Global_DB_SID>
-- There is no such thing as a <Global_DB_SID>. There is a database name.
Please note your tnsnames.ora, in a standard install, needs to have the following service names.
ERP
ERP1
ERP2
I'm not sure why you have the non-standard service_name racdb2.
Somehow it looks like you both don't understand the RAC concept, and didn't understand my answer. I had to correct several things I already corrected in my previous response. I'm not sure why I'm not getting through.
Sybrand Bakker
Senior Oracle DBA

Deleting archivelog files once applied to physical standby database

Hi,
Any procedure for automatically deleting the archivelog files after applied to physical standby database.

also pls see DataGuard: auto delete redo logs after applied to physical standby?

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

Status of Logical Standby In case of Failover to Physical Standby

I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

RMAN in 10g database deletes archivelog files before standby receives them

Hi all,
We currently have problem with our Oracle 10gR1 database on Windows 2000 server in that the RMAN backups on the primary database delete archivelogs before the standby database can receive current and new archivelogs from primary database. What happens is that RMAN backs up the archivelogs and deletes them from disk before the archivelogs are sent to the standby. The standby then looks for these archivelogs on the primary but is unable to locate them. Whenever this happens, the production database (primary) hangs and we have to restart the instance on the primary. We have our Data Guard setup in maximum performance mode so this should not happen.
As a short term fix, we have changed the backups to have RMAN backup and delete the archive logs 15 minutes older than current time so that the standby can receive the logs and not have problems. Besides this fix is there a long term solution to the problem or is it a bug in Oracle 10g? The issue came up after we upgraded from 9i to 10g and never saw it before in 9i with RMAN and Data Guard physical standby databases.
Thanks
Ben Prusinski, Oracle DBA

thanks for answer...
did you managed to make it 'work'?
according to doc. if set on standby it should:
<>
Then, these files are eligible for deletion:
Archived redo log files in the flash recovery area that
were applied on the standby database.
<>
and this is to my understanding irespective to retention policy...unfortunately report obsolete does not report applied archived logs as eligable for deletion.
How this works in your case?
regards.
goran

Forward physical standby archivelog files to a logical standby database

Similar Messages

Maybe you are looking for