ORA-01579 in MRP After shrinking (i.e. resizing) a data file successfully, I was worry about the applying state of the standby database. Not surprisingly, I found ORA-01579: write error occurred during recovery in Managed Recovery Process (MRP) log. oracle@boston>tail -f orcl_mrp0_23309410.trc … *** 2019-03-15 08:51:13.521 Media Recovery Log /oradata/ORCL/ARCH/ORCL_1_342376.arc *** 2019-03-15 09:02:01.230 Media Recovery Log […]
ORA-00600 [3020] Found MRP shutdown with ORA-00600 [3020] in alert log of a standby database due to inconsistency of a newly created data file. Wed Nov 21 18:32:12 2018 Errors in file /oracle/admin/ORCL/bdump/orcl_mrp0_4589393.trc: ORA-00600: internal error code, arguments: [3020], [1786773511], [1], [37836], [320123], [72], [], [] ORA-10567: Redo is inconsistent with data block (file# 854, […]
At times, you may need to enable configuration or enable database to make the broker work again.$ dgmgrl /…DGMGRL> enable configuration;If you were waiting for it to complete for a long time and no return, please check the disk space on both sides (primary and standby servers) by df -h on Linux or df -g on […]
Since ALTER SYSTEM ARCHIVE LOG CURRENT is a synchronized fashion of switching redo logs, it has to synchronize the archive log completely to all archive log destinations including standby databases before returning the prompt to you. It could seem dead, but actually, the background process is transporting the archived log to standbys.If any one of the […]
I tried to connect both primary and standby database by RMAN. But it failed with ORA-01017 error.[oracle@primary01 ~]$ rman target sys@primdb auxiliary sys@standbRecovery Manager: Release 11.2.0.4.0 – Production onCopyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.target database Password:RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-00554: initialization of internal recovery manager package […]
When I queried the archive gap on the standby database which is a 9i in the morning, I got this error:SQL> select * from v$archive_gap;select * from v$archive_gap*ERROR at line 1:ORA-01220: file based sort illegal before database is openSQL> show parameter workarea_size_policy;NAME TYPE […]
As a DBA, you might see many gaps on the standby database in your career like this.SQL> select * from v$archive_gap; THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#———- ————- ————– 1 113187 113187Just don’t rush to take some actions on archived logs, we can check the arrival of the […]
Normally and generally, recovery catalog recognizes the databases by DBID which is a unique number among different databases. But there’s a problem: the primary database and its standby databases share the same DBID, this could make the standby database sync its meta data back to the recovery catalog. This is the source of our problem.When […]
Starting data guard services is actually a reverse process of stopping data guard services by any ways. Let’s see how we start the services along the same route of stopping.With the brokerEnable apply service of the standby database.DGMGRL> EDIT DATABASE ‘standby_db’ SET STATE=’APPLY-ON’;Succeeded.Enable transport service of the primary database.DGMGRL> EDIT DATABASE ‘primary_db’ SET STATE=’TRANSPORT-ON’;Succeeded.Without the brokerStart […]
Stop Data Guard Is Broker Enabled? First of all, you need to know whether the data guard broker is configured, started and controls over the data guard. SQL> show parameter dg_broker_start NAME TYPE VALUE ———————————— ———– […]
