Logical Standby - LGWR or ARCH mode

After reading the [Setting the Data Protection Mode of a Data Guard Configuration|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1183694] , I'm still confusing about it!
What is the main difference between LGWR or ARCH when implementing a logical standby database, if I want "Maximum Performance" mode?
What the advantages and disadvantages of them? In real situation, which are used mostly by business?
Thanks!

Using the LGWR process differs from ARCn processing because instead of waiting for the online redo log to switch at the primary database and then writing the entire archived redo log at the remote destination all at once, the LGWR process selects a standby redo log file at the standby site that reflects the log sequence number (and size) of the current online redo log file of the primary database. Then, as redo is generated at the primary database, it is also transmitted to the remote destination. The transmission to the remote destination will either be synchronous or asynchronous, based on whether the SYNC or the ASYNC attribute is set on the LOG_ARCHIVE_DEST_n parameter. Synchronous LGWR processing is required for the maximum protection and maximum availability modes of data protection in Data Guard configurations.
Regards,
Muzafar

Similar Messages

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 in noarchive mode

Hello,
does anybody know if it is possible to run a logical standby (10gR2) in noarchivelog mode?
For my understanding it should be possible, why not... But I can't find a piece of documentation which prove this.
Thanks in advance,
Boris...

I also was curious if setting up a Logical Standby in noarchivelog mode was possible. It looks like it is...
We use this simply as a reporting copy of our data. Our analysts do not change any of this data. They just need it to be fairly current (~3 days). At this point, there isn't any need to generate archivelogs so we want to disable the feature to minimize our maintenance and our storage requirements.
STANDBY DB:
SQL> select log_mode, open_mode from v$database;
LOG_MODE     OPEN_MODE
ARCHIVELOG   READ WRITE
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Database mounted.
SQL> alter database noarchivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Database altered.Then I created an object on the production server:
SQL> create table testuser.noarchivelog_testing as select * from dba_objects;
Table created.
SQL> alter system switch logfile;
System altered.
Mon Jun 22 11:13:26 2009
Beginning log switch checkpoint up to RBA [0xe6.2.10], SCN: 1031235046
Mon Jun 22 11:13:26 2009Now I see it on the standby:
Mon Jun 22 11:13:43 2009
RFS LogMiner: RFS id [25920] assigned as thread [1] PING handler
RFS[1]: Archived Log: '/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc'
Mon Jun 22 11:13:46 2009
RFS LogMiner: Registered logfile [/oracle/LH1/oraarch/LH1arch_1_229_680639127.arc] to LogMiner session id [1]
Mon Jun 22 11:13:48 2009
LOGSTDBY status: ORA-16204: DDL successfully applied
Mon Jun 22 11:13:51 2009
LOGMINER: End mining logfile: /oracle/LH1/oraarch/LH1arch_1_229_680639127.arc
SQL> select count(*) from testuser.noarchivelog_testing;
COUNT(*)
     24444

Physical vs Logical standby database

In the Oracle HA guide, it is mentioned that we must take Logical backup "in addition" to Physical backup (not instead of Physical Backup)
If I run have two systems i.e a Primary System and a Logical standby database system , is it not sufficient protection ? If the primary fails, can I not recover the primary system using the nightly backup I take from the Logical Standby Database.
If it is not sufficient protection, what exactly I will lose ?
Assume I take the nightly complete hot backup backup from the Logical Standby Database instead of the Primary System to save CPU cycles of the primary system.
In other words, it is said that "physical standby database provides zero data loss without any allowance for data divergence" -- What exactly is meant here ?

Thanks Werner for the reply.
1. If there is a human error (dropping a table by mistake), it will be applied to the standby database irrespective of whether it is physical standby or Logical standby. I am unable to see any advantage with Logical standby database in this case. Am I missing something here ?
Or are there any other type of user errors where Logical standby provides an advantage ? Can you please name some ?
2. If I backup from the logical database and if I am willing to "restore" (instead of recover) the primary from this backup in case of a primary failure, is it not the same effort ?
3. Can't we set up a Logical Standby with Maximum Protection Mode ?
I am aware physical standby offers a better performance and it has no data type restrictions. I do not care about these two. Also, I am aware of the extra features provided by Logical database.
Overall, I am trying to see whether physical standby database has any "feature" which I will miss with Logical standby database. I tried my best with Oracle documentation, but I could not get a clear answer.
Any help is appreciated.

