follow "27 Setting Up High Availability " in Oracle® Enterprise Manager Cloud Control Administrator's Guide
12c Release 2 (12.1.0.2)
"To allow Enterprise Manager to monitor a Physical Standby database
(which is typically in a mounted state), specify sysdba monitoring
privileges. This can be specified either during the Standby creation
wizard itself or post creation by modifying the Monitoring Configuration
for the standby database target."In my case, DG is primary database , and DGS is the standby database.
as suggested, I provided sys password here. sysdba(sys) or sysoper account is preferred credential for monitoring metric / reconfigure database, as Mounted / standby database can't be monitored by normal user. I think in production, some IT security may require change sys password regularly .
- Verify the Physical Standby
Verify the Physical Standby database through the Enterprise Manager Console. Click the Log Switch button on the Data Guard page to switch log and verify that it is received and applied to the standby database.
Initializing
Connected to instance orarac1poc:DG
Starting alert log monitor...
Updating Data Guard link on database homepage...
WARNING: Broker name (dg) and target name (DG.POC) do not match.
WARNING: The broker name will be renamed to match the target name.
WARNING: Broker name (dgs) and target name (DGS.POC) do not match.
WARNING: The broker name will be renamed to match the target name.
Skipping verification of fast-start failover static services check.
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
dg: ASYNC
dgs: ASYNC
Checking standby redo log files.....not checked due to broker name mismatch. Run verify again.
Checking Data Guard status
dg : Normal
dgs : Normal
Checking inconsistent properties
Checking agent status
WARNING: No credentials available for target. orarac1poc
Attempting agent ping ... Down
WARNING: No credentials available for target. orarac2poc
Attempting agent ping ... Down
Processing completed.
