ORA-16766 Error in Oracle Data Guard: Causes and Fix (19c Guide)

ORA-16766 Error in Oracle Data Guard: Causes and Fix (Oracle 19c Guide)

Redo Apply Service Not Running, How to Diagnose and Restart MRP in Under 5 Minutes

📅 4 May 2026

👤 Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 10-12 min read

⏱️ Estimated Reading Time: 10-12 minutes

ORA-16766, MRP Not Running, DGMGRL Diagnosis, MRP Restart, Standby Apply Fix, Oracle 19c

ORA-16766

Full Error: ORA-16766: Redo Apply is stopped

This error appears in DGMGRL SHOW CONFIGURATION output against the standby database. It means the Managed Recovery Process (MRP) on the standby has stopped and redo is no longer being applied. The standby is diverging from the primary with every passing second.

It was 3:22 AM. The monitoring alert fired: "Data Guard configuration warning — ORA-16766 on standby." Apply lag had jumped from zero to 47 minutes in under an hour. The standby database was alive, connected, receiving redo, but not applying any of it.

ORA-16766 is one of the most common Oracle Data Guard errors in production Oracle 19c environments. It always means the same thing: the MRP process on the standby has stopped. But the reasons it stops, and the correct fix for each reason, are completely different.

This guide covers every root cause of ORA-16766 in Oracle 19c, the exact DGMGRL and SQL commands to diagnose it, and the step-by-step fix commands for each scenario. Most ORA-16766 errors are resolved in under 5 minutes once you know which cause you are dealing with.

Why You're Not Getting Interview Calls: Blind Applications vs Targeted Strategy

Why You're Not Getting Interview Calls in 2026: Blind Applications vs Targeted Strategy

100 Applications. 0 Responses. Here Is Exactly Why, and How to Fix It.

📅30 April 2026

👤 Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 12 - 14 min read

⏱️ Estimated Reading Time: 12,14 minutes

Blind Applications, ATS Failures, No Referral Strategy, Quality vs Quantity, Targeted Job Search 2026

🎯 Who This Guide Is For

Final year students sending applications and hearing nothing back. Freshers who have applied to 80,200 jobs over several months with 0,2 responses. Anyone who has been told "just keep applying" without being told why their applications are failing and what to do differently.

If you are not getting interview calls despite sending dozens of applications, the problem is almost never your skills or your degree. Freshers not getting interview calls in 2026 is an epidemic, and the root cause is almost always the same: blind, untargeted applications that fail before any human ever reads them.

A student messaged me last month: "I have applied to 140 jobs in the last 3 months. I have received 2 responses and both were rejections. I have a decent GPA, a relevant degree, and I have been doing everything right. What am I missing?"

The answer was not what she expected. She was not missing skills. She was not missing certifications. She was applying to jobs the wrong way. Every application was a copy-paste of the same generic resume. No keyword matching. No company research. No follow-up. No referral outreach.

She was doing everything she had been told to do, and none of it was working because the advice she had been given was wrong. This guide explains the real reasons, and the exact targeted job search strategy that actually produces interview calls.

How to Fix Data Guard Lag in Oracle 19c (6 Real Production Fixes with SQL)

How to Fix Data Guard Lag in Oracle 19c: Step-by-Step Troubleshooting Guide

5 Proven Fixes for Transport Lag and Apply Lag with Exact SQL Commands

📅 27 April 2026

👤 Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 12-14 min read

⏱️ Estimated Reading Time: 12-14 minutes

Missing SRLs, Parallel Apply, Network Compression, RMAN Conflict, Protection Mode Mismatch

⚙️ Environment Referenced

Oracle Database: 19.18.0.0.0 Enterprise Edition  •  Standby Type: Physical Standby (Active Data Guard)  •  Protection Mode: Maximum Availability (SYNC/AFFIRM)
Primary: 2-Node RAC, 4.8 TB OLTP  •  Network: Dedicated 1 GbE WAN, RTT 1.8 ms  •  Peak Load: 2,800 TPS

In Oracle 19c environments, Data Guard lag is one of the most common production issues DBAs face. It is also one of the most stressful alerts a DBA receives. The standby is falling behind the primary. Every second of lag is a second of potential data loss if the primary fails right now. The pressure to fix it quickly is real.

