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

Similar Messages

Unable to open the physical standby in read only (10g)

Hi,
I m trying to create physical standby using RMAN to another server . But at the last step when trying to test Real Time Apply i m unable to open the standby in read only mode.Can Anyone please let me know whats the issue and how to resolve it
SQL> select status from v$instance;
STATUS
MOUNTED
SQL> alter database recover managed standby database using current logfile disconnect from session;
Database altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1:
'/u01/app/oracle/product/10.2.0/oradata/test1/system.dbf'

Hi,
This is a newly created standby. I created just now. Below the o/p requested
In Primary
SQL> set line 200
SQL> set pagesize 200
SQL> col message format a90
SQL> select severity, error_code, to_char(timestamp,'DD-MON-YYYY HH24:MI:SS'), message from v$dataguard_status where dest_id=2;
SEVERITY      ERROR_CODE TO_CHAR(TIMESTAMP,'D MESSAGE
Error              12541 04-MAR-2012 11:55:05 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error              12541 04-MAR-2012 12:00:12 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 12541.
Error               1034 04-MAR-2012 12:06:25 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning             3113 04-MAR-2012 13:21:24 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning             3113 04-MAR-2012 13:21:24 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error               3113 04-MAR-2012 13:21:24 PING[ARC1]: Error 3113 when pinging standby test1.
Warning             3113 04-MAR-2012 13:33:29 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning             3113 04-MAR-2012 13:33:29 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error               3113 04-MAR-2012 13:33:29 PING[ARC1]: Error 3113 when pinging standby test1.
Error               1034 04-MAR-2012 13:39:50 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Error               1034 04-MAR-2012 13:45:29 PING[ARC1]: Heartbeat failed to connect to standby 'test1'. Error is 1034.
Warning             3113 04-MAR-2012 13:57:56 ARC1: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3113)
Warning             3113 04-MAR-2012 13:57:56 ARC1: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error               3113 04-MAR-2012 13:57:56 PING[ARC1]: Error 3113 when pinging standby test1.
14 rows selected.
SQL> select     ds.dest_id id
,       ad.status
,       ds.database_mode db_mode
,       ad.archiver type
,       ds.recovery_mode
,       ds.protection_mode
,       ds.standby_logfile_count "SRLs"
,       ds.standby_logfile_active active
,       ds.archived_seq#
from    v$archive_dest_status   ds
,       v$archive_dest          ad
where   ds.dest_id = ad.dest_id
and     ad.status != 'INACTIVE'
order by
        ds.dest_id
/   2    3    4    5    6    7    8    9   10   11   12   13   14   15   16
        ID STATUS    DB_MODE         TYPE       RECOVERY_MODE           PROTECTION_MODE            SRLs     ACTIVE ARCHIVED_SEQ#
         1 VALID     OPEN            ARCH       IDLE                    MAXIMUM PERFORMANCE           0          0            64
         2 VALID     UNKNOWN         ARCH       UNKNOWN                 MAXIMUM PERFORMANCE           3          0            64In standby
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
   THREAD# MAX(SEQUENCE#)
         1             64
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
   THREAD# MAX(SEQUENCE#)
         1             64
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC0: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 63
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
MESSAGE
RFS[1]: Assigned to RFS process 9880
RFS[1]: Identified database type as 'physical standby'
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_63_776981781.arc
Media Recovery Log /u01/app/oracle/product/10.2.0/archive/test1/1_64_776981781.arc
Media Recovery Waiting for thread 1 sequence 65
16 rows selected.

Error raised when opening physical standby in read only