Is it possible to have a 10g (R1) LOGICAL standby db in read-ONLY mode?

From what I've gathered reading the 10g (R 1) docs, the logical standby turns read-only when applying sql, and then in read-write mode otherwise. I have to meet a requirement that the remote database be strictly in read-only mode the entire time (so as to not risk writing to it), as well as being as up-to-date as possible off the primary. (Hence I decided on the logical vs. the physical) Does anyone pls. know if I can keep the logical read-only all the time?
Much appreciated,
Sophie

Oh, Ok. I guess i interpreted it differently. The direct quote from the docs: "Although the logical standby database is opened in read/write mode, its target tables for the regenerated SQL are available only for read-only operations." So I guess what it means, as you suggest, is the entire set of tables from the primary, and not just those few that happened to be updated at that particular time frame, are kept in read-only the entire time...

Open Mode for Logical Standby

HI,
I have a logical standby. It's v$database.open_mode shows READ WRITE
Q1. I am correct in assuming that the Database is only writable for tables that are not in the primary ?
Q2. Are the tables that are also in the primary, in effect in read only mode on the logical standby ? Am I able to see the mode of these tables to prove they are read only ?
thanks,
Jim

Hello;
User modification to tables on the Logical Standby has three possible settings:
ALL
STANDBY
NONE
You can check the mode using this query:
SELECT GUARD_STATUS FROM V$DATABASE;
If you try to insert data into a table and the mode is 'ALL' and you are not the SYS user you should get an error
ORA-16224
If you want users to modify non-replicated standby tables then you need to change the mode from its default of 'ALL'.
You can use DBA_LOGSTDBY_SKIP to find non-replicated tables ( the ones with skip rules ).
If you create new objects consider a naming convention that allows you to easily see the write status.
Best Regards
mseberg

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

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)

Standby Database (Archive Log Mode)

I'm going to be setting up a standby database.
I understand that the primary database must be in archive log mode.
Is there any reason for the standby database to be in archivelog mode?

Since your primary Db is in archive log mode, so will be your standby, when it is made primary.But. you can use STANDBY REDO LOGS from 9i version, where these Standby Redo Logs then store the information received from the Primary Database.
As per metalink:-
>
Standby Redo Logs are only supported for the Physical Standby Database in Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs are only used if you have the LGWR activated for archival to the Remote Standby Database.If you have Standby Redo Logs, the RFS process will write into the Standby RedoLog as mentioned above and when a log switch occurs, the Archiver Process of the Standby Database will archive this Standby Redo Log to an Archived Redo Log, while the MRP process applies the information to the Standby Database. In a Failover situation, you will also have access to the information already written in the Standby Redo Logs, so the information will not be lost.
>
Check metalink Doc ID: Note:219344.1
Regards,
Anand

Logical Standby: WAITING FOR DICTIONARY LOGS status.

Hi,
I have just configured a Logical Standby from Physical Standby, I followed all steps explained in section 4.2.1 from the Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) documentation, but now my logical standby stay on WAITING FOR DICTIONARY LOGS more than 3 days, all archives from primary DB have been replicated and registered, I don't understand whats
wrong.
SQL> SELECT * FROM V$LOGSTDBY_STATE;
PRIMARY_DBID SESSION_ID
REALTIME_APPLY
STATE
144528764 1
Y
WAITING FOR DICTIONARY LOGS
Fri Apr 8 18:05:47 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157573.arc] to LogMiner session id [1]
Fri Apr 8 18:10:55 2011
RFS LogMiner: Client enabled and ready for notification
Fri Apr 8 18:10:55 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/redo2a/dbp/redo4a_stb.log'
Fri Apr 8 18:10:58 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157574.arc] to LogMiner session id [1]
Fri Apr 8 18:15:54 2011
RFS LogMiner: Client enabled and ready for notification
Fri Apr 8 18:15:54 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 3: '/redo1a/dbp/redo3a_stb.log'
Fri Apr 8 18:15:57 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157575.arc] to LogMiner session id [1]Thanks in advance.
My Oracle version is: 10.2.0.4
My Platform is: AIX 6.1
Nataly.

