Grid Infrastructure 18c has been upgraded to 19c GI successfully. So 18c GI_HOME needs to be de-installed. There are two ways to uninstall the old GI_HOME ( 18c ).
Subscribe to get access
Read more of this content when you subscribe today.
Blog
How to Configure OMS to Connect to Repository Database with Standby Database
This post demonstrates how to configure database connection string for OMS to connect to repository database, which has a data guard standby database. The purpose is to make sure OEM is still functioning after database has been switched or failed over to data guard physical standby database.
Subscribe to get access
Read more of this content when you subscribe today.
Restart all OMS
[oracle@oemnode1 ~]$ emctl stop oms -all
[oracle@oemnode1 ~]$ emctl start oms
Switch Over Repository Database to Standby Database
DGMGRL> show configuration; Configuration - dg_oemrep Protection Mode: MaxPerformance Members: oemrep - Primary database stboemrep - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS (status updated 27 seconds ago)
DGMGRL> switchover to stboemrep; Performing switchover NOW, please wait... Operation requires a connection to database "stboemrep" Connecting ... Connected to "STBOEMREP" Connected as SYSDBA. New primary database "stboemrep" is opening... Operation requires start up of instance "OEMREP" on database "oemrep" Starting instance "OEMREP"... Connected to an idle instance. ORACLE instance started. Database mounted. Connected to "OEMREP" Switchover succeeded, new primary is "stboemrep" DGMGRL>
Check and Confirm OEM 13c is Still Working
How to Setup Data Guard Physical Standby in Oracle Database 18c
This post applies to 12c and 19c as well, it introduced two popular ways for creating a standby database: RMAN DUPLICATE and from primary database backup
Introduction
This post demonstrates how to build an Oracle 18c physical standby database managed by data guard. The method should also apply to 12c and 19c as well.
Subscribe to get access
Read more of this content when you subscribe today.
DUPLICATE FROM ACTIVE DATABASE Fails With RMAN-03009 ORA-17628 ORA-19505
While creating a new physical standby database by using RMAN duplicate command, the following errors occur:
RMAN> run {
allocate channel prim1 type disk;
allocate channel prim2 type disk;
allocate auxiliary channel standby1 type disk;
DUPLICATE TARGET DATABASE
FOR STANDBY
FROM ACTIVE DATABASE
...
..
.
RMAN-03009: failure of backup command on prim2 channel
ORA-17628: Oracle error 19505 returned by remote Oracle server
ORA-19505: failed to identify file ""
SOLUTION
- Check and remove the old standby database data files.
- Make sure directories for standby database data files created and accessible.
network unreachable resolving ‘./NS/IN’ or ‘./DNSKEY/IN’
While checking named status on Oracle Linux, the following warnings occur:
# systemctl status named .. . May 17 20:40:59 HOSTNAME named[8468]: network unreachable resolving './NS/IN': 2001:500:1::53#53 May 17 20:40:59 HOSTNAME named[8468]: network unreachable resolving './DNSKEY/IN': 2001:500:2d::d#53 .. .
Subscribe to get access
Read more of this content when you subscribe today.
Make DBA Life Easy 