<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>V$dataguard_stats on Oracle Scripts</title><link>https://www.oraclescripts.com/tags/vdataguard_stats/</link><description>Recent content in V$dataguard_stats on Oracle Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>OracleScripts.com</copyright><lastBuildDate>Sat, 03 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.oraclescripts.com/tags/vdataguard_stats/index.xml" rel="self" type="application/rss+xml"/><item><title>Check Oracle Data Guard Standby Synchronization Status</title><link>https://www.oraclescripts.com/post/check-oracle-data-guard-standby-synchronization-status/</link><pubDate>Sat, 03 Jan 2026 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/check-oracle-data-guard-standby-synchronization-status/</guid><description>
&lt;h2 id="how-to-check-physical-standby-database-synchronization"&gt;How to Check Physical Standby Database Synchronization&lt;/h2&gt;
&lt;p&gt;Physical standby databases in Oracle Data Guard need regular monitoring to ensure they stay synchronized with the primary database. The most effective way to check synchronization status is by comparing the current sequence number on the primary database with the applied sequence number on the standby database.
&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="5317081938"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
&lt;/p&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;These SQL queries help database administrators quickly identify if a physical standby database is lagging behind the primary database. By comparing sequence numbers, you can determine the replication gap and take corrective action if the standby falls too far behind. This monitoring is essential for disaster recovery readiness and maintaining your Recovery Point Objective (RPO).&lt;/p&gt;</description></item><item><title>Removing Standby Database Apply Delay in Oracle Data Guard</title><link>https://www.oraclescripts.com/post/removing-standby-database-apply-delay-oracle-data-guard/</link><pubDate>Fri, 24 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.oraclescripts.com/post/removing-standby-database-apply-delay-oracle-data-guard/</guid><description>
&lt;h2 id="removing-standby-database-apply-delay-in-oracle-data-guard"&gt;Removing Standby Database Apply Delay in Oracle Data Guard&lt;/h2&gt;
&lt;h2 id="purpose"&gt;Purpose&lt;/h2&gt;
&lt;p&gt;This script removes the apply delay from an Oracle Data Guard physical standby database. Apply delays are safety features that create a time lag between when redo data arrives at the standby database and when it is applied, protecting against corrupted or incorrect data from the primary database. These commands cancel any existing recovery process and restart it immediately without delay.
&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:block"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="5317081938"
data-ad-format="auto"
data-full-width-responsive="true"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
&lt;/p&gt;</description></item></channel></rss>