Why is the MRP process not running in Oracle Data Guard?

The MRP process stops in Oracle Data Guard for five main reasons: manual cancellation during maintenance, missing Standby Redo Logs preventing real-time apply, Data Guard Broker setting apply state to OFF, protection mode conflict causing MRP abort, or no auto-start after standby instance crash. Each cause has a different fix command.

How do I restart the MRP process in Oracle Data Guard 19c?

Run on the standby: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION; Then verify with: SELECT process, status FROM v$managed_standby WHERE process='MRP0'; If using Data Guard Broker, run in DGMGRL: EDIT DATABASE standby_db SET STATE='APPLY-ON';

What is the difference between MRP not running and ORA-16766?

They describe the same condition from different perspectives. ORA-16766 is the error code Oracle reports in DGMGRL SHOW CONFIGURATION output. MRP not running is the underlying technical reason for that error. Both mean the Managed Recovery Process on the standby has stopped and redo is no longer being applied.

Why does MRP stop immediately after I restart it?

Recurring MRP stop after restart points to three causes: Data Guard Broker has apply set to OFF and overrides your manual restart (fix via DGMGRL), missing Standby Redo Logs cause MRP to fail on start (create SRLs first), or Maximum Protection mode with an unstable standby connection causes repeated abort (lower to Maximum Availability).

How do I prevent MRP from stopping after a standby reboot?

Create an AFTER STARTUP database trigger on the standby that checks the database role and automatically runs ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT. Alternatively, enable Data Guard Broker with dg_broker_start=TRUE and set the database state to APPLY-ON, which makes the broker auto-restart MRP after any restart.

What does ORA-16766 mean in Oracle Data Guard?

ORA-16766 means the Redo Apply Service on the standby database is not running. The MRP (Managed Recovery Process) is stopped, which means the standby is not applying redo from the primary and is falling behind.

How do I fix ORA-16766 in Oracle 19c Data Guard?

Run: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT; on the standby. If using Data Guard Broker, run: DGMGRL> EDIT DATABASE standby_db SET STATE='APPLY-ON'; Then verify with: SELECT process, status FROM v$managed_standby WHERE process='MRP0';

Why does ORA-16766 keep coming back after restart?

Recurring ORA-16766 usually means either Standby Redo Logs are missing (preventing real-time apply), the Data Guard Broker has the database set to APPLY-OFF state, or protection mode is set to Maximum Protection with an unstable standby connection causing repeated MRP abort.

Does ORA-16766 cause data loss?

ORA-16766 itself does not cause data loss immediately. However, while MRP is stopped, the standby is not applying redo. If the primary fails during this window, you will lose all redo generated since MRP stopped. Fix it as soon as it is detected.

How long should a targeted job search take before I get an interview?

With a genuinely targeted approach of 10 to 15 customised applications per week, LinkedIn outreach, and referral requests, most freshers in tech see their first interview within 3 to 6 weeks.

Why am I not getting interview calls despite applying to many jobs?

The most common reasons are: ATS rejecting your resume due to missing keywords or wrong format, applying to roles you are underqualified for, using a generic resume for every application, and having no referral or follow-up strategy.

Is it okay to apply to the same company multiple times?

For different roles, yes, but space them out by at least 2 to 3 weeks. Applying to 5 roles at the same company in the same week flags your application as unserious.

What if I have no connections at any company I want to apply to?

Connect with college alumni who graduated 1 to 3 years before you and are now working in your target domain. Search LinkedIn for your college name plus your target company name to find alumni who can refer you.

How do I ask for a referral without being awkward?

Start with a genuine connection message mentioning something specific about their work. Build the relationship over 1 to 2 weeks of conversation before asking. Always make it easy for them to say no, which actually increases the yes rate.

Monday, May 11, 2026

MRP Process Not Running in Data Guard: Fix in Oracle 19c

MRP Process Not Running in Data Guard: Fix It Step-by-Step (Oracle 19c)

MRP Process Not Running in Data Guard? Fix It Step-by-Step (Oracle 19c)

5 Root Causes, DGMGRL Diagnosis and Exact Fix Commands for Every Scenario

📅 April 2026

👤 Chetan Yadav, Senior Oracle & Cloud DBA, Oracle ACE Apprentice

⏱️ 12,14 min read

⏱️ Estimated Reading Time: 12,14 minutes

MRP Not Running, ORA-16766, DGMGRL Fix, SRL Creation, Broker State, Auto-Start Trigger, Oracle 19c

mrp process not running data guard oracle 19c server infrastructure troubleshooting guide

⚙️ Environment Referenced in This Article

Oracle Database: 19.18.0.0.0 Enterprise Edition • Primary: 2-Node RAC, 4.8 TB OLTP, 2,800 TPS
Standby: Physical Standby with Active Data Guard enabled
Protection Mode: Maximum Availability (SYNC/AFFIRM) • Broker: Data Guard Broker enabled

The monitoring alert arrived at 2:48 AM: "Standby apply lag crossing 90 minutes." I connected to DGMGRL immediately. SHOW CONFIGURATION confirmed it: the MRP process was not running on the standby. Every transaction committed on the primary for the past 90 minutes was sitting unprocessed in Standby Redo Logs, and the gap was growing by the second.

In my 15 years managing Oracle production environments, a stopped MRP process is one of the most common Data Guard incidents I have resolved. It is not complicated once you know which of the five root causes you are dealing with. The problem is that each cause has a completely different fix, and applying the wrong one wastes critical time.

This guide gives you the exact decision path, the diagnostic commands to identify your specific cause, and the precise fix for each scenario. In most cases the MRP process not running in Data Guard is resolved in under 5 minutes.

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 vs Targeted Job Search 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

Fresher job search strategy 2026, why not getting interview calls, targeted applications vs blind applications guide

🎯 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.

Chetan Yadav

Pages