SolutionPack for Oracle Database

Table of Contents

Overview

This article explains how to install and configure the SolutionPack for Oracle Database.

The SolutionPack for Oracle Database monitors the status and performance of an Oracle database. The SolutionPack gives visibility into listeners, tablespaces, versions, connections, commits and rollbacks. You can survey the Oracle core process, such as the SGA, and verify the hit ratio about cache, dictionary cache, latch cache, library cache, sort and sessions.

This article applies to EMC ViPR SRM version 3.5.1.

report screen

SolutionPack for Oracle Database

Back to Top

Technical specifications

SolutionPack version

Compatible ViPR SRM version

Main reports

For details on Oracle database user credentials see the following section:

Back to Top

Installing SolutionPack

Before you begin

Procedure

  1. Log in.
  2. Click Administration.
  3. Click Centralized Management.
  4. Click SolutionPacks.
  5. Select SolutionPack Center.
  6. Select the SolutionPack for Oracle Database in the Browse and Install SolutionPacks screen.
  7. Click Install.
  8. In Data Collection, in the Select the components to install window select the Collector host.
  9. In Reports, select the Frontend host.
  10. Click Next.
  11. In the Data collection window, select a value for Data Collection.
    If you select Add a new data collection, type information about the data collection.
    • Failover-Filter must be enabled, which is the default.
    • In HostName or the IP address to send data to, type the Primary Backend host.
  12. Leave Enable alerting on data collected checked.
  13. Select a value for Alerting on data collection.
    If you select Add a new Alerting on data collection, type information about the alerting configuration.
    • In Alerting Backend the hostname or IP address, select the Primary Backend host.
    • Alerting Backend data port must be set to the port on which alerts will be collected by the Primary Backend Host.
  14. Optionally select the Enable property import for server enrichment checkbox.
  15. In the Backend configuration section, type the host information and credentials for the Primary Backend Host.
  16. Select Configure collector advanced settings to configure polling settings.
  17. Click Next.
  18. In Administration Web-Service Instance in the Reports window, select the Frontend host.
  19. Click Install.
    The SolutionPack installation begins.
  20. Click Ok once installation is complete.
    Performance data will displayed in about an hour.
Back to Top

Configuring the SolutionPack for Oracle Database with an unprivileged account

The ViPR SRM collector must connect to each instance of Oracle databases and perform SQL queries. You can use either an administrator equivalent system account, or create a dedicated system account for the collector. If you want to use the last option, please ask the DBA administrator to run the following query against every instances/RAC cluster. This will create a watch4net account with specific grants for the ViPR SRM collector.

Procedure

  1. Run the query as follows:
    create user watch4net identified by securepassword default tablespace users temporary tablespace temp;
    grant connect to watch4net;
    grant select on V_$SYSSTAT to watch4net;
    grant select on v_$filestat to watch4net;
    grant select on v_$database to watch4net;
    grant select on dba_data_files to watch4net;
    grant select on dba_extents to watch4net;
    grant select on dba_free_space to watch4net;
    grant select on v_$parameter to watch4net;
    grant select on v_$sgainfo to watch4net;
    grant select on v_$rowcache to watch4net;
    grant select on v_$librarycache to watch4net;
    grant select on v_$latch to watch4net;
    grant select on v_$rollstat to watch4net;
    grant select on v_$dispatcher to watch4net;
    grant select on v_$instance to watch4net;
    grant select on v_$sesstat to watch4net;
    grant select on v_$statname to watch4net;
    grant select on v_$session to watch4net;
    grant select on v_$sess_io to watch4net;
    grant select on v_$asm_disk to watch4net;
    grant select on v_$asm_diskgroup to watch4net;
    grant select on v_$logfile to watch4net;
    grant select on v_$log to watch4net;
    grant select on dba_tablespaces to watch4net;
    
  2. For Oracle11, you also need to run:
    Begin
    dbms_network_acl_admin.create_acl(
    acl         => 'Resolve_Access.xml',
    description => 'Resolve Network Access using UTL_INADDR',
    principal   => 'WATCH4NET', -­ MUST BE IN CAPS
    is_grant    => TRUE,
    privilege   => 'resolve',
    start_date  => null,
    end_date    => null
    );
    commit;
    end;
    begin
    dbms_network_acl_admin.assign_acl (
    acl           => 'Resolve_Access.xml',
    host          => '*',
    lower_port    => null,
    upper_port    => null);
    end;
    commit;
    

Results

Your dedicated account is configured.

Back to Top