Home » Server Options » Data Guard » Changes in primary are not getting updated on logical standby (HP UX 11.23)
Changes in primary are not getting updated on logical standby [message #359459] Sun, 16 November 2008 12:24 Go to next message
pramod_garre
Messages: 6
Registered: April 2008
Junior Member
Hi gentlemen,

We have configured Logical standby for one of our databases.We have followed all the things mentioned in oracle documentation and all the views related to logical standby are showing accurate results.but if we change some data in primary for instance,inserting some rows in table and switch log files and after it applied on logical standby ,these rows are not appearing in standby tables??what must be the problem???
Re: Changes in primary are not getting updated on logical standby [message #359462 is a reply to message #359459] Sun, 16 November 2008 12:44 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
Did you commit the data on the primary ?

If so, did you verify that the logs were sent and applied on the standby ? Check the alert log and check max(sequence#) from V$LOG_HISTORY on the standby.
Re: Changes in primary are not getting updated on logical standby [message #359467 is a reply to message #359462] Sun, 16 November 2008 12:58 Go to previous messageGo to next message
pramod_garre
Messages: 6
Registered: April 2008
Junior Member
Yes ..I did the follwing

I commited in primary and then i switched the logfile in primary.Alert log at standby and the related views at standby are as follows

Alert log of logical standby

LOGMINER: Begin mining logfile: /oradata_two/Adb/archive_standby/arch1_39_667920052.dbf
Sun Nov 16 23:33:06 2008
LOGMINER: End mining logfile: /oradata_two/Adb/archive_standby/arch1_39_667920052.dbf
Sun Nov 16 23:33:33 2008

And this is log is applied on standby as per it's views


select NAME,THREAD#,SEQUENCE# from dba_logmnr_log;


NAME
--------------------------------------------------------------------------------
THREAD# SEQUENCE#
---------- ----------
/oradata_two/Adb/archive_standby/arch1_33_667920052.dbf
1 33

/oradata_two/Adb/archive_standby/arch1_39_667920052.dbf
1 39


but this query shows the following output

SQL> select max(sequence#) from V$LOG_HISTORY ;

MAX(SEQUENCE#)
--------------
1


i started logical stndby apply process but still why it is not applying event every log is reached standby and evtn though alert log shows that log miner is mining every log .





Re: Changes in primary are not getting updated on logical standby [message #359469 is a reply to message #359467] Sun, 16 November 2008 13:14 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
What is the current state of SQL Apply (V$LOGSTDBY_STATE) ?

Check for any events in DBA_LOGSTDBY_EVENTS and V$LOGSTDBY_PROGRESS for the applied SCN.

Re: Changes in primary are not getting updated on logical standby [message #359470 is a reply to message #359469] Sun, 16 November 2008 13:37 Go to previous messageGo to next message
pramod_garre
Messages: 6
Registered: April 2008
Junior Member

select * from V$LOGSTDBY_STATE;


PRIMARY_DBID SESSION_ID REALTIME_APPLY STATE
------------ ---------- ---------------------------------------- ----------------------------------------
1475211572 1 N IDLE


SQL> select to_char(EVENT_TIME,'DD-MON-YY:HH24:MI:SS'),CURRENT_SCN,COMMIT_SCN,EVENT,STATUS from DBA_LOGSTDBY_EVENTS;

TO_CHAR(EVENT_TIME CURRENT_SCN COMMIT_SCN EVENT
------------------ ----------- ---------- --------------------------------------------------------------------------------
STATUS
----------------------------------------------------------------------------------------------------------------------------------

15-NOV-08:11:43:20
ORA-16111: log mining and apply setting up



2 ;

APPLIED_SCN APPLIED_TIME RESTART_SCN RESTART_TIME LATEST_SCN LATEST_TIME MINING_SCN MINING_TIME
----------- ------------------ ----------- ------------------ ---------- ------------------ ---------- ------------------
240321 16-NOV-08:23:35:22 240305 16-NOV-08:23:34:42 240321 16-NOV-08:23:35:22 240322 16-NOV-08:23:35:22


The above SCN and timings are advancing as and when log shipping done and alert log of standby shows log mining is done




Re: Changes in primary are not getting updated on logical standby [message #359473 is a reply to message #359470] Sun, 16 November 2008 14:13 Go to previous messageGo to next message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
It would appear that the apply is working appropriately. Is the APPLIED_SCN close to the current_scn from the primary (select current_scn from v$database) ?

Have you tried to stop and start the apply process ?
Re: Changes in primary are not getting updated on logical standby [message #359476 is a reply to message #359473] Sun, 16 November 2008 15:05 Go to previous messageGo to next message
pramod_garre
Messages: 6
Registered: April 2008
Junior Member
Yes it is closer...and i tried starting and stopping of Log apply ....As this is configured for first time are there any miscellenious prerequisites to make logical log apply possible??i have done all the prerequisites like supplement logging,force logging etc provided by oracle documentation
Re: Changes in primary are not getting updated on logical standby [message #359479 is a reply to message #359476] Sun, 16 November 2008 18:14 Go to previous message
ebrian
Messages: 2794
Registered: April 2006
Senior Member
In seeing the output you provided, I can't think of anything else to suggest.

You may want to review Understanding Logical Standby Databases to see if there is any information there that may help you with setting up and configuring a logical standby.
Previous Topic: Protection mode
Next Topic: Physical Standby Creation
Goto Forum:
  


Current Time: Wed Dec 07 04:52:29 CST 2016

Total time taken to generate the page: 0.08099 seconds