Alert Log In Standby Database is Flooded with Warnings - MRP has not responded for more than 600 seconds.
Last updated on MAY 22, 2018
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.2 [Release 11.2 to 12.1]Information in this document applies to any platform.
Symptoms
The alert log in standby database is flooded with MRP has not responded.
Thu Oct 06 18:50:52 2016
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
Thu Oct 06 22:23:01 2016
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
Thu Oct 06 22:24:46 2016
ORA-1013 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL...
...
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
Thu Oct 06 22:31:19 2016
License high water mark = 49
USER (ospid: 64595): terminating the instance
Instance terminated by USER, pid = 64595
Thu Oct 06 18:50:52 2016
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
Thu Oct 06 22:23:01 2016
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
...
Thu Oct 06 22:24:46 2016
ORA-1013 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL...
...
MRP has not responded for more than 600 seconds. Possible that primary not shipping logs, check log_archive_dest_state params on primary.
Thu Oct 06 22:31:19 2016
License high water mark = 49
USER (ospid: 64595): terminating the instance
Instance terminated by USER, pid = 64595
- MRP hangs when an RMAN backup is run on an Active Data Guard standby database.
- Block change tracking been used on Standby for Rman backups.
- The CTWR trace file is full of msgs 'krcptmo: MR checkpoint requested but not completed'
Changes
None. This database was using 11.2.0.4.160719 PSU
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms