Thursday Feb 16, 2012

Managing Oracle Database 11g—Questions and Answers from the Oracle Enterprise Management Online Forum

We received tons of questions from our recent Oracle Enterprise Manager 12c Online Forum, we wanted to continue to provide answers to the most popular ones. In this installment, we'll cover questions from the DBA and developer track.

Q. What kind of testing do you recommend for upgrading from Oracle Database 11gR1 to 11gR2?
A. Oracle Real Application Testing using Database Replay and SQL Performance Analyzer's capabilities are recommended for any Oracle Database upgrade. Check out these resources for more details: Oracle Real Application Testing datasheet and OTN for details on upgrading your database.

Q. Can I manage Oracle Exadata and traditional Oracle Databases from the same console?
A. Yes, you can manage Oracle Exadata and single instance and/or RAC databases from the same Oracle Enterprise Manager Cloud Control console, as well as WebLogic and many other targets. Check out this demo to see how.

Q. I thought Active Session History (ASH) was intended for real-time?
A. ASH can be use for both real-time and historical analysis. It is a black box that records session activities and helps to analyze across several performance dimensions. Click here to see a quick demo.

Q. What is the difference between Oracle Enterprise Manager 12c and Oracle Database Control?
A. Database Control is a subset which runs off a single database. Oracle Enterprise Manager 12c is a central repository which allows administrators to manage and monitor from a single console.

Q. How does Real-Time Automatic Database Diagnostics Monitor (ADDM) work – the database is hung right?
A. Real-Time ADDM, included in the Oracle Diagnostic Pack for Oracle Database, uses 2 different modes of connection to the database. A normal connection and a diagnostic mode that is a lock less, latch less connection which allows only few actions. Using the diagnostic mode connection Real-Time ADDM performs a hang analysis and determines any blockers in the systems. Check out this demo to see how Real-Time ADDM works.

Q. Can we achieve all the new functionality in Oracle Enterprise Manager 12c using terminal?
A. No. Features like ASH Analytics, Real-Time ADDM and Compare Period ADDM are only available using Oracle Enterprise Manager 12c's console.

Q. Is Real-Time ADDM available only in Oracle Enterprise Manager 12c?
A. Yes, Real-Time ADDM is a new feature in Oracle Enterprise Manager 12c.

Q. Can you explain the difference between Oracle Database 11g Monitor in Memory Access Mode vs. Real-Time ADDM direct access to SGA?
A. Real-Time ADDM does not use Memory attach mode. We use a proprietary connection method which connects using a lock less, latch less connection bypassing the SQL Access layer.

Q. Is there any limit on the number of days on which ASH can be used for analysis?
A. The in memory ASH data is typically available for 1 hour or till the point the memory buffer is flushed to disk. You can find out ASH retention by using: select min(sample_time), max(sample_time) from sys.WRH$_ACTIVE_SESSION_HISTORY;

From more Oracle Database Management product information check out these resources:

Stay Connected:

Twitter | Facebook | YouTube | Linkedin | Newsletter

Wednesday Aug 31, 2011

How to create a consolidated backlog indicator report for EM11

While working with customers, and looking through some of the setups and configurations of Enterprise Manager, one question typically comes up all the time:

Q) How do I know my Enterprise Manager site is running healthy?

And the one thing, that is by far the most important for Enterprise Manager, is to keep an eye on the backlog indicators Enterprise Manager itself is collecting.
By looking at those numbers, you can more or less predict performance 'hiccups', or some bad behavior starting to form.

To help Enterprise Administrators keeping an eye on these important infrastructure metrics, a report can be created in Enterprise Manager to show all the relevant data in one single page.
To create this report, follow these steps:

  • In the Console, go to the 'Reports' tab, and use the 'Create' button to create a new report
  • On the report creation screen, enter this information
General Tab
 Title      : Backlog Indicators
 Category   : Enterprise Manager Setup
 Subcategory: Enterprise Manager Health
 Target     : Specify a 'specific' one:
              Name: Management Services and Repository
              Type: OMS and Repository
 Time Period: Check the 'Allow the report viewer to customize the time period' checkbox

