Re: Troubleshooting log shipping

  • From: Mladen Gogala <gogala.mladen@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Sat, 9 Jan 2016 17:32:44 -0500

Hi Upendra,
Did you configure DG broker? DG broker is the best tool for monitoring and troubleshooting DG in existence.
Regards


On 01/08/2016 02:52 AM, Upendra nerilla wrote:

Hello everyone -
Happy new year!

Oracle RAC 11.2.0.3
OEL 5.x

I have an environment in which the primary is shipping logs to a local standby and a remote dataguard database.
What I am seeing is that, somehow not all the archivelogs are being shipped to the remote site. At the time of log apply these logs are being transmitted over.

Here is an example on how the redologs appear in the remote site:
512 1860501 952576512 954204160 thread_1_seq_434986.5778.900455621
512 1883168 964182016 965738496 thread_1_seq_434991.8962.900456295
512 1850346 947377152 948961280 thread_1_seq_434997.9060.900456899
512 1865067 954914304 956301312 thread_1_seq_435003.3202.900457539
512 134582 68905984 70254592 thread_1_seq_435008.1471.900457605
512 1848325 946342400 947912704 thread_1_seq_435009.3990.900458259
512 1863147 953931264 955252736 thread_1_seq_435017.6484.900458793
512 1834310 939166720 940572672 thread_1_seq_435023.8233.900459079
512 1438234 736375808 738197504 thread_1_seq_435024.11250.900460605

Similar gaps for thread_2 as well..

Here is the configuration of the log_archive_dest_3 on primary for the remote site:
*service="SID_DR", LGWR ASYNC NOAFFIRM delay=0 optional compression=disable max_failure=0 max_connections=1 reopen=15
db_unique_name="SID_DR" net_timeout=30, valid_for=(all_logfiles,primary_role)*

I do not see any errors for the redo transport in the alert log on the primary site or on the remote DG site.
Any thoughts on how should I troubleshoot this? Are there any known bugs around this?

Your help is appreciated.

Thanks
-Upendra


--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com

Other related posts: