Copyright (c) 2019, Oracle. All rights reserved. Oracle Confidential.

Exadata Capacity Planning BI Publisher Report for Enterprise Manager. (Doc ID 2164067.1)

In this Document

Abstract
History
Details
Summary
Recommendations
Modification History

APPLIES TO:

Enterprise Manager Base Platform - Version 12.1.0.3.0 to 12.1.0.5.0 [Release 12.1]

Enterprise Manager Base Platform - Version 13.1.0.0.0 to 13.2.0.0.0 [Release 13c]
BI Publisher (formerly XML Publisher) - Version 11.1.1.6.x to 11.1.1.7.x [Release 11.1]
Information in this document applies to any platform.

ABSTRACT

Oracle Enterprise Manager collects metrics from the monitored targets and stores them in the OMS repository. When
monitored by Oracle Enterprise Manager, Oracle Exadata Database Machine provides a set of metrics that can be used for
capacity planning analysis, growth forecasting and historical health checking.

Note: Currently this report provides the baseline and historical resource consumption of an Exadata
Database Machine. Predictive analysis and forecasting will be introduced in a future release.

HISTORY

DETAILS

This report is divided into six main sections.

1. Exadata Machine Configuration : This section lists the Exadata machine name and servers.
2. Global Summary : This section is a summary listing the maximum and average values for CPU, and memory and
network throughput for the last 24 hours, 7 days, 31 days and 365 days.
3. Storage Capacity Planning Details : This section shows the historical space usage in the ASM diskgroups (raw and
usable) as well as the the space used by the top 5 serviced databases.
4. CPU and Memory Capacity Planning Details : This section shows the CPU and memory utilization of each database
node in the Exadata Database Machine in the last 24 hours, 7 days, 31 days and 365 days.
5. IO Capacity Planning Details: This section shows several IO metrics for cell disks and Flash: Utilization, Throughput
(MBPS), IOPS, Load and Response Time (ms). These metrics are aggregated across all the storage cells for the last
24 hours, 7 days, 31 days and 365 days.
6. Network Capacity Planning: This section shows the bonded (logical) interface and slave (physical) interface
throughput in the last 24 hours, 7, 31 and 365 days.

Note: The report by default will show data for the last 24 hours and 7 days. If there is not enough data for the longer
time periods, the charts for those periods will not be shown.

Deployment Steps:

The steps below will guide you in deploying the BI Report responsible for producing the Exadata Capacity Planning
information. There are two files attached: The data model (Exadata Capacity Planning.xdmz) and the Report template
(Exadata Capacity Planning.xdoz).
Ensure that BI Publisher is integrated with your Oracle Enterprise Manager installation. To do this, run the following
command against your OMS:

$emctl status oms -bip_only

Once BI publisher is configured and running you will see a similar message to the following:

Oracle Enterprise Manager Cloud Control 12c Release 5

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
BI Publisher Server is Up

You can also run the following command to get the OMS details:

$emctl status oms -details

Once BI publisher is configured and running you will see a similar message to the following at the end of details.

BI Publisher Server is Up
BI Publisher Server named 'BIP' running at local URL: https://<SERVER>:<PORT>/xmlpserver
BI Publisher Server Logs: /u01/app/em/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/
BI Publisher Log :
/u01/app/em/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/bipublisher/bipublisher.log

If BI publisher is not integrated with your Oracle Enterprise Manager, follow the procedure for the EM version:

For Oracle Enterprise Manager 13c:

Configuring BI Publisher with Enterprise Manager

For Oracle Enterprise Manager 12.1.0.4 and 12.1.0.5:

Configuring BI Publisher with Enterprise Manager

For Oracle Enterprise Manager 12.1.0.3:

Integrating BI Publisher with Enterprise Manager

Once BI Publisher is configured, follow the steps below to deploy the report:

Create a Folder and Upload Files to BI Publisher

1. Download the attached files in this note (Exadata_Capacity_Planning.xdmz and

Exadata_Capacity_Planning_Report.xdoz)
2. Connect to your xmlserver as sysman, The URL should look similar to this: https://<SERVER>:
<PORT>/xmlpserver/servlet/catalog
3. Click on "My Folders" (Step 3).
4. Click on the New icon (Step 4).
5. Click on the Folder (Step 5).
6. Give a name to your new folder (ex: Exadata Capacity Planning) (Step 6).
7. Click on the folder you just created (Step 7). "Repeat the steps 8 through 12 to upload both the xdmz and xdoz
files."
8. Click on the upload icon (Step 8).
9. Click on choose file (Step 9).
10. Choose the xdmz file (Step 10).
11. Press Open (Step 11).
12. Press upload (Step 12).
Check the report configuration

1. Click on "My Folders" (Step 1).

2. Click on the folder you created previously (Step 1). You will see both files you already uploaded. (Highlighted in
yellow).
3. Click on edit below the report name (Step 3). This will open a new window and you should see data model
(Highlighted in green).
4. If the data model "Exadata Capacity Planning" does not show, click on the magnifier and choose the data model
from the folder you uploaded it into and click the open button (Step3) which will close this window, then click the
"Save Report" icon on the upper right hand side.
5. Go back to the folder you created and click on Edit below the data model (Step 6). This will open the structure of
the data model, Click on "Data Model" (Step 7).
6. Make sure that the "Default Data Source" is pointing to your OMS (Highlighted in Orange). Click on the drop down
choose the correct Data Source, then click the "Save" icon on the upper right hand side. If you don't have a data
source configured for your OMS please refer to the following : Setting Up Data Sources
Run the Report

1. Click on the report name "Exadata Capacity Planning Report" (Step 1) - This will open the report window.
2. Click on the LOV drop down, choose the Exadata target (Step 2), then click Apply (Step 3).
3. The report displays and you can navigate using hyperlinks (Step 4).

Known Issues:

The steps below are required only if you experience memory issues when generating the report. These
issues are generally identified - but not limited to - the occurrence of similar warning messages (to the
below) in the BIP log files.

===========
[2016-07-20T12:15:12.598-04:00] [BIP] [WARNING] [] [oracle.xdo] [tid: 41] [userId: <anonymous>]
[ecid: 005E1Bcrza45UcI76rU4UE0001yC000Fuu,0:1] [APP: bipublisher#11.1.1] [URI:
/xmlpserver/servlet/xdo] java.lang.OutOfMemoryError: GC overhead limit exceeded[[
==========

The solution is to increase the heap value for the BIP server by executing the following procedure on
each Weblogic server in the configuration.

(If you have a multi-OMS configuration, steps c through e should be executed on each Weblogic server
in the configuration.)

a. Login to the OMS server as the owner of the Oracle Installation.

b. Stop all the Management Services : $ emctl stop oms -all
c. Go to the following location : $MIDDLEWARE_HOME/user_projects/domains/GCdomain/bin/setDomainEnv.sh
d. Create a copy of the existing file: $ cp setDomainEnv.sh setDomainEnv.sh.'date +%y%m%d%H%M%S'
e. Modify the setDomainEnv.sh file by adding the following line at the end : MEM_ARGS="-Xms512m -Xmx8192m
-XX:MaxPermSize=8192m -XX:CompileThreshold=8000 -XX:-UseGCOverheadLimit"
f. Restart all the Management Services: $ emctl start oms

Currently this report does not collect the Exadata RDS network traffic.
 Due to: Bug 22903578 - DISK LATENCY CELL METRIC IS SHOWING A VERY LARGE VALUE THAN NORMAL, the report
might show abnormal spikes (very high value) in the "Average Cell Disk Response Time" chart. This behavior is
corrected in the Exadata Storage Software version 12.1.2.3.2.

SUMMARY

This report is based on the Oracle Exadata Database Machine metrics collected by the Oracle Enterprise Manager Agents
and is stored in the OMS repository. For additional information about Exadata Metrics in Oracle Enterprise Manager please
refer to: Exadata Metrics.

Recommendations
Use caution before changing the collection frequency of the Exadata metrics in EM. Reducing the collection
frequency will result in larger data sets being collected by the OMS and this might affect the overall performance of
the repository. Also, more frequent metric collections will affect Agent performance and this can result in data being
queued to the OMS as well as higher memory utilization by the Agent. As a best practice, keep the metric
collection intervals set to the default value.

As mentioned earlier, this report is intended for capacity planning analysis, growth forecasting and health checking
of an Oracle Exadata Database Machine. It is recommended to schedule the report using BI publisher, which will
enable the user to receive a copy via email or by accessing the historical runs of the job. A suggested frequency is
once a month but this can be modified depending on the requirements. For information on scheduling BI reports,
please refer to : Navigating to the Schedule Report Job Page

The performance of the report will depend on the history kept in the OMS as well as the amount of physical
resources available. In some cases the report execution might timeout. To avoid the timeout please refer to My
Oracle Support noteBI Publisher Consolidated Reference (Doc ID 1546377.1) under the section "How To Change
The Session Timeout In Oracle BI Publisher 11g".

Important BI Publisher Best Practices notes;

Oracle BI Publisher Best Practices: Be a Reporting Super Star

Oracle Business Intelligence Publisher Best Practices

Modification History

07/22/2016 - Creation

Didn't find what you are looking for?