physical standby purpose itself is to replicate the changes on primary to standby. so when you say you have configured active dataguard, by this time itself what ever you are expecting to work is ready. to check yourself, try to do some changes in primary and see if same values are reflecting on standby or not.
also, i am assuming you opened your standby in read-only mode. if not please do it now, then only you will be able to query from standby.
I have configured oracle 11g active data guard.
my requirement is , as soon as transaction done in primary database , standby database will be updated. So that promptly user from standby database session cat see the changes.
what would be the configuration to full fill the requirement?
Maximum protection This protection mode ensures that no data loss will occur if the primary database fails.
Read-Only Standby and Active Data Guard
Once a standby database is configured, it can be opened in read-only mode to allow query access. This is often used to offload reporting to the standby server, thereby freeing up resources on the primary server. When open in read-only mode, archive log shipping continues, but managed recovery is stopped, so the standby database becomes increasingly out of date until managed recovery is resumed.
To switch the standby database into read-only mode, do the following.
SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE OPEN READ ONLY;
To resume managed recovery, do the following.
SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
In 11g, Oracle introduced the Active Data Guard feature. This allows the standby database to be open in read-only mode, but still apply redo information. This means a standby can be available for querying, yet still be up to date. There are licensing implications for this feature, but the following commands show how active data guard can be enabled.
SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE OPEN READ ONLY; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Since managed recovery continues with active data guard, there is no need to switch back to managed recovery from read-only mode in this case.
Thanks & Regards
Moved to the Data Guard forum - pl post future questions in appropriate forum
you can use real time apply.Redo log will ship to standby and applied as soon as redo log was generated at the primary database.
You can activate real time apply with below command after startup database in mount state.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE
Create Redo Logs if you have not created
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 ('/u01/app/oracle/oradata/PRIM/standby_redo02.log') SIZE 200M;
If you need to cancel the apply process, issue the following command.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Provided you have configured standby redo logs, you can start real-time apply using the following command.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;