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

Similar Messages

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.

When to use Real Time Apply for Logical standby..!!

Hello All,
I have been trying many ways to speed up the archival on primary and improve sql apply on logical standby, but still we are getting about 45-50 mins of delay between primary and logical standby.
We wanted to have our transactions applied on logical standby within couple minutes. Which i guess wont be possible in async mode.
That's why i am planning to implement Real Time apply between primary and logical standby.
Now since both our databases are too far away from each other (Primary is in US and logical is in India) would it be recommended to implement real time apply in such scenario? And if implemented would it affect Primary DB Performance?
Also if there might be some packet loss or network hitch would Primary will try again and keep logical DB in Sync with Primary?
Any help or suggestions would be great.
Thanks.

yes, real time apply is recommended in your scenario.
however due to the geographical distance between your primary and standby; I would suggest to keep your standby in current mode - max performance ; ASYNC- itself. It would not affect the performace of the primary.
As long as you set the FAL parameters and configure tnsnames properly and ensure proper deletion policy for archivelog cleanup in primary ( so that it's not deleted before shipping if need be), you shouldn't find any problem with primary & standby synching.
Good Luck.
Cheers.

Prereq query for Logical Standby runs for days

Have had an SR open for a month that isn't getting anywhere, thought I'd check here and see if anybody has run into this.
We're looking at setting up a logical standby database, Oracle 11.2.0.3 on AIX running PeopleSoft.
There is a prereq query in the Oracle manual which is also run via the GC wizard to find tables without unique logical identifiers.
SELECT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_NOT_UNIQUE
WHERE (OWNER, TABLE_NAME) NOT IN
(SELECT DISTINCT OWNER, TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED)
AND BAD_COLUMN = 'Y';
My problem is that the darned thing runs for 5.5 days.
The view in that query runs the function logstdby$tabf, which runs the following SQL over and over and over and over:
SELECT * FROM LOGSTDBY_UNSUPPORT_TAB_11_2B
Each time it runs the LOGSTDBY_UNSUPPORT_TAB_11_2B query is about 8 seconds. Run it 100,000 times and that adds up. Looks like the big problem in that query is full table scans of TAB$ and COL$.
Anybody seen it? Anybody fixed it?

Good suggestion - in 15 minutes you got farther than support did in 2 weeks.
Rather than remove the sub-query, I can change it into a minus, which is functionally equivalent to the original but changes the executions on DBA_LOGSTDBY_UNSUPPORTED from many times to just once.
select owner, table_name from dba_logstdby_not_unique
where bad_column = 'Y'
minus
select distinct owner, table_name from dba_logstdby_unsupported;
The top part of the query still takes 9.5 hours to run though, with the time now being spent the following SQL which is called from the function logstdby$tabf which is called from the view DBA_LOGSTDBY_NOT_UNIQUE :
SELECT * FROM LOGSTDBY_SUPPORT_TAB_11_2B
Sorry for not putting that in the original post, but I want the original query to run if possible so the GC wizard will work - and I didn't want to clutter up the question.

Real time apply for logical standby

Hi
Oracle 11.2.0.3.0
I have a primary database orcl and logical standby database orcl_std.
Real time apply is enabled. I have standby redologs in both primary and standby sides and I`ve started recovery with below command:
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
When I create a new table in primary database, I am unable to see it on standby database (Although real time apply is enabled)
However, when I switch log in primary, I can see the new table in standby database.
My question is, why realtime apply is not working in my scenerio ? I was expecting to see the new table immediately in standby database once it is created in primary database. Why am I supposed to wait for log switch in real time apply ?

Using Real-Time Apply to Apply Redo Data Immediately
http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_apply.htm#i1022881
1.What is compatible parameter, it should be 11.1
2.Try to check parameters mentioned in below link:
http://easyoradba.com/2011/01/10/real-time-apply-in-oracle-data-guard-10g/
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 15, 2012 12:37 PM

Query for logical standby

Hi ,
We have one logical standby database is running for our production database .
Now business require one more logical standby for reporting purpose
so during step for creating new logical standby we need to run
EXECUTE DBMS_LOGSTDBY.BUILD;
so is this will impact exsiting logical standby ? or we don't run this time this statemnet ?
Thanks
Gaurav

user12219815 wrote:
Hi ,
We have one logical standby database is running for our production database .
Now business require one more logical standby for reporting purpose
so during step for creating new logical standby we need to run
EXECUTE DBMS_LOGSTDBY.BUILD;
so is this will impact exsiting logical standby ? or we don't run this time this statemnet ?
Thanks
Gauravno need to execute.

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,

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

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

Physical standby, logical standby which one shud i prefer?

Hi ,
how to decide which standby to create that is whether Physical or Logical.
I want to create it for database failover. so which one i shoul prefer?
pls give ur suggestions.
Thanks,
Kuamr.
Message was edited by:
user548258

Physical standby is the easiest to setup and administer and supports all datatypes. You can use it for reporting (if it's rarely req'd), except for you would have to cancel the recovery, open the db is a read-only mode, and then put it back in the recovery mode.
Logical standby is a pain, but you can run reports at anytime without canceling recovery. logical does not support certain datatypes, like IOT's, BLOBs, etc.

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

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.

Creating logical standby from non primary backup

We want to test creation for logical standby in our test enviroment.
Here is the plan we are
1. Backup Prod.
2. Restore Test Primary (T1) and Restore test standby (T2) from Prod backup.
3. Setup standby between T1 and T2.
Plan is to save the time for backup and restore process. I have not doe it before. Will this process work or T2 restore needs to be done from backup of T1 as that would be primary.
Manuj

969257 wrote:
Thanks Tobi.
I will try this. The test system is very large about 16TB and the backup/restore process takes days. I just wanted to be sure if the same backup would work for creating the primary and standby at the same time.
So in this case, I will just have to restore from backup and move forward with archivelogs. Will I have to use the control-file from Prod or from T1.
Use the control file from T1(test primary)
I would like to use the backup COPY.
General steps to follow:
1. restore T1 as the (test)primary DB.
2. recover/apply the T1 using the redo log.
3. restore T2 but do not apply redo to prevent it from divergence from T1. i mean, let T2 scn be behind T1 scn.
4. following the general steps as it apply to you in preparing and creating primary and standby DB
http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm
5. make sure T2 can receive and apply redo data from T1
6.covert T2 to logical standby DB
http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ls.htm
HTH
Tobi

Logical standby real time apply problem

Hi all,
The real time apply for logical standby on my Oracle 10.2 DB is not working
SELECT SEQUENCE#, FIRST_TIME, APPLIED
FROM DBA_LOGSTDBY_LOG
ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TI APPLIED
2113 07/10/09 NO
2115 07/10/09 NO
2116 07/10/09 NO
There is no error inside alert log.
Any help
Thanks

Using Real-Time Apply to Apply Redo Data Immediately
http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_apply.htm#i1022881
1.What is compatible parameter, it should be 11.1
2.Try to check parameters mentioned in below link:
http://easyoradba.com/2011/01/10/real-time-apply-in-oracle-data-guard-10g/
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 15, 2012 12:37 PM

Determining Gaps in Logical Standby

DB version: 11.2
For determining the gaps for Physical Standby DB, I use the queries mentioned in the post below
StandbyDB is not in sync with primary
For checking if a Logical Standby and Primary is in Sync, Can I use the same query ? Do I have to consider any other factors for Logical standby when checking for gaps ?

Hello;
Which part of that huge post! I'm thinking No, because that is not a Logical Standby.
On a logical standby database, query the DBA_LOGSTDBY_LOG view on the logical standby database :
COLUMN FILE_NAME FORMAT a55
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#;The Data Guard Concepts and Administration Oracle document should have a "Redo Transport Services" section on this.
Another one, also run on the logical standby :
SELECT
SUBSTR(FILE_NAME,1,100) FILE_NAME, SUBSTR(SEQUENCE#,1,10) "SEQ#",
FIRST_CHANGE#, NEXT_CHANGE#, TO_CHAR(TIMESTAMP, 'HH:MI:SS') TIMESTAMP,
DICT_BEGIN BEG, DICT_END END, SUBSTR(THREAD#,1,4) "THR#"
FROM
DBA_LOGSTDBY_LOG
ORDER BY
SEQUENCE#;
Best Regards
mseberg

Open Mode for Logical Standby

Similar Messages

Maybe you are looking for