How to Use the PowerPoint Template - Oracle...Title How to Use the PowerPoint Template Author...

Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |

OpenWorld 2016 Never Miss a Beat: Always-On Monitoring with Oracle Enterprise Manager [CON6986]

Karilyn Loui, Principal Product Manager Yutaka Takatsu, Group Product Manager Manas Goswami, Director of Software Development Oracle Enterprise Manager September 22, 2016


Complete Cloud Control

Optimized, Efficient | |

Integrated Cloud & On-premise Stack Management

Agile, Automated

Complete Cloud & On-premise Lifecycle Management

Scalable, Secure

Superior Enterprise-Grade Management


Safe Harbor Statement

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3


Program Agenda

Overview

Architecture

Demo

Deployment Best Practices

Setup Requirements & Sizing Guidelines

High Availability

Current Limitations

FAQ

1

2

3

4

5

4

6

7

8


Overview

5


Enterprise Manager Cloud Control Infrastructure

6

• Oracle Management Repository (OMR)

– Heart

– Data Storage, rollup and purging

• Oracle Management Server (OMS)

– Brain

– Handles management data from Agents

– Handles administration requests from UI

– Sends out notifications

• Agents

– Nerve endings

– Gather management information

– Perform administration task


Always-On Monitoring: Background and Challenges

7

• No monitoring during Enterprise Manager (EM) patching and upgrades.

• No alerting when Oracle Management Server (OMS) or Oracle Management Repository (OMR) is down.

EM Architecture (without AOM)

OMS

Email

13.1 Agent

Monitored Targets

13.1 Agent

Monitored Targets

13.1 Agent

Monitored Targets

Agent

Monitored Targets

OMR


Customer Expectations

8

• Enterprise Manager Cloud Control monitoring to be available 100% of the time

• Continuous monitoring of targets during planned EM downtime

"Enterprise Manager is powerful for management of our big deal customers' large-scale systems. We use EM to manage a few hundreds of targets and is so important that we cannot afford to lose a single alert and we must manage these systems efficiently without error” -Naoto Kashiwagi, Head of Middleware and Cloud Engineering Team, NEC Japan -Yoki Moriyama, Deputy General Manager, NEC Japan


Always-On Monitoring (AOM) • New feature available in EM13c

– Never miss a beat - Continuous monitoring of targets during EM downtime

– Available as a separate java (J2SE) application

– Runs standalone without EM

9

Always-On Monitoring


Key Capabilities • 24x365 monitoring for Enterprise Manager targets

• “Always on” regardless of the status of Enterprise Manager

• Receives target availability events and metric alerts from agents

• Sends email notifications for all target status and metric alerts to ‘Downtime Contact’ target property

• Downtime Contact target property

– Global level: recipients for all alerts across all targets

– Target-specific level: recipients for all alerts on a specific target.

– Can be populated based on current email recipients from target down event rules (emcli generate_downtime_contact)

10


Architecture

11


Always-On Monitoring Topology

12

OMR

Targets, Metric Data, Alerts, Config

Email

AOM Repository

13.1 Agent

Monitored Targets

13.1 Agent

Monitored Targets

13.1 Agent

Monitored Targets

13.2 Agent

Monitored Targets

AOM Upload URL

Always-On Monitoring

OMS


Demo

13


Always-On Monitoring DEMO Assumptions

• EM and a target (WLS) are up and running

• You plan to stop EM as a planned downtime

• AOM is set up and started

• AOM notification is disabled (default)

• Downtime Contact is configured

• You want to enable AOM notification before the EM downtime so that you can continue to monitor the target WLS during the downtime

• The target WLS stops during the EM downtime

• AOM sends mail notification although EM is down

14

Demo Flow

• Verify OMS/Target Availability

• Verify AOM Status

• Enable AOM Notifications

• Stop OMS (for Planned Maintenance)

• Verify OMS is Down

• Stop the WebLogic Server (Target)

• Verify WLS is Down

• Receive Notification in Mail

• Disable AOM Notification (Once EM is back in service)


Deployment Best Practices

15


All-in one installation on a single host is not secure and not a recommended deployment model

In EM13.1, install OMR and AOM repository on different hosts from where OMS and AOM is installed

AOM Deployment Best Practices

16


In EM 13.2, install AOM service and OMS on different hosts


• Install AOM service on a non-EM host.

EM13.2

17


Install each component on a separate host to avoid a single point of failure

AOM sends Alerts to Admins during the EM downtime


18



• Have Always-On Monitoring up at all times regardless of whether Enterprise Manager is up or down.

– AOM repository syncs with EM repository daily by running a synchronization job.