The problem is that "Data Guard lag" is not one problem. It is five different problems that all show the same symptom. Applying the wrong fix wastes time and can make things worse. This guide gives you the exact decision path, the exact diagnostic queries, and the exact fix commands for each root cause, in the order you should check them.

Follow the steps in order. Each step either identifies your problem and gives you the fix, or clears that cause and moves you to the next. Most Data Guard lag issues are resolved within Steps 1 to 3.

How to Fix Data Guard Lag in Oracle 19c: Step-by-Step Troubleshooting Guide

5 Proven Fixes for Transport Lag and Apply Lag with Exact SQL Commands

 March 2026

 Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 12 - 14 min read

⏱️ Estimated Reading Time: 12 - 14 minutes

Missing SRLs, Parallel Apply, Network Compression, RMAN Conflict, Protection Mode Mismatch

⚙️ Environment Referenced

Oracle Database: 19.18.0.0.0 Enterprise Edition  •  Standby Type: Physical Standby (Active Data Guard)  •  Protection Mode: Maximum Availability (SYNC/AFFIRM)
Primary: 2-Node RAC, 4.8 TB OLTP  •  Network: Dedicated 1 GbE WAN, RTT 1.8 ms  •  Peak Load: 2,800 TPS

Data Guard lag is one of the most stressful production alerts a DBA receives. The standby is falling behind the primary. Every second of lag is a second of potential data loss if the primary fails right now. The pressure to fix it quickly is real.

The problem is that "Data Guard lag" is not one problem. It is five different problems that all show the same symptom. Applying the wrong fix wastes time and can make things worse. This guide gives you the exact decision path, the exact diagnostic queries, and the exact fix commands for each root cause, in the order you should check them.

Follow the steps in order. Each step either identifies your problem and gives you the fix, or clears that cause and moves you to the next. Most Data Guard lag issues are resolved within Steps 1 to 3.

 Table of Contents

1. Before You Start: Run These 4 Queries First
2. Step 1: Check for Transport Lag vs Apply Lag
3. Step 2: Fix Missing Standby Redo Logs (Most Common Root Cause)
4. Step 3: Enable Parallel Apply to Fix MRP Bottleneck
5. Step 4: Fix Network Latency and Bandwidth
6. Step 5: Resolve RMAN vs MRP I/O Conflict
7. Step 6: Fix Protection Mode Mismatch
8. Fix for Active Data Guard (ADG) Apply Lag
9. After the Fix: Verify and Monitor
10. Prevent Lag From Returning: Configuration Checklist
11. FAQ
12. Related Reading

How to Build a Powerful LinkedIn Profile That Attracts Recruiters in 2026

Weak Profiles Get Ignored. Here Is the Exact Framework to Get Found.

9 April 2026

Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 12 - 13 min read

⏱️ Estimated Reading Time: 12 - 13 minutes

All-Star Status, Headline Formula, About Section, Experience Bullets, Skills Strategy, Content Plan

 Who This Guide Is For

Final year students building their LinkedIn for the first time, freshers who have a profile but get zero recruiter messages, working professionals who set up LinkedIn years ago and never touched it since, and anyone who has been told "just be on LinkedIn" without being told what that actually means.

I know freshers who applied to 80 jobs on Naukri and got 2 interviews. I know other freshers who optimised their LinkedIn profile over one weekend and received 6 recruiter messages within 3 weeks without applying to a single job. The difference was not their skills, their college, or their GPA. The difference was visibility.

LinkedIn is not a digital version of your resume. It is a search engine for talent. Recruiters run Boolean searches with specific keywords, filter by location, experience level, and skills, and contact candidates who match. If your profile does not contain the right words in the right places, you are invisible, no matter how qualified you are.

This guide covers the exact framework to build a LinkedIn profile that attracts recruiters in 2026: every section, every formula, every mistake to avoid, and a content strategy to keep your visibility growing week after week.

Why Data Guard Lag Happens in Production: Sync, I/O and Network Deep Dive

6 Root Causes of Transport and Apply Lag, With Diagnostic SQL to Prove Each One

06 March 2026

Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 14 - 16 min read

⏱️ Estimated Reading Time: 14 - 16 minutes

Transport Lag, Apply Lag, SYNC vs ASYNC, Network RTT, Standby I/O, MRP Apply Bottleneck

⚙️ Production Environment Referenced

Oracle Database: 19.18.0.0.0 Enterprise Edition  •  Primary: 2-Node RAC, 4.8 TB OLTP  •  Standby: Physical Standby (Active Data Guard)
Protection Mode: Maximum Availability (SYNC/AFFIRM)  •  Network: Dedicated 1 GbE WAN, 120 km, RTT 1.8 ms
Peak Load: 2,800 TPS, 180 MB/sec redo generation  •  Application: Core banking transaction processing

The monitoring alert fires at 11:43 PM: "Data Guard apply lag exceeds 900 seconds." Transport lag is 180 seconds. Apply lag is 900 seconds. The standby is 15 minutes behind the primary. If the primary fails right now, 15 minutes of financial transactions are at risk.

This scenario happens in production Data Guard environments more often than most teams admit. The problem looks the same from the outside every time, but the root cause is completely different each time. Transport lag and apply lag each have different causes, different diagnostic queries, and different fixes. Treating them as the same problem wastes hours of investigation.

This guide covers all six real production causes of Data Guard lag, the exact SQL to identify each one, and the specific fix for each. No guesswork. Precise diagnosis first, then precise resolution.

How to Create a Resume That Actually Gets Shortlisted in 2026

Generic Resumes Get Rejected Instantly. Here Is What Actually Works.

02 March 2026

Chetan Yadav, Senior Oracle & Cloud DBA

⏱️ 14 - 16 min read

⏱️ Estimated Reading Time: 14,16 minutes

ATS Optimisation, Impact Writing, Section Structure, Common Mistakes, Before-Submit Checklist

 Who This Guide Is For

Final year students writing their first resume, freshers who have applied to 50 jobs and heard nothing back, mid-level professionals switching roles or industries, and anyone who has been told their resume is "fine" but it keeps getting rejected. This guide covers the real mechanics of how resumes are screened in 2026 and what you must do differently.

I have reviewed hundreds of resumes over 15 years of hiring, mentoring, and career coaching within the technology industry. The same mistakes appear in almost every rejected resume. Not spelling errors. Not bad formatting. The real problem is almost always this: the resume describes what the person did instead of proving what the person achieved.

A resume is not a job description of your past roles. It is a marketing document with one purpose: to get you into the interview room. Every word, every bullet point, every section must serve that purpose. When a recruiter spends 8 seconds on your resume, you have 8 seconds to make them believe you can solve their problem. Generic resumes fail this test instantly.

This guide will show you the exact structure, the ATS rules, the impact writing formula, the before-submit checklist, and the specific mistakes that are costing you interviews right now.

Why Data Guard Lag Happens in Production: Sync, I/O and Network Deep Dive

Six Root Causes of Transport and Apply Lag , With Diagnostic SQL to Prove Each One

30 March 2026

Chetan Yadav , Senior Oracle & Cloud DBA

⏱️ 14–16 min read

⏱️ Estimated Reading Time: 14–16 minutes

Transport Lag • Apply Lag • SYNC vs ASYNC • Network RTT • Standby I/O • MRP Apply Bottleneck

⚙️ Production Environment Referenced in This Article

Oracle Database: 19.18.0.0.0 Enterprise Edition  •  Primary: 2-Node RAC, 4.8 TB OLTP  •  Standby: Physical Standby (Active Data Guard)
Protection Mode: Maximum Availability (SYNC/AFFIRM)  •  Network: Dedicated 1 GbE WAN (120 km distance, RTT 1.8 ms)
Peak Load: 2,800 TPS, 180 MB/sec redo generation  •  Application: Core banking transaction processing

The alert arrives at 11:43 PM: "Data Guard apply lag exceeds 900 seconds." The DBA on call opens the monitoring dashboard. Transport lag is 180 seconds. Apply lag is 900 seconds. The standby is 15 minutes behind the primary. If the primary fails right now, 15 minutes of financial transactions could be at risk.

This scenario plays out in production Data Guard environments more often than most teams admit. Lag is not a single problem , it is six different problems that look identical from the outside. Transport lag and apply lag each have completely different root causes, different diagnostic queries, and completely different fixes. Treating them the same wastes hours of investigation time.

This guide covers every real cause of Data Guard lag I have diagnosed in production, the exact SQL to prove which one you are dealing with, and the specific fix for each. No guesswork. No generic advice about "check your network." Precise diagnosis first, then precise resolution.