*.remote_listener – Um, ok, we didn’t expect that – REMOTE_LISTENER - part #2
From time to time even us seasoned DBA’s run into a feature, behavior or trick we didn’t know existed. This is really interesting and worthy of sharing in the hopes that someone else can learn something they didn’t previously know.
Like we discussed in Part #1, we’ve replacing a legacy Windows RAC system with a new X8-2M Oracle database appliance (ODA). Fast forward, the implementation was wildly successful (700% higher performance, increased stability, and implementation of DBvisit as this is an Oracle SE implementation), and we’re doing the decommissioning of the legacy Windows RAC system. Part of those steps is the removal of the hosts from Oracle Enterprise Manager (backups, alerting, monitoring, reports, etc.). I’ve found the best way to accomplish this is to navigate to the agent within OEM, navigate to decommission agent and allow the decommission process to remove the associated targets (host, db, etc.). Here’s where it get interesting. Apparently when the ODA’s PROD database registered itself with Windows RAC cluster, Oracle Enterprise Manager also got involved and associated the two systems. So when I decommissioned the Windows RAC server, database, agent, etc. it proceeded to delete all of the targets (and their associated backup jobs & monitoring) from the new ODA. Had we run an OEM discovery process I might have considered this possible, but this was all “auto-magic”. Not the end of the world, but certainly wasn’t what we expected since these were two technically unrelated systems
**Author – Re-Quest-EC