On standby alert no error messages found.
RFS LogMiner: Client enabled and ready for notification
Mon Apr 11 18:09:58 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/redo2a/mefsf/redo4a_stb.log'
Mon Apr 11 18:10:01 2011
RFS LogMiner: Registered logfile [/archive/mefsf/581440892_1_0000157782.arc] to LogMiner session id [1]
Mon Apr 11 18:23:16 2011
RFS LogMiner: Client enabled and ready for notification
Mon Apr 11 18:23:16 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 3: '/redo1a/mefsf/redo3a_stb.log'
Mon Apr 11 18:23:18 2011
RFS LogMiner: Registered logfile [/archive/mefsf/581440892_1_0000157783.arc] to LogMiner session id [1]Continues
On primary alertlog,
There is a common message:
ORACLE Instance bdprod - Archival Error. Archiver continuing.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc4_2818414.trc:
ORA-00308: cannot open archived log '/archive/bdprod/581440892_1_0000157545.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Mon Apr 11 18:22:57 2011
FAL[server, ARC4]: FAL archive failed, see trace file.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc4_2818414.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Apr 11 18:22:57 2011
ORACLE Instance bdprod - Archival Error. Archiver continuing.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc1_7078038.trc:
ORA-00308: cannot open archived log '/archive/bdprod/581440892_1_0000157546.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Mon Apr 11 18:22:57 2011
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc1_7078038.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Apr 11 18:22:57 2011
ORACLE Instance bdprod - Archival Error. Archiver continuing.

Archive destination on Logical Standby

Dear colleagues,
A physical standby database writes archivelogs in '/oradata3/iclgstdb/archivelog' destination because a parameter standby_archive_dest set in '/oradata3/iclgstdb/archivelog':
SQL> sho parameter standby
NAME                                 TYPE        VALUE
standby_archive_dest                 string      /oradata3/iclgstdb/archivelog
standby_file_management              string      AUTO
When I switch the physical to a logical standby then archivelogs are written in '$ORACLE_HOME/dbs/arch' destination:
SQL> ARCHIVE LOG LIST
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /ora/OraHome11203/dbs/arch
Oldest online log sequence     1
Next log sequence to archive   2
Current log sequence           2
But I don't see this destination in v$parameter view.
How can I change "Archive destination /ora/OraHome11203/dbs/arch" to '/oradata3/iclgstdb/archivelog'?

Hi,
Above answered given by one of our DBA friend is correct...just want to add few things,
We need to update both the parameters related to log_archive_dest_1 and log_archive_dest_2 on primary and standby location,
on primary,
log_archive_dest_1 would be local directory or would be ASM...
log_archive_dest_2 would be standby database service name and archive will generated on standby location location...
Correct ans:-
"If your version of Oracle is 11 then STANDBY_ARCHIVE_DEST parameter is deprecated.
set LOG_ARCHIVE_DEST_1 to '/oradata3/iclgstdb/archivelog on the standby"
Regards,
GRB

Logical standby and Primary keys

Hi All,
Why primary keys are essential for creating logical standby database? I have created a logical standby database on testing basis without having primary keys on most of the tables and it's working fine. I have not event put my main DB in force logging mode.

I have not event put my main DB in force logging mode. This is because, redo log files or standby redo logfiles transforms into set of sql statements to update logical standby.
Have you done any DML operations with nologging options and do you notice any errors in the alert.log? I just curious to know.
But I wanted to know that, while system tablespace in hot backup mode,In the absence of both a primary key and a nonnull unique constraint/index, all columns of bounded size are logged as part of the UPDATE statement to identify the modified row. In other words, all columns except those with the following types are logged: LONG, LOB, LONG RAW, object type, and collections.
Jaffar

Logical Standby databases

Hi,
When we say "Logical Standby Databases are logically identical to primary databases although the physical organization and structure of the data can be different." what does it exactly means?
Does it mean that in logical standby tablespace name, schema name, table name, column names etc can be different and still has the same data as primary?
Does it mean that we can exclude indexes and constraints as present in primary?
Only the data should match with primary word by word, value by value?
I am asking this as i have never worked in a logical standby database but i seriously want to know.
Please answer.
Regards,
SID

Physical standby differs from logical standby:
Physical standby schema matches exactly the source database.
Archived redo logs and FTP'ed directly to the standby database which is always running in "recover" mode. Upon arrival, the archived redo logs are applied directly to the standby database.
Logical standby is different from physical standby:
Logical standby database does not have to match the schema structure of the source database.
Logical standby uses LogMiner techniques to transform the archived redo logs into native DML statements (insert, update, delete). This DML is transported and applied to the standby database.
Logical standby tables can be open for SQL queries (read only), and all other standby tables can be open for updates.
Logical standby database can have additional materialized views and indexes added for faster performance.
Installing Physical standbys offers these benefits:
An identical physical copy of the primary database
Disaster recovery and high availability
High Data protection
Reduction in primary database workload
Performance Faster
Installing Logical standbys offer:
Simultaneous use for reporting, summations and queries
Efficient use of standby hardware resources
Reduction in primary database workload
Some limitations on the use of certain datatypes

