Logical standby configuration details

we want to be able to gather additional information about the logical standby configuration.
How do we know if log_auto_delete is turn on or off?
How do we know if any of the tables/schema dml/ddl are in skip mode?
Thanks.

I am running 9.2.0.4, but I am still getting this error. Any idea why?
-Kelvin

Similar Messages

What are advantage and disadvantage for Physical Standy and Logical Standby

HI,
What are advantage and disadvantage for Physical Standy and Logical Standby configuration?
Thanks
Ken

Logical standby database
The key advantage for logical standby databases is that they're opened read/write, even while they're in
applied mode. That is, they can be used to generate reports and the like. It is indeed a fully functional
database. Also, additional indexes, materialized views and so on can be created.
However (this being a disadvantage) not all datatypes are supported.
Oracle (or more exactly the log apply services) uses the primary database's redo log, transforms them into
SQL statements and replays them on the logical standby database.
Physical standby database
A physical standby database is a byte for byte exact copy of the primary database. This also means that
rowids stay the same in a physical standby database environment.
Oracle (or more exactly the log apply services) uses the primary database's redo log to recover the
physical database.
A physical standby database might be opened read only; however, the received logs are in this case not
applied. When the logs are applied, the database is not accessible (it is then in a managed recovery state).
Regards,

DR for a logical standby

Friends,
Oracle version 10.2.0.4:
On the primary site, we have one non-rac primary database P1. We will create a logical standby (L1) on primary site to be used for reporting. This logical standby L1 will have its own additional indexes and materialized views.
On the Disaster recovery site, which is at a remote location, a physical standby P2 will protect the primary database P1. What should be done such that the logical database L2 on the disaster recovery site remains in sync with L1? Also, if we were to lose the primary site, what should be done such that L2 gets fed by P2 after P2 takes over as primary?
Is such a configuration possible?
thanks for any thoughts.

