Oracle Scan Requirements

AvailabilityGuard is capable of collecting Oracle configuration data using the following methods:

1. Querying Oracle Enterprise Manager (OEM) - recommended.
   
2. Querying Oracle instances directly.
3. Querying Oracle GoldenGate Monitor - if GoldenGate is used.

Oracle Enterprise Manager (AKA  Grid Control / Cloud Control)

AvailabilityGuard uses read-only JDBC queries to collect additional data from Oracle Enterprise Manager (OEM) repository views.

To scan OEM, you should make the following preparations:

• Obtain OEM Name or IP address.
  
• Obtain OEM Database name.
  
• Obtain an OEM user with a view any target privilege (EM_ALL_VIEWER in OEM 12)
  
• Verify that IP connectivity through JDBC is available between the AvailabilityGuard™ collector server and the OEM.
  

Note: Oracle Exadata machines are scanned using Oracle Enterprise Manager version 12 or higher.

Direct Oracle Instance Scanning

AvailabilityGuard™ collects configuration data from Oracle instances by opening a JDBC connection to each instance and running read-only select queries on certain system (meta data) views.

AvailabilityGuard™ automatically discovers database instances, including virtual IP addresses and non-default ports, subject to scanning the operating system hosting the instance.

To scan an Oracle instance, you should make the following preparations:

• Identify the instance virtual IP (name or address) - if not automatically discovered.
  
• Identify the instance connection port - if not automatically discovered.
  
• Obtain a user account on each instance with the following rights:

CREATE USER rguser IDENTIFIED BY [rguserpassword];

grant create session to rguser;
grant select any dictionary to rguser;
grant select on dba_logstdby_events to rguser;
grant select on dba_logstdby_log to rguser;
grant select on dba_logstdby_not_unique to rguser;
grant select on dba_logstdby_parameters to rguser;
grant select on dba_logstdby_progress to rguser;
grant select on dba_logstdby_skip to rguser;
grant select on dba_logstdby_skip_transaction to rguser;
grant select on dba_logstdby_unsupported to rguser;
grant select on dba_logstdby_history to rguser;
grant select on dba_temp_files to rguser;
grant select on dba_free_space to rguser;
grant select on dba_temp_files to rguser;
grant select on dba_free_space to rguser;
grant select on dba_tablespaces to rguser;
grant select on dba_data_files to rguser;
grant select on dba_libraries to rguser;

• Make sure that IP connectivity through JDBC (default port 1521) is available between the
  AvailabilityGuard™ collector server and each database server. 
  

Oracle GoldenGate Monitor

AvailabilityGuard™ uses read-only JDBC queries to collect additional configuration data from Oracle GoldenGate Monitor repository views. 

To scan Oracle GoldenGate Monitor, you should make the following preparations:

• Obtain Oracle GoldenGate Monitor Name or IP address.
  
• Obtain Oracle GoldenGate Monitor Database name.
  
• Obtain a Oracle GoldenGate Monitor user with read privileges on the GoldenGate Monitor repository views.
  
• Verify that IP connectivity through JDBC is available between the AvailabilityGuard™ collector server and each GoldenGate Monitor.

Additional notes

• An Oracle instance should be scanned directly or through OEM - but not both.
• OEM scan also collects configuration data for Exadata infrastructure.