• Disable AOM notification (default). Use emsctl enable_notification to turn notification on just before EM planned downtime.

19

Synchronizes data every 24 hours


$ ./emsctl list_agents Oracle Enterprise Manager Cloud Control 13c Release 2 Copyright (C) 2015, 2016, Oracle Corporation. All rights reserved. --------------------------------------------------------------------------------------------------------- Connecting to Always-On Monitoring Repository. Number of Agents that have communicated with Always-On Monitoring Service in the past hour : 3 URLs of these Agents are: https://myserver1.us.oracle.com:3872/emd/main/ https://myserver2.us.oracle.com:3872/emd/main/ https://myserver3.us.oracle.com:3872/emd/main/ $


• Use emsctl list_agents verb to ensure all agents are communicating

with AOM Service before taking down EM for maintenance.

– Provides a count of the number of agents communicating with AOM Service.

– Lists each agent URL for easy tracking.

20

EM13.2


Setup Requirements & Sizing Guidelines

21


Setup Requirements • Prerequisites:

– Identify an Oracle 12.1.0.2.0 Database to install the Always-On Monitoring repository

– Oracle Management Server (OMS) and Oracle Management Agent should be upgraded to EM 13c

– Grant required privileges to AOM schema owner

– Save the EM key to the Enterprise Manager repository

• Java Requirements:

– JDK7 must be installed on the AOM host

– JAVA_HOME environment variable must point to JDK7 location

• System Resource Requirements:

– Open file descriptors = http.queueSize + http.maxThreads

– Number of open database connections ranges between the number of active threads up to a maximum of 100 connections

– Maximum memory requirement is 10 Megabytes per thread

22


How to set it up

23

Step Description Status

1 Go to [$EM_HOME]/sysman/ems directory for the installation file (ems_13.x.0.0.0.zip) or download via Self-Update

2 Run emsca script to install and configure AOM

3 Setup email recipients in Enterprise Manager Cloud Control (Downtime Contact target property)

4 Sync with Enterprise Manager 13.x repository (gets latest target metadata, email addresses for Downtime Contact)

5 Specify AOM upload URL in Enterprise Manager 13.x

6 Start AOM service


Always-On Monitoring Sizing Guidelines

24

<100 Agents <1000 Targets <10 Concurrent User Sessions

Small EM Deployment

1 AOM Host (2 Core, 5 GB RAM, 12 GB Disk Space) 1 Database (2 Core, 3.5 GB RAM, 40 GB Disk Space)

AOM HW Requirements

*HW requirements for each AOM host

100 - 999 Agents 1000-9,999 Targets 10-24 Concurrent User Sessions

Medium EM Deployment

2 AOM Hosts (3 Core, 6 GB RAM, 12 GB Disk Space)* 1 RAC Database (3 Cores, 5 GB RAM, 80 GB Disk Space)

AOM HW Requirements

RAC

>=1000 Agents >=10,000 Targets 25-50 Concurrent User Sessions

Large EM Deployment

4 AOM Hosts (3 Core, 6 GB RAM, 12 GB Disk Space)* 1 RAC Database (6 Core, 9 GB RAM, 120 GB Disk Space)

AOM HW Requirements

RAC


Always-On Monitoring Database Sizing Considerations

EMS_TABLESPACE Table data and indexes specific to Always-On Monitoring are stored in this tablespace.

Undo When running the SYNC processes, especially the initial SYNC, the Undo tablespace is utilized especially when transferring large numbers of rows from the Enterprise Manager instance to Always-On Monitoring.

Temp The SYNC process will also utilize TEMP tablespace, especially when indexes are created or sorting occurs during the data movement process.

Redo Logs Redo logs should be large enough to minimize the number of checkpoints that occur during times when the SYNC is occurring. It is recommended to configure 3 x 1 GB REDO log files.

Special Oracle Parameter Settings

Use the same DB parameters as the EM repository. Set the following parameter to avoid unforeseen optimizer issues. ALTER SYSTEM SET OPTIMIZER_ADAPTIVE_FEATURES=FALSE SCOPE=BOTH SID='*';

25


Always-On Monitoring Database Sizing Example

26

Tablespace Name Total DB Space Allocation (GB)

EMS_TABLESPACE 55

Supporting Tablespaces 65

Total 120

• Allocate ~45% of space to EMS_TABLESPACE.

• Remaining 55% of space is used by supporting tablespaces (System, Sysaux, Temp, Undo, Users).

4 AOM Hosts (3 Core, 6 GB RAM, 12 GB Disk Space) 1 RAC Database (6 Core, 9 GB RAM, 120 GB Disk Space)

AOM setup for Large EM Deployment

RAC


High Availability

27