Hi,
If you setup a physical standby L2, which will be sync with L1 this will be a cascaded configuration.
P1 --> L1 (logical) --> L2 (physical)
But this configuration is not supported. (It used to be, but not now... ) From my blog post about cascade standby databases: (http://emrebaransel.blogspot.com/2010/08/dataguard-cascade-standby-database.html)
The Layer1 standby database cannot be a logical standby where Layer2 can be. (Oracle mentions about Layer1 logical standby configuration on 10gR2 doc, and indicates that a Layer1 logical standby will generate and transmit redo information which won’t be identical with the one between primary and Layer1 standby. As a result "Layer2 physical standby databases created from a logical standby database will be a block-for-block copy of the logical standby database and a logical copy of the original primary database.”
But it is indicated that information in Metalink bulletin 409013.1 replaces Appendix E Cascaded Destinations, of Oracle Data Guard Concepts and Administration 10g Release 2 document. Metalink bulletin 409013.1 and 11gR1 doc says that “A logical standby database cannot forward redo to another standby database” and specifies that Layer1 logical standby configuration is not supported.
A logical standby database cannot forward redo to another standby database
At the end, this means you're not able to keep a copy of L1 logical standby.
But you can have this:
P1 --> P2 (physical) --> L2 (logical)
L2 will be sync with primary (P1). In a case of disaster it will still be sync with new primary (P2). But you need to maintain its own additional indexes and materialized views.

How to remove logical standby database configuration cleanly

Hello,
We are on RHL with 11.2.0.3 DB version. Due to various unknown reasons we would like to recreate logical standby database and for that purpose I would like to cleanly remove/uninstall/drop LOGICAL STANDBY DATABASE from the DATA GUARD configuration we have.
The DG setup already has 1 PHYSICAL STANDBY DATABASE which is working fine. PRIM,PHYSICAL, and LOGICAL all are on different HOSTS. Could you please guide or suggest us exact MOS Doc id regarding this? I have found one MOS Doc id which is close enough but its steps include removing dg configuration completely which I don't want. Only Logical Standby database needs to be remove cleanly so that it can be installed again properly.
We are using GRID CONTROL and DATA GUARD BROKER.
Bundle of thanks in advance.
Best Regards

Hello;
I would review this Oracle note:
How to remove a Data Guard Configuration from Primary Database (Doc ID 733794.1)
Best Regards
mseberg

Configuration of the Physical & Logical standby servers on the same machine

I've encoutered a problem to connect to one of the standby servers .
I created a DataGuard in 10.2. Primary on 1 machine, 1 physical standby and 1 logical standby on another machine (both phy and logical in same machine)
I first created a primary then a physical standby. I've got no problem at all.
But when I created a logical standby server on the same machine with the physical then I could not connect to both phy and logical . I can connect to either one of them.
According to DataGuard setup, the db_name must be the same in primary and all standby servers. This is fine when each of the primary or the standby installed in a separate machine.
The db_name of the physical = rolex
The db_name of the logical = rolex
When we have more than one instance in the same machine, we just set the ORACLE_SID = db_name ( or instance), then connect to it.
If I connect to the physical, then I try to connect to the logical, it goes to the physical or vice versus.
Does anyone have the solution ?
QN

DB_UNIQUE_NAME parameter will be the seperator.
give DB_UNIQUE_NAME parameters different names and set ORACLE_SID with DB_UNIQUE_NAME name you gave
DB_NAME is the primary instances database name DB_UNIQUE_NAME is given for standby instances database name

Local logical standby and remote physical standby

Dear All,
My database version is 10.2.0.1.0(production) and Operating System Linux x86-64 OS Version Red Hat Enterprise 4
Below is my configuration details:
Rprimary Database:Two Nodes RAC
StandBy Database LOCAL:Standalone database
Standby Database Remote:Two Node RAC
So,my question is, i want my local physical DR to convert into logical standby and
Remote DR will operate as physical standby as it IS.
sql>EXECUTE DBMS_LOGSTDBY.BUILD
After executing the above statement in my production primary database will there be any performance HIT.
And another important is that my above statement shouldn't affect my remote physical DR database.
Just the local DR should get converted into logical standby database
Thanks and Regards
Monoj Das

monoj wrote:
Dear All,
My database version is 10.2.0.1.0(production) and Operating System Linux x86-64 OS Version Red Hat Enterprise 4
Below is my configuration details:
Rprimary Database:Two Nodes RAC
StandBy Database LOCAL:Standalone database
Standby Database Remote:Two Node RAC
So,my question is, i want my local physical DR to convert into logical standby and
Remote DR will operate as physical standby as it IS.
sql>EXECUTE DBMS_LOGSTDBY.BUILD
After executing the above statement in my production primary database will there be any performance HIT.
And another important is that my above statement shouldn't affect my remote physical DR database.
Just the local DR should get converted into logical standby database
Thanks and Regards
Monoj DasIn any Data Guard environment, you can have either physical or logical or even mixed[physical + logical]
There will be no performance issue if you run the package for logical standby DBMS_LOGSTDBY.BUILD , This package provides you to manage even logical standby database.

CPU patch procedure with physical and logical standby database in place

Hello All,
I've also placed this in the Upgrades forum, but perhaps this is the best place to have put it.
I'm trying to compile a decent set of steps for applying the CPUOCT2008 patch to our production RAC cluster which has both a logical and physical standby in place. I've read a tonne of documentation, including the CPU readme, DOCID 437276.1 and 278641.1. I''ve also read through the Upgrading Databases in a Data Guard Configuration chapter of Dataguard Concepts and Administration. The last doc mentioned is really for upgrading a full version of Oracle rather than applying a CPU (at least I think that's the case). DocID 437276.1 is rather sparse on details.
I guess what I'm trying to understand is the proper method for applying the patch with the logical standby in place. The physical standby looks pretty straightforward. After running opatch on it as well, it will basically have all of the changes applied to the primary shipped over and applied as per the normal primary/standby relationship. Will the same be true for the logical (having applied the patch, and then re-enabling SQL apply)? Should I aim to have it work that way? By that I mean start it up and re-enable sql apply and then upgrade the primary. Or, am I to apply the catcpu.sql script to it as well before re-enabling the sql apply? Am I wrong in regards to the physical standby as well i.e. should the catcpu also be applied directly to it?
Thanks very much in advance.
Cheers,
Chris
Edited by: chris.baron on Dec 12, 2008 11:38 AM

Given the fact that your system is far from main-stream I'd recommend opening an SR with Oracle Support Services (metalink) and asking them.
If you would like to publish a White Paper on your experience after you have successfully completed the project let me know off-line.

Apply CPUOCT2008 with both a physical and logical standby in place

Hello All,
I'm trying to compile a decent set of steps for applying the CPUOCT2008 patch to our production RAC cluster which has both a logical and physical standby in place. I've read a tonne of documentation, including the CPU readme, DOCID 437276.1 and 278641.1. I''ve also read through the Upgrading Databases in a Data Guard Configuration chapter of Dataguard Concepts and Administration. The last doc mentioned is really for upgrading a full version of Oracle rather than applying a CPU (at least I think that's the case). DocID 437276.1 is rather sparse on details.
I guess what I'm trying to understand is the proper method for applying the patch with the logical standby in place. The physical standby looks pretty straightforward. After running opatch on it as well, it will basically have all of the changes applied to the primary shipped over and applied as per the normal primary/standby relationship. Will the same be true for the logical (having applied the patch, and then re-enabling SQL apply)? Should I aim to have it work that way? By that I mean start it up and re-enable sql apply and then upgrade the primary. Or, am I to apply the catcpu.sql script to it as well before re-enabling the sql apply? Am I wrong in regards to the physical standby as well i.e. should the catcpu also be applied directly to it?
Thanks very much in advance.
Cheers,
Chris

Given the fact that your system is far from main-stream I'd recommend opening an SR with Oracle Support Services (metalink) and asking them.
If you would like to publish a White Paper on your experience after you have successfully completed the project let me know off-line.

Import a schema (tables, Views, Stored Procedures) on logical standby

Hi,
We have a logical standby for reporting purpose. The logical standby build through data guard
we need to import a new user in logical standby using import utility. The user dump contain tables, views, procedures, packages, roles).
The new user import has to go in users tablespace.
Is is possbile to import a new user in logical standby and what are the steps.
Thanks in advance

Hi,
Can you give me more details about your envirnoment configuration, O/S, DB version.
But generally i don't think that is this possible becuase as you know standby only for cloning the primary database, so you can import it on the production then it will be transfered to the logical standby database.
Regards;

Logical Standby Database in NOARCHIVE Mode

Hi,
I have configured a Logical Standby Database for Reporting purposes. A Physical Standby Database is running for MAA. i.e. in case of Role Transition (switch/Failover) the Physical Stdby Db will get the role of the Primary.
The logical standby database is creating a lot of Archive Redologs files, nearly every minute. Redolog files are 50MB and there is no work done in db during the time. I'm NOT using Standby Redolog files.
Is there a need for logical standby database to be in NOARCHIVELOG mode? The Primary is definatley in ARCHIVELOG mode.
Thanks for any responses.
regards
Sahba

hi,
well there are two things to the above:-
1. there was an archive file nearly every minute:
this is due to a db recovery. for some reason, the db was in inconsistent state, after a sudden shutdownof the OS. I was on a test environment, on windows vista, unfortunately. unimportant ... a reboot solved it.
2. Logical standby db in NOARCHIVE MODE when setup for the purpose of Reporting.
As long as the MAA configured for the primary db, such as physical standby db, and a second, the logical standby db setup purely for the purpose of reporting, which then can run with NOARCHIVELOG mode, after converting the physical standby db to logical.
logical standby db uses Streams architecture, so this method brings cost, time and performance advantages to the customer.
regards
Sahba

Logical standby stuck at initializing SQL apply only coordinator process up

Hi
OS: solaris 5.10
Hardware: sun sparc
Oracle database: 11.2.0.1.0
Primary database name: asadmin
Standby database name: test
I had been trying to convert a physical standby to logical standby database. Both the primary and standby reside on the same machine.
The physical standby was created with a hot backup of primary.
I had been following document id 278371.1 to convert the physical to logical standby and used the following steps:
Relevant init parameters on primary:
*.db_name='asadmin'
*.db_unique_name='asadmin'
*.log_archive_config='dg_config=(asadmin,test)'
*.log_archive_dest_1='location=/u01/asadmin/archive valid_for=(all_logfiles,all_roles) db_unique_name=asadmin'
*.log_archive_dest_2='SERVICE=test async valid_for=(online_logfiles,primary_role) db_unique_name=test'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.fal_client='asadmin'
*.fal_server='test'
*.remote_login_passwordfile='EXCLUSIVE'
Relevant init parameters on standby database:
*.db_name='test' -- Was asadmin before I renamed the DB during conversion to logical standby
*.db_unique_name='test'
*.log_archive_dest_1='location=/u01/test/archive valid_for=(all_logfiles,all_roles) db_unique_name=test'
*.log_archive_dest_2='service=asadmin async valid_for=(online_logfiles,primary_role) db_unique_name=asadmin'
*.log_archive_dest_state_1=enable
*.log_archive_dest_state_2=defer
*.remote_login_passwordfile='EXCLUSIVE'*.fal_server=test
*.fal_client=asadmin
Steps on primary:
1) alter system set log_archive_dest_state_2=defer;
2) shutdown immediate;
3) Made sure that the physical standby has applied all of the redo sent to it following the shutdown.
4) startup mount;
5) ALTER DATABASE BACKUP CONTROLFILE to '/home/oracle/control01.ctl';
6) ALTER SYSTEM ENABLE RESTRICTED SESSION;
7) ALTER DATABASE OPEN;
8) Verified that the supplemental logging is on.
9) ALTER SYSTEM ARCHIVE LOG CURRENT;
10) Checked for the checkpoint change no. at this point which is 72403818 and is present in archive log file 1_62_775102253.dbf
11) EXECUTE DBMS_LOGSTDBY.BUILD;
12) ALTER SYSTEM ARCHIVE LOG CURRENT;
13) Checked for the archive log containing dictionary build which is 1_64_775102253.dbf
14) ALTER SYSTEM DISABLE RESTRICTED SESSION;
Details of archive logs and related checkpoint change nos:
NAME FIRST_CHANGE# NEXT_CHANGE#
/u01/asadmin/archive/1_61_775102253.dbf 72402901 72403817
/u01/asadmin/archive/1_62_775102253.dbf 72403817 72404069
/u01/asadmin/archive/1_63_775102253.dbf 72404069 72404211
/u01/asadmin/archive/1_64_775102253.dbf 72404211 72405700
Steps on standby:
1) shutdown immediate;
2) Copy the archivelog file 61(was created at primary after apply stopped at standby), 62(contains checkpoint no. 72403818), 63 and 64(contains dictionary build). Copy the backup controlfile from step 5 above to the controlfile location in standby init.
3) startup mount;
4) Rename all datafiles and redo log files (including standby redo log files) to the correct path on standby.
5) alter database recover automatic from '/u01/test/archive' until change 72405700 using backup controlfile; -- This completed error-free
6) alter database guard all; -- this completed error free
7) alter database open resetlogs; -- this completed error free.
8) nid target=sys/oracle12 dbname=test
9) Changed the db_name in init file to new name test.
10) Added a tempfile to temp tablespaces.
11) ALTER DATABASE REGISTER LOGICAL LOGFILE '/u01/test/archive/1_61_775102253.dbf'; -- ORA-16225: Missing LogMiner session name for Streams
12) ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL 72405700; -- This completed error free.
Also enabled the log_archive_dest_state_2 on primary.
After this output from some views:
SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
SESSION_ID STATE
1 INITIALIZING
SQL> SELECT SID, SERIAL#, SPID, TYPE FROM V$LOGSTDBY_PROCESS;
SID SERIAL# SPID TYPE
587 22 15476 COORDINATOR
SELECT PERCENT_DONE, COMMAND
FROM V$LOGMNR_DICTIONARY_LOAD
WHERE SESSION_ID = (SELECT SESSION_ID FROM V$LOGSTDBY_STATE);
PERCENT_DONE
COMMAND
0
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16111: log mining and apply setting up
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
72405700 72411501
SELECT THREAD#, SEQUENCE#, FILE_NAME FROM DBA_LOGSTDBY_LOG L
WHERE NEXT_CHANGE# NOT IN
(SELECT FIRST_CHANGE# FROM DBA_LOGSTDBY_LOG WHERE L.THREAD# = THREAD#)
ORDER BY THREAD#,SEQUENCE#;
no rows selected
SQL> SELECT EVENT_TIME, STATUS, EVENT
FROM DBA_LOGSTDBY_EVENTS
ORDER BY EVENT_TIMESTAMP, COMMIT_SCN; 2 3
EVENT_TIME STATUS EVENT
14-FEB-12 02:00:50 ORA-16111: log mining and apply setting up
14-FEB-12 02:00:50 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:20:11 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:20:39 ORA-16111: log mining and apply setting up
14-FEB-12 02:20:39 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:54:15 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:57:38 ORA-16111: log mining and apply setting up
EVENT_TIME STATUS EVENT
14-FEB-12 02:57:38 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 03:01:36 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 03:13:44 ORA-16111: log mining and apply setting up
14-FEB-12 03:13:44 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 04:32:23 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:34:17 ORA-16111: log mining and apply setting up
14-FEB-12 04:34:17 Apply LWM 72405699, HWM 72405699, SCN 72405699
EVENT_TIME STATUS EVENT
14-FEB-12 04:36:16 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:36:21 ORA-16111: log mining and apply setting up
14-FEB-12 04:36:21 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 05:15:22 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 05:15:29 ORA-16111: log mining and apply setting up
14-FEB-12 05:15:29 Apply LWM 72405699, HWM 72405699, SCN 72405699
I also greped for lsp and lcr processes and found that lsp is up but do not see any lcr.
The logs are getting transported to the archive destination on standby whenever they are archived on primary but are not getting applied to standby.
Also in case the standby is down while a log is generated on primary it is not automatically transported to standby once the standby is up, means gap resolution is also not working.
I see the following in alert log every time I try to restart the log apply, everything seems to be stuck at initialization.
ALTER DATABASE START LOGICAL STANDBY APPLY (test)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Tue Feb 14 05:15:28 2012
LSP0 started with pid=28, OS id=23391
Completed: alter database start logical standby apply immediate
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 0
-- NOTHING AFTER THIS

Hello;
I noticed some of your parameters seem to be wrong.
fal_client - This is Obsolete in 11.2
You have db_name='test' on the Standby, it should be 'asadmin'
fal_server=test is set like this on the standby, it should be 'asadmin'
I might consider changing VALID_FOR to this :
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
Document 278371.1 is showing its age in my humble opinion.
-----Wait on this until you fix your parameters----------------------
Try restarting the SQL Apply
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
Use these statements to trouble shoot :
SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
mseberg
Edited by: mseberg on Feb 14, 2012 7:37 AM

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

Archive log shipping error in Logical standby database

Hi,
We have Primay and logical database configuration both in RAC in Production. both database are in 10.2.0.4.
Everyday we having issue of some archivelog not transfered to logical server around 2AM. I am having good exposure in Logical/Log minor/Goldgendate and can say fal server/client server configuration is correct.
Can you guys please give some input of what can cause this.
Yes we take RMAN backup of both database around 1:30 using control file instead of recovery catalog and I doubt this put lock on control file and cause this issue.
I would be glad of you could help me out in this.
Thanks a lot!
Pradeep
Below is the configuration of archive/fal on both database.
PIP1REP2 is logical database(instance 2) where apply process is running/configured.
Primary server configuration on (PIP11) (same are on other instances).
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP2
fal_server string PIP11
SQL> sho parameter archive
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=+ARCH01
log_archive_dest_2 string SERVICE=pip1rep2 lgwr async
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string ENABLE
llog_archive_local_first boolean TRUE
log_archive_max_processes integer 10
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
Logical server configuration
SQL> sho parameter fal
NAME TYPE VALUE
fal_client string PIP1REP
fal_server string pip11, pip12, pip13, pip14, pi
p15
SQL> sho parameter archive
NAME TYPE VALUE
alog_archive_dest_1 string LOCATION=+ARCH01/PIP1REP valid
for=(onlinelogfiles, all_rol
es) db_unique_name=pip1rep
log_archive_dest_2 string LOCATION=+ARCH01/PIP1REP/ARCH_
DEST2_STANDBY_LOGS VALID_FOR=(
STANDBY_LOGFILES,STANDBY_ROLE)
db_unique_name=pip1rep
log_archive_dest_state_1 string enable
log_archive_dest_state_2 string enable
log_archive_local_first boolean TRUE
log_archive_max_processes integer 20
log_archive_min_succeed_dest integer 1
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string +ARCH01

Do you think creating recovery catalog will resolve it?
Yes, I do. (But I do not know for sure)
If it helps when I got to this part I decided to backup either the Primary or the Standby, but not both.
I decided Primary only and documented how to recreate my standby without downtime.
I hope this helps.
regards.

Doubt regarding switchover from logical standby to primary

I am using Oracle 10g databases on Linux environment
I was trying creating a data guard configuration and once I was successfully done I created a logical standby database from the physical standby . Then I was trying to do a switchover .
By mistake I gave the prepare switchover command in the logical standby before executing it in the primary . And then when I gave it in the primary both the status turned to be "PREPARING SWITCHOVER"
In logical standby
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO PRIMARY;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
PREPARING SWITCHOVER
In primary
SQL> ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY;
Database altered.
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
PREPARING SWITCHOVERNow I am not able to commit any of them to primary or logical standby
In primary
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;
ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY
ERROR at line 1:
ORA-16217: prepare to switchover has not completed
ORA-06512: at line 1
In logical standby
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
ALTER DATABASE commit TO SWITCHOVER TO PRIMARY
ERROR at line 1:
ORA-16109: failed to apply log data from previous primaryLet me know what should be done now ? Is there anyway to solve this issue ?

Can you try using the following first on Primary and then on Standby?
ALTER DATABASE PREPARE TO SWITCHOVER CANCEL;

Logical standby is in Normal State but it dosent apply any changes.

I had a Rac active data guard 11.2.0.3   and i converted it to logical standby database.
My soluition was same as this link : http://docs.oracle.com/cd/E11882_01/server.112/e41134/create_ls.htm#SBYDB4734
After that configuration was complete,
When i change for example 1 row in a table in primary server, it does'nt Apply in standby server .I have checked alert log file and i have not seen any error in alert logfile.
Primary parameter file:
*.db_name='KS'
*.db_unique_name='KS'
*.dg_broker_start=true
*.fal_client='KS'
*.fal_server='KSSTBY_standby'
*.log_archive_config='DG_CONFIG=(KS,ksstby)'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=KS'
*.log_archive_dest_2='SERVICE=KSSTBY_standby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ksstby'
*.log_archive_dest_3='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=KS'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.log_archive_format='archive_%s_%t_%r'
*.log_file_name_convert='+DATA/KSSTBY','+DATA/KS','+fra/KSSTBY','+fra/KS'
*.db_file_name_convert='+DATA/KSSTBY','+DATA/KS'
*.standby_file_management='auto'
Logical standby parameter file:
*.db_name='KS'
*.db_unique_name='ksstby'
*.fal_client='ksstby'
*.fal_server='KS_primary'
*.log_archive_config='DG_CONFIG=(KS,ksstby)'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ksstby'
*.log_archive_dest_2='SERVICE=KS_primary LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=KS'
*.log_archive_dest_3='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=ksstby'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.log_archive_format='archive_%s_%t_%r'
*.log_file_name_convert='+DATA/KS','+DATA/KSSTBY','+fra/KS','+fra/KSSTBY'
*.db_file_name_convert='+DATA/KS','+DATA/KSSTBY'
*.standby_file_management='auto'
The Status of Standby server :
select sequence#,applied from dba_logstdby_log;
    SEQUENCE# APPLIED
1 5486 CURRENT
2 5487 CURRENT
3 5488 CURRENT
4 5489 NO
5 5490 NO
6 5491 NO
7 5492 NO
8 5493 NO
9 5494 NO
select * from v$logstdby_stats;
    NAME VALUE
1 logminer session id 1
2 number of preparers 1
3 number of appliers 5
4 server processes in use 9
5 maximum SGA for LCR cache (MB) 30
6 preserve commit order TRUE
7 transaction consistency FULL
8 coordinator state INITIALIZING
9 coordinator startup time 28-APR-15
select * from v$logstdby_state;
    PRIMARY_DBID SESSION_ID REALTIME_APPLY STATE
1 3130490787 1 Y APPLYING
Please help to me.

Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
* [[Troubleshooting extensions and themes]]
In Firefox 4 [http://kb.mozillazine.org/Safe_mode Safe mode] disables extensions and disables hardware acceleration.
Check if there is an update available for your graphics display card driver.
* Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
In Firefox 4 you can use one of these to start in <u>[[Safe mode]]</u>:
* Help > Restart with Add-ons Disabled
* Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)

Logical standby configuration details

Similar Messages

Maybe you are looking for