ORA-01017 in DGMGRL Switchover ORA-01017 means that the credentials you provides are not correct, either the username cannot be recognized by the database instance or the password does not match the user’s. In DGMGRL, ORA-01017 may cause switchover to be interrupted. But luckily, the interruptions are not serious. There’re two error patterns for ORA-01017 in […]
Suppose you have duplicated a 19c physical standby already, it’s time to build the data guard relationship between the primary and standby databases. In this post, we directly enable data guard broker to implement 19c data guard environment. Standby Redo Logs We have to add standby redo logs on both primary and standby database for […]
You don’t have to create an empty database on the standby server for building a standby database. In this post, I will show you how to duplicate a 19c physical standby database from scratch by the following sections. Password File File Management Mode Parameter File Necessary Directories Name Resolution Connect Identifiers Listeners Force Logging RMAN […]
ORA-16571 ORA-16571 means that DGMGRL tried to create or save broker files on the destination you designed, but somehow it failed in DGMGRL command line interface. For example, when we tried to create a configuration for 19c data guard broker, we got ORA-16571 like this. [oracle@primary-19c ~]$ dgmgrl / DGMGRL for Linux: Release 19.0.0.0.0 – […]
Asymmetric Data Guard Usually we build data guard environments with the symmetric architecture design on primary and standby servers, that is, single-instance to single-instance or RAC to RAC. Practically, we could have downgraded standby servers in hardware specifications. For example, we may use 16 cores per instance on the primary side but use 8 cores […]
We’re going to introduce 3 ways that can failover to a standby database at connect-time in this post. Using a Persistent Service Name Using a Dynamic Service Name Using a SRVCTL Configured Service Using a Persistent Service Name Connect-Time Failover is a feature of local naming method, and can be easily set up by adding […]
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 […]
