SolutionPack for Oracle Database 1.4.1 Summary Sheet – Service Assurance Suite 9.4

Table of Contents

Revision history

Use this table to review the revisions made to this document.

Back to Top

Overview

Learn 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.

SolutionPack for Oracle Database

SolutionPack for Oracle Database

Back to Top

Technical specifications

Notes

Main reports

Back to Top

Installing the SolutionPack

Before you begin

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Click SolutionPacks.
  4. Click SolutionPack Center.
  5. Select the SolutionPack in the Browse and Install SolutionPacks window.
  6. Click Install.
  7. Type the instance name.
  8. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  9. Click Next.
    The window displays data collection details.
  10. From the Data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new data collection.
    If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
  11. Leave Activate the FailOver-Filter checked.
  12. If you select Configure collector advance settings, you have the option of selecting from polling periods of 5 minutes, 15 minutes, 30 minutes, and 1 hour. The default polling period is set to 15 minutes. Consult with your database administrator to set the polling period based on the number of Oracle Database instances that are being polled by this particular instance of the collector manager.
  13. Click Next.
    The window displays reports settings.
  14. From the Web-Service Gateway drop-down menu, select existing settings that have been specified for other components, or select Add a new Web-Service Gateway.
    If you select Add a new Web-Service Gateway, type information about the web-service gateway.
  15. In Administration Web-Service Instance, select an existing instance or create a custom instance.
  16. Click Install.
  17. Click Ok when the installation is complete.
  18. Click Discovery Center > Devices Management.
  19. Click Add new device.
  20. Click Oracle Database.
  21. Select the server and collector instance where you want to store the configuration details for this device, and then enter the hostname or IP address of the host, supply the login credentials, and specify the appropriate configuration settings.
    EMC recommends adding a watch4net user beforehand so that the correct credentials are added to Oracle Database Devices Management.
    For each Oracle Database instance being polled, it is useful to have the following information on hand before it is added to the Collection devices list:
    • Oracle service name
    • Oracle instance name (in case of a RAC setup)
    • Username (watch4net user)
    • Password
    • Port
    • Server details (Windows or Linux)
    • Server details (Physical or VM)
    • Oracle setup (ASM or non ASM)
    • Oracle setup (RAC or non RAC)
    • Oracle version
    • RAC version (if installed)
  22. Click Test to validate the credentials.
  23. Click OK.
  24. Click Save.
Back to Top

Configuring the SolutionPack with an unprivileged account

The 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 collector.

Procedure

  1. Create the watch4net user:
    create user watch4net identified by <securepassword> default tablespace users temporary tablespace temp;
  2. Grant the necessary privileges to the watch4net user by running the following grants:
    grant create session 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_segments 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;
    grant select on dba_libraries to watch4net;
    grant select on V_$MEMORY_DYNAMIC_COMPONENTS to watch4net;
    grant select on V_$PGA_TARGET_ADVICE to watch4net;
    grant select on V_$SGA_TARGET_ADVICE to watch4net;
    grant select on V_$MEMORY_TARGET_ADVICE to watch4net;
    grant select on V_$instance_recovery to watch4net;
    grant select on V_$SYSTEM_event to watch4net;
    grant select on V_$PGASTAT to watch4net;
    grant select on V_$LOCK to watch4net;
    grant select on v_$lock_type to watch4net;
    grant select on v_$locked_object to watch4net;
    grant select on dba_objects to watch4net;
    grant select on v_$system_wait_class to watch4net;
    grant select on V_$SYSTEM_event to watch4net;
    grant select on gv_$sysmetric to watch4net;
    grant select on v_$sysmetric to watch4net;
    grant select on V_$version to watch4net;
    

Results

Your dedicated account is configured.

Back to Top

Limitations

The All > Report Library > Oracle Database > Inventory > List all servers report does not work.

Back to Top

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Modules.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top
[an error occurred while processing this directive]