Elements Tab
Add 8 elements, 4 charts, 4 tables, and use the layout button to represent then on 4 rows like this:

     Row 1   
       Chart from SQL
       Table from SQL
     Row 2
       Chart from SQL
       Table from SQL
     Row 3
       Chart from SQL
       Table from SQL
     Row 4
       Chart from SQL
       Table from SQL

  • Details for Row 1 (XML Loader backlog)
    Chart:
    Header    : XML Loader Backlog - Historical
    Type      : Timeseries chart
    Legend    : Bottom
    SQL to use:

          SELECT SUBSTR(key_value,0,INSTR(key_value,':')-1), rollup_timestamp, average
          FROM   sysman.mgmt$metric_hourly
          WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
            AND  metric_guid = HEXTORAW('B72713257822A65853FDF0C77554F660')
            AND  rollup_timestamp BETWEEN ??EMIP_BIND_START_DATE?? AND ??EMIP_BIND_END_DATE??

          ORDER BY rollup_timestamp, key_value

Table:
Header: XML Loader Backlog - Current
SQL to use:
      SELECT SUBSTR(key_value,0,INSTR(key_value,':')-1), value
      FROM   sysman.mgmt$metric_current
      WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
        AND  metric_guid = HEXTORAW('B72713257822A65853FDF0C77554F660')
      ORDER BY key_value

  • Details for Row 2 (EM Job backlog)
    Chart:
    Header: Job Backlog - Historical
    Type  : Timeseries chart
    Legend: Bottom
    SQL to use:
          SELECT 'System', rollup_timestamp, average
          FROM   sysman.mgmt$metric_hourly
          WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
            AND  metric_guid = HEXTORAW('CA4FF4BB045B18ADD7CA465C47A696F5')
            AND  rollup_timestamp BETWEEN ??EMIP_BIND_START_DATE?? AND ??EMIP_BIND_END_DATE??
          ORDER BY rollup_timestamp
Table:
Header: Job Backlog - Current
SQL to use:
      SELECT 'System', value
      FROM   sysman.mgmt$metric_current
      WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
        AND  metric_guid = HEXTORAW('CA4FF4BB045B18ADD7CA465C47A696F5')
  • Details for Row 3 (Notification backlog)
    Chart:
    Header: Notification Delivery Backlog - Historical
    Type  : Timeseries chart
    Legend: Bottom
    SQL to use:
          SELECT key_value, rollup_timestamp, average
          FROM   sysman.mgmt$metric_hourly
          WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
            AND  metric_guid = HEXTORAW('F4450F5AD8E95174CBFA21A261D5993C')
            AND  rollup_timestamp BETWEEN ??EMIP_BIND_START_DATE?? AND ??EMIP_BIND_END_DATE??
            AND  key_value != 'RCA'
          ORDER BY rollup_timestamp, key_value
Table:
Header: Notification Delivery Backlog - Current
SQL to use:
      SELECT key_value, value
      FROM   sysman.mgmt$metric_current
      WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
        AND  metric_guid = HEXTORAW('F4450F5AD8E95174CBFA21A261D5993C')
        AND  key_value != 'RCA'
      ORDER BY key_value

  • Details for Row 4 (Repository Metrics backlog)
    Chart::
    Header: Repository Metrics Backlog - Historical
    Type  : Timeseries chart
    Legend: Bottom
    SQL to use:
          SELECT key_value, rollup_timestamp, average
          FROM   sysman.mgmt$metric_hourly
          WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
            AND  metric_guid = HEXTORAW('5175E215E86BCCD6A55CF3D883B6AF2D')
            AND  rollup_timestamp BETWEEN ??EMIP_BIND_START_DATE?? AND ??EMIP_BIND_END_DATE??
          ORDER BY rollup_timestamp, key_value
Table:
Header: Repository Metrics Backlog - Current
SQL to use:
      SELECT key_value, value
      FROM   sysman.mgmt$metric_current
      WHERE  target_guid = ??EMIP_BIND_TARGET_GUID??
        AND  metric_guid = HEXTORAW('5175E215E86BCCD6A55CF3D883B6AF2D')
      ORDER BY key_value
  • Now save the report, and click on it, so you can see the consolidated backlog report of the site.
    On the top of the screen, you will have the option to set a time period, to report on backlog of a given period.
    The default is the last 24 hours, but you can change this to any period containing hourly rollup date (which typically will be the last 31 days, unless the system has been tweaked to change this default retention time)
About

Latest information and perspectives on Oracle Enterprise Manager.

Related Blogs




Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
3
5
6
7
9
10
11
12
13
14
15
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today