Key Features : • EM and AOM Repository housed in

RAC database + Local Data Guard

• Two (or more) Active OMS’s, AOMs

• Agents and console/EMCLI users talk to Server Load Balancer

• Load balancing for localized failures

• Incorporate AOM as a part of a Disaster Recovery plan in case of a site-wide failure

High Availability Solution for Always-On Monitoring Agent

>EMCLI

Users

Load Balancer

Active OMS

OMR with RAC OMR (Local Standby)

NFS

Active AOMs

AOM Repository with RAC

AOM Repository (Local Standby)

28


• Install AOM and OMS on different servers

• Add another AOM instance with a simple command (emsca add_ems)

• Configure Server load balancer (SLB) to redirect requests to available AOM instances

• Update configuration for all AOM instances at a single location (emsctl set_property)

• Run Multiple AOM instances (active-active)

– If one AOM instance goes down:

• SLB redirects agent alerts to another running AOM instance

• Queued notifications for downtime contacts are transferred to another available AOM instance

• Notification data is recorded into the AOM repository by the active AOM instance

High Availability Solution for Always-On Monitoring

29

EM13.2


Current Limitations

30


Always-On Monitoring Known Limitations

31

• After OMS comes up from maintenance, it will receive queued notifications from the Agent. The OMS will send the same notifications as AOM.

• AOM will notify Administrators based on the configured downtime contacts . It does not currently honor incident rules and advanced notifications (PL/SQL procedures, SNMP traps, OS command scripts).

• AOM will send notifications for target availability and metric alerts. There is no switch to configure what type of alerts to enable or disable.

• AOM will continue to send notifications during notification blackout.

• AOM notifications are sent via emails only.


FAQ

32


Always-On Monitoring FAQ Q1: Is the Always-On Monitoring repository database included in EM’s restricted-use license?

A1: EM includes a restricted-use license of the Oracle Database for use with the EM Repository. It does not include a license for the Always-On Monitoring repository.

33

Q2: Does AOM need to be installed on the same host as the OMS?

A2: For EM 13.1, AOM should be co-located with the OMS. For EM 13.2, we recommend installing AOM on a separate host from the OMS for high availability reasons.

Q3: Does AOM directly communicate with the OMS?

A3: AOM does not talk to the OMS. It syncs with the EM repository to get target metadata and downtime contacts and writes to the AOM repository. It was designed this way so it can be independent from the OMS.

Q4: Do we support AOM 13.2 with EM 13.1 agents?

A4: In order for AOM 13.2 to run, EM Agent and OMS must be running 13.2. AOM 13.1 works with EM 13.1 Agents and OMS.


Always-On Monitoring FAQ

34

Q6: Will EM patching or upgrade downtime be reduced if I use AOM?

A6: AOM does not affect the length of EM downtime.

Q5: How do I receive alerts from AOM only for Mission Critical targets?

A5: AOM will send alerts only for targets with “Downtime Contact” property defined. You can set the “Downtime Contact” property only for Mission Critical targets.

Q7: Can AOM automatically enable notification during unplanned downtime?

A7: AOM cannot monitor the status of the OMS or OMR. Therefore it cannot automatically enable notification during unplanned downtime.

Q8: Should we use AOM instead of EM HA?

A7: AOM does not replace EM HA as it is complementary to it. We recommend having AOM as part of your EM HA solution.


Oracle Enterprise Manager Sessions & Hands On Labs

ID Title Time Location

CON1125 (CFP) Accenture: Lift and Shift onto Oracle Database Exadata Cloud Service Using Database Consolidation Advisor

12:00 PM – 01:00 PM

Marriott Marquis - Salon 12

CON2260 (CFP) Nationwide: Database Patch at 1,000 Scale: Nationwide’s Oracle Enterprise Manager Fleet Maintenance Odyssey

12:00 PM – 01:00 PM

Moscone South - 305

CON6983 Building a WebLogic, SOA, Service Bus Cloud in your Data Center 12:00 PM – 01:00 PM

Marriott Marquis - Salon 13

CON6989 Best Practices for Upgrading to Enterprise Manager 13c: Learn from Customers

01:15 PM – 02:15 PM

Moscone South - 305

CON6988 Tips for maximizing reliability and scalability of Oracle Enterprise Manager

02:30 PM – 03:30 PM

Moscone South - 305

36

Thursday, September 22nd

Copyright © 2016, Oracle and/or its affiliates. All rights reserved.

Safe Harbor Statement

The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

37

How to Use the PowerPoint Template - Oracle...Title How to Use the PowerPoint Template Author...

Documents

Transcript of How to Use the PowerPoint Template - Oracle...Title How to Use the PowerPoint Template Author...