A Friend wrote: “In the Enterprise Manager Cloud Control 12c console, we can define an RMAN “Catalog” database to be used to store catalog information for RMAN backups. We can define the same catalog database to be used by multiple target databases. “However, there is a problem when the catalog database is switched over or failed over to its standby (role reversal). After this, all scheduled backup jobs in Enterprise Manager for target databases fail because the jobs are not able to reach the parent catalog database. Manual intervention is required, which is difficult. “Is there any way to make catalog database switchover seamless? This is not a problem for manual backups because the TNS entry for connecting to the catalog database can contain the address for both primary and standby catalog, but we don’t have similar option in the cloud control 12c console. There should be an option to provide the complete TNS connect string with client failover construct for the catalog database.” The same friend then wrote: “There is a column called RCVCAT_CONNECT_STR in the table SYSMAN.MGMT_RCVCAT_CONFIG. It contains data like following .. '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST= )(PORT=1521)))(CONNECT_DATA=(SID= )(SERVER=DEDICATED)))', “It may be possible to simply update this column, this would resolve the issue.” He mentioned that his company had updated the connect string after the failover to point to the new RMAN catalog host, and it had worked so far as they could see. However, later on if an “Edit Recovery Catalog” was performed via the Enterprise Manager console, the existing value of this column was overwritten. What he mentioned of course – updating a view directly in the EM repository - was a totally unsupported workaround. The correct course of action is mentioned in the following My Oracle Support (MOS) document: How to Change Recovery Catalog Setting For All Target Databases In EM Grid Control (Doc ID 840051.1) This document explains that the changes to the Recovery Catalog can be performed globally for all databases by selecting Targets..Database and then selecting Recovery Catalog from the menu, and editing the applicable recovery catalog. An easy fix. By the way, the steps in the document are applicable to EM12c even though the document only mentions EM10g and EM11g.
↧