Hi,
I've a physical standby 11.2.0.2 created using RMAN duplicate from active database which is configured with data guard. When I open the database in READ ONLY mode
SQL> alter database open read only;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY
I get this error in the alert log
Physical standby database opened for read only access.
Fri Aug 12 15:14:01 2011
db_recovery_file_dest_size of 256000 MB is 4.72% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Errors in file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/ora intsb_ora_8692.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
Completed: alter database open read only
the tracefile is showing this,
Trace file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/oraintsb_ora_8692.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/oracle/product/11.2.0/ORAINT
System name: Linux
Node name: c4p-db01
Release: 2.6.18-194.0.0.0.3.el5xen
Version: #1 SMP Mon Mar 29 18:27:00 EDT 2010
Machine: x86_64
VM name: Xen Version: 3.4 (PVM)
Instance name: oraintsb
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 8692, image: oracle@c4p-db01 (TNS V1-V3)
*** 2011-08-12 15:14:03.367
*** SESSION ID:(24.1) 2011-08-12 15:14:03.367
*** CLIENT ID:() 2011-08-12 15:14:03.367
*** SERVICE NAME:(SYS$USERS) 2011-08-12 15:14:03.367
*** MODULE NAME:(sqlplus@c4p-db01 (TNS V1-V3)) 2011-08-12 15:14:03.367
*** ACTION NAME:() 2011-08-12 15:14:03.367
Error in executing triggers on database startup
*** 2011-08-12 15:14:03.367
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
----- Error Stack Dump -----
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
if I disable the system triggers using
ALTER SYSTEM SET "_system_trig_enabled"=FALSE scope=both;
The error doesn't appear but when trying to switch to active dataguard the open_mode goes from READ ONLY to MOUNTED rather than READ ONLY WITH APPLY
Any help much appreciated
Edited by: phil74 on 12-Aug-2011 07:22

Have you checked what your guard status is set to?
SQL> SELECT guard_status from v$database;I've had a similar issue before but with a standby, whereby the status was set to ALL. This means all users apart from SYS are unable to make changes on the database.
My resolution was to set the status to standby:
SQL> ALTER DATABASE GUARD STANDBY;You may wish to set the guard status to NONE however.
I took some notes:
http://juniororacledba.wordpress.com/2011/07/17/oracle-logical-standby-dataguard-error However, I do not have a link to any Oracle documentation on the subject to hand. But might give you a head start.

Convert standby to read only

Hi,
Oracle 11gR2 / Unix
I want to convert standby database (2 node rac) currently (which is in mount mode) to open read only mode. Can someone please help me steps to be done?
Thanks

>from which node shall I run command to cancel manage recovery and .make it read only
In DataGuard (or manual Standby) even if the Standby database is RAC, only one node and instance is used to manage recovery. So, you would be having the database instance up and applying managed recovery on only one node. You would stop managed recovery on that node and shutdown and startup (read only) again on that node.
>So Is it safe to keep it in read only mode for longer time?
You'll be building up a backlog of archivelogs. You need to ensure that you have enough disk space (on the primary and standby) for those archivelogs.
Also note that your DR protection will be unavailable while the standby is OPEN READ ONLY. If your primary goes down after 12hours or 24hours, your Standby has data only as of 12hours or 24hours ago. Some sites choose to build 2 standby's, one continuously running recovery and another open READ ONLY as and when required. OR to use Active Dataguard Licence.
Hemant K Chitale

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...

ORA-01403: no data found on LOGICAL STANDBY database