Logical standby server stopped applying changes

Hi
I set up a logical standby database with database guard and it worked fine for some time. But recently I had to use it again and discovered that applying changes from primary database to secondary database just stopped working. I see in V$ARCHIVED_LOG one entry per day. If I restart the logical standby then the changes from primary server are also applied. But if I just make a change on primary server and even call 'alter system switch logfile' then I see an entry in V$ARCHIVED_LOG on primary server but not on standby server (BTW in general there are much more entries in this view on the primary server). I checked pairs of log files indicated by the parameter *.log_file_name_convert in standby server's spfile: their last changed date is always the same.
I will paste spfile of my standby server (dh5). Primary server name is dh2.
dh2.__db_cache_size=79691776
dh5.__db_cache_size=96468992
dh2.__java_pool_size=4194304
dh5.__java_pool_size=4194304
dh2.__large_pool_size=4194304
dh5.__large_pool_size=4194304
dh2.__shared_pool_size=71303168
dh5.__shared_pool_size=54525952
dh2.__streams_pool_size=0
dh5.__streams_pool_size=0
*.audit_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/adump'
*.background_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5/control01.ctl'
*.core_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='dh2','dh5'
*.db_name='dh7'
*.db_recovery_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.db_unique_name='dh5'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=dh2XDB)'
*.fal_client='dh5'
*.fal_server='dh2'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dh2,dh5)'
*.log_archive_dest_1='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5_local
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=dh5'
*.log_archive_dest_2='SERVICE=dh2 LGWR ASYNC
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=dh2'
*.log_archive_dest_3='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5
VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLES)
DB_UNIQUE_NAME=dh5'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_dest_state_3='ENABLE'
*.log_archive_format='%t_%s_%r.arc'
*.log_archive_max_processes=30
*.log_file_name_convert='oradata/dh2/redo01.log','flash_recovery_area/DH5/onlinelog/o1_mf_4_5x0o5grc_.log','oradata/dh2/r
edo02.log','flash_recovery_area/DH5/onlinelog/o1_mf_5_5x0o61mw_.log','oradata/dh2/redo03.log','flash_recovery_area/DH5/on
linelog/o1_mf_6_5x0o63gj_.log'
*.nls_language='AMERICAN'
*.open_cursors=300
*.pga_aggregate_target=311427072
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.undo_management='AUTO'
*.undo_retention=3600
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/udump'
Thanks in advance for any help.
JM

Hi,
Nice to hear you issue got resolved.
It is good practice to keep monitoring the progress of SQL apply on the logical standby on a regular basis.
You can mark my response as helpful if it has helped you.
Regards
Anudeep

Logical standby as read only

we are using 3 node RAC in 10g R2 and we have been requested to create one physical(for DR) and one logical standby(for reporting) for the primary database.we created both successfully.
everything worked fine until i opened the logical standby database as read only.the sql apply stops once i opened the logical standby as readonly.
once i shut it down and opened in read write mode the sql apply works fine.
is there any way to open the logical standby only in read only,because we want to use the database only for reporting and doesnt want anyone creating anything in the database.
anyhelp is appreciated
thanks

Users (other than SYSDBA) cannot create anything in a Logical standby unless someone with SYSDBA privs executed ALTER DATABASE GUARD STANDBY; or ALTER DATABASE GUARD NONE;
STANDBY says they can create objects that they have the normal privs to do but they cannot affect/change anything that SQL Apply is maintaining (i.e. the stuff coming in from the Primary)
NONE says they still cannot create/change anything they do not have the privs to do but they CAN mess with the tables that SQL Apply is maintaining which would toast your standby so you would never do that.
It is lightly documented at http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_1004.htm#i2110829 :^(
The default for the GUARD is ALTER DATABASE GUARD ALL; which gets set for you when you created the Logical Standby following the procedures at http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#g105412
Larry

Logical Standby - LGWR or ARCH mode

Similar Messages

Maybe you are looking for