Hi ,
Logical Standby issue :
Oracle 10.2.0.2 enterprise edition .
M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
I m getting countinuously no data foud errror on logical standby database .
I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
exec dbms_logstdby.instantiate_table (.......................................
but when i start apply process on logical standby it again give no data found for new table :
Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
As much as i known abt the error that is :
table1
id
10
20
30
Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
update table1 set id=100 where id=50;
above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
watingggg guyssss/......

Troubleshooting ORA-1403 errors with Flashback Transaction
In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
ORA-1403: No Data Found
Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
The initial error
When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
LOGSTDBY stmt: update "SCOTT"."MASTER"
set
"NAME" = 'john'
where
"PK" = 1 and
"NAME" = 'andrew' and
ROWID = 'AAAAAAAAEAAAAAPAAA'
LOGSTDBY status: ORA-01403: no data found
LOGSTDBY PID 1006, oracle@staco03 (P004)
LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
The Investigation
The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
SQL> select versions_xid
, versions_startscn
, versions_endscn
, versions_operation
, pk
, name
from scott.master
versions between scn minvalue and maxvalue
where pk = 1
order by nvl(versions_startscn,0);
VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
03001900EE070000 3492279 3492290 I 1 andrew
02000D00E4070000 3492290 D 1 andrew
Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
SQL> select operation
, undo_sql
from flashback_transaction_query
where xid = hextoraw('02000D00E4070000');
OPERATION UNDO_SQL
DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
('1','andrew');
BEGIN
Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
SQL> commit;
The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
SQL> alter database start logical standby apply;

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.

Active database link in read-only DB

I am unable to active a db_link on a Standby database. The TNS names and Link settting are replication of production DB. My Standby is READ-ONLY.
Are there any special setting for a READ-ONLY DB link.... I just want to activate it
Then I can create a read-only view on the remote DB. Or are all operations over a LINK (even select) seen as DML/DDL and there is no point in activating link?
Thanks.

10 G oracle database

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.

Database open read only

Does the alert<sid>.log always show a warning message as such when a standby database is put into read only mode?
***Warning - Executing transaction without active Undo Tablespace

Hi,
It's a bug happen to 9i
Bug 3270493:EXCESSIVE QMNX TRACE FILES WHEN PLACING STANDBY IN READ ONLY MODE
This does not reproduce in 10g. It looks like there were some modifications made to kwqitnfy to check whether the database is in read-write mode before starting the QMNC process.
The workaround is to set aq_tm_processes=0 when using the database in read-only mode for the long-term. This can be done with a simple alter system command:
ALTER SYSTEM SET aq_tm_processes=0;
By running the above command, the errors would stop and therefore so would the trace files.
Note: Use spfile is applied in order to ensure aq_tm_processes will be zero after restart.
Mike

Read-only agent synching to a Data Guard physical standby?

Hi all,
we are trying to use TimesTen 11.2.2.4.1 as a read-only memory cache for an Oracle 11.2.3.0.7 schema on Linus RedHat 6.3, while using Oracle Data Guard to replicate the Oracle instance over geographically remote sites. On each site we would like to have two TT instances synchronizing with the local Oracle 11g instance. This works fine against the master DB, but are the TT agents going to be able to synchronize against physical standby instances?
The problem it seems is that the TT agent uses dedicated structures in the Oracle master instance (related to the cache grid), which are going to be replicated into the standby instances. Is the TT agent able to use the read-only, replicated structures to complete synchronization, or is this approach unworkable? What would be your advise as how to achieve this?
Thanks for your help,
Chris

Hi again,
so after testing a little bit it appears that this approach works indeed, at least against a limited number of manual DML operations. What I needed to do on the slave instance to have it working is the following:
1 - Entirely exclude TTADMIN and TIMESTEN schemas from the Data Guard replication:
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'SCHEMA_DDL', schema_name => 'TIMESTEN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TTADMIN', object_name => '%');
execute dbms_logstdby.skip(stmt => 'DML', schema_name => 'TIMESTEN', object_name => '%');
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
2 - Erase both schemas from the local instance:
DROP USER TTADMIN CASCADE;
DROP USER TIMESTEN CASCADE;
CREATE USER TTADMIN etc
3 - Temporarily disable the database guard while creating the local ttCache structures, as the scripts seem to need to set a table-level lock on the source table:
ALTER DATABASE GUARD NONE;
ttIsql> CREATE READONLY CACHE GROUP etc
ALTER DATABASE GUARD STANDBY;
4 - Unset the "Fire_Once_Only" property for the local TTADMIN triggers:
execute dbms_ddl.set_trigger_firing_property(trig_owner=> 'TTADMIN', trig_name=> 'TT_06_70560_T', fire_once => FALSE);
At that point the cache seems to replicate properly in the most simple cases. I will try to test with some substantial load and against DG failovers to see how this behaves.
Regards,
Chris

Remove Standby/Read only mode for a database in sql server 2005

Hi,
I have a problem in sql sever . my database is showing standby/read-only mode. i want to remove that mode.please help me for the issue.

HI
Did you assign any DB read only user?
check the administrator guide in your SAP Business one->Documntation->system setup->Administrator guide...
but removing DB read only user is impossible.....

Standby Database - from READ-ONLY to Managed Recovery

We have a standby database set up for our production environment.
We are able to switch logfile on production and perform the managed recovery and then switch over to READ-ONLY mode. However, when the database is in READ-ONLY mode...I cannot close it if there are active connections.
There are 2 ways I can attempt to close the database...either by "shutdown immediate" or by issuing an "alter system kill session (##,##);"
If I issue the "shutdown immediate", then the RFS process does not transmit any more files...saying the connection to host is not there. Therefore this is not a valid solution.
I can use an alter system kill...to kill all active connections...but it would require to know what other connections are there.
Does anybody know how to best do this...to close the database by forcing all connections to end (except your current one) so you can "alter database close" and switch over to managed recovery?
Please HELP!
Thanks.
-Nicolas

u just shutdown the server and restart in standby mode. it will apply all pending archive autometically.

Error during open standby database in read only mode

hi,
alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/u02/app/oracle/oradata/standby/system01.dbf'
Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
what is the reason of this.
Thanks in advance.

thanks for your reply.
[oracle@standby admin]$ cat listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
LISTENER_STANDBY =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME =/opt/app/oracle/product/11.2.0/db_1)
(PROGRAM = extproc)
tnsfile
[oracle@standby admin]$ cat tnsnames.ora
standby =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.124)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = standby)
ora11g =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.120)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = ora11g)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.120)(PORT = 1521))
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
pfile
[oracle@standby standby]$ cat initstandby.ora
ora11g.__db_cache_size=130023424
ora11g.__java_pool_size=4194304
ora11g.__large_pool_size=4194304
ora11g.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
ora11g.__pga_aggregate_target=146800640
ora11g.__sga_target=276824064
ora11g.__shared_io_pool_size=0
ora11g.__shared_pool_size=121634816
ora11g.__streams_pool_size=8388608
*.audit_file_dest='/u01/app/oracle/admin/ora11g/adump'
*.audit_trail='db'
*.compatible='11.2.0.1.0'
#*.control_files='/u02/app/ora11g/oradata/ora11g/control01.ctl','/u01/app/oracle/flash_recovery_area/ora11g/control02.ctl'
*.db_block_size=8192
*.db_domain=''
*.db_name='ora11g'
*.db_recovery_file_dest='/opt/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=4039114752
*.diagnostic_dest='/opt/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=ora11g)'
*.memory_target=2016M
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.undo_tablespace='UNDOTBS1'
*.audit_file_dest='/opt/app/oracle/admin/standby/adump'
*.audit_trail=none
#*.background_dump_dest='/opt/app/oracle/admin/standby/bdump'
#*.compatible='10.2.0.2.0'
#*.control_files='/opt/app/oracle/oradata/standby/control01.ctl'
#,'/opt/app/oracle/oradata/standby/control02.ctl','/opt/app/oracle/or
*.control_files='/u02/app/oracle/oradata/standby/control_sb01.ctl'
#,'/u02/app/oracle/oradata/standby/control_02.ctl','/u02/app/oracle/oradata/standby/control_03.ctl'
*.core_dump_dest='/u01/app/oracle/diag/rdbms/standby/standby/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
#*.db_name='standby'
#*.dispatchers='(PROTOCOL=TCP) (SERVICE=standby)'
*.job_queue_processes=10
*.log_archive_dest_1='location=/opt/app/oracle/arch'
*.log_archive_config='dg_config=(standby,ora11g)'
*.log_archive_dest_1='LOCATION=/opt/app/oracle/oradata/standby/archivelog'
*.log_archive_dest_2='service=orcl valid_for=(online_logfiles,primary_role) db_unique_name=ora11g'
*.log_archive_format='%t_%s_%r.dbf'
*.standby_file_management=auto
*.db_unique_name =standby
*.fal_server='ora11g'
*.fal_client='standby'
*.service_names='standby'
*.open_cursors=300
*.pga_aggregate_target=525336576
*.processes=1500
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=1576009728
*.undo_management='AUTO'
*.undo_tablespace='undotbs02'
#*.user_dump_dest='/opt/app/oracle/diag/rdbms/standby/standby/trace'
*.standby_file_management ='manual'
*.instance_name =standby
#*.standby_archive_dest=/opt/app/oracle/oradata/standby/archivelog
*.db_file_name_convert=(/u02/app/ora11g/oradata/ora11g,/u02/app/oracle/oradata/standby)
*.log_file_name_convert='/u02/app/ora11g/oradata/ora11g','/u02/app/oracle/oradata/standby'
#*.remote_listener=LISTENER_ora11g

It is possible to apply redo while the standby is open in read only mode ?

Hi,
I am using Oracle 11g R2 (11.2.0.1.0)
Step 1: Two node RAC is Configured.
Step 2: One node Data Guard RAC is configured.( i,e Standby is one node RAC).
Primary:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ WRITE PRIMARY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
Standby:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
Question:
I have not purchased active dataguard license.
In my case In Data Guard RAC it is possible to apply redo while the database is open in read only mode?
Thanks
Solaiman

876149 wrote:
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM AVAILABILITY MAXIMUM AVAILABILITY
"READ ONLY WITH APPLY" in V$DATABASE.OPEN_MODE means Active Data Guard is enabled.
Oracle code cannot check if you have the right license: it is up to you to know which license you have for your database environments.

Logical standby as read only

Similar Messages

Maybe you are looking for