RDBMS SIG 26th January

Upgrade to

Enterprise Manager

13c NOW

Philip Brown @pbedba

Upgrade to EM13 Now

• Agenda• Introduction to Red Stack Tech and Me

• Upgrading OEM

• New Features

• Why you should upgrade NOW

Upgrade to EM13 NOW

• Red Stack Tech– Specialised Oracle Platinum Partner– 2014 Oracle Engineered Solution Partner of the Year (UK, EMEA, GLOBAL)– 2010, 2012, 2013 Oracle Technology Partner of the Year– 2010 EMEA Technology Partner of the Year– Professional Services / Managed Services / Cloud Services– Oracle ACEs and OCMs

• Philip Brown - philip.brown@redstk.com– Red Stack Professional Services Manager / Global Lead Systems Management – Oracle Ace Associate – Oracle OCP 9i, 10g, 11g, OCA 10g AS – Regular Speaker at the Oracle User Group– Contact me on LinkedIn and Twitter @pbedba– Resources:

• Blog http://www.redstk.com/blog/ #SavingYou15Minutes #em12c #em13c• Articles in Oracle Scene and OTECH Magazine

– Speaking at:• UKOUG License Special Event (Using OEM to manage license compliance)• TECH15 (em12c and In-Memory)• OOW15 (Hybrid Cloud)

Common Mistakes When Implementing 12c OEM

The most common mistake with implementing EM

Install OEM

Install agents with wild abandon

Get annoyed with OEM

relentlessly spamming you

The most common mistake with implementing EM

1# Oracle Enterprise Manager is an ‘ENTERPRISE’ application

2# It’s a critical part of your infrastructure

3# It’s designed to HELP you manage your estate

4# Oracle Enterprise Manager isn’t a glorified db console

5# Why isn’t success criteria defined?

6# IT Manager shouldn’t see this as ‘just’ a job for a DBA

Upgrading to EM13c

• Start Here:

• Documentation: https://docs.oracle.com/cd/E63000_01/EMUPG/toc.htm

• MOS: Checklist for Upgrading Enterprise Manager Cloud Control from Version 12.1.0.3/4/5 to 13c (Doc ID 2095192.1)

• Prerequisites:

• http://docs.oracle.com/cd/E63000_01/EMUPG/prerequisites.htm#CIHIDCED

• ./em13100_linux64.bin -silent EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE= /oracle/home/oraomsd1/stage/check.rsp -J-Djava.io.tmpdir=/oracle/home/oraomsd1/stage• Documented example .rsp file has install type as INSTALL not UPGRADE

Upgrading to EM13c

• Prerequisites:

• http://docs.oracle.com/cd/E63000_01/EMUPG/prerequisites.htm#CIHIDCED

Itemalter system set optimizer_adaptive_features=false scope=both sid='*';Management Agent Patch 19154291Management Agent Patch 20282974OMS Ports < 1024 Default Incident Rules Use of BI 12.1.0.3DB Service Instance RequestsRepo Snapshots VerificationLogin TriggersAudit Delete TargetSkip JobsCopy Key to OMS

ItemCheck for invalid objects in the EM repositoryCheck the job_queue_processes instance parameter value

Check the CBO stats gathering jobEnsure that EM triggers are not disabledCheck parallel max servers parameterCheck parallel min servers parameterCheck the existence of login/logoff triggersCheck the processes instance parameter valueCheck the pga_aggregate_target instance parameter valu

Check the sga_target instance parameter value.

Check the redo log size.Check the compatible instance parameter value.

• ./em13100_linux64.bin -silent EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE= /oracle/home/oraomsd1/stage/check.rsp -J-Djava.io.tmpdir=/oracle/home/oraomsd1/stage

Upgrading to EM13c

• Have you previously upgraded to 12.1.0.4 from 12.1.0.X?:

Ensure that EM triggers are not disabled

Known Issue Fails but not an issue: 12.1.0.4 Bug 20137693 : Triggers EM_ASSOC_INS_TRIG and EM_ASSOC_INS_TRIG are disabled after upgrading OM

Upgrading to EM13c

• Prerequisites:

Checking the Documentation

OS Space requirements only checked during the

initial install!

Patching Your Agents

• Prerequisites:

Patching Your Agents

• Prerequisites:

Patching Your Agents

• Prerequisites:

http://docs.oracle.com/cd/E63000_01/OEMLI/base_functionality.htm#OEMLI157

Do you want to patch all your agents????

I didn’t !

What kind of upgrade?

• Upgrade Choices:

• One-System Upgrade

• Two-System Upgrade (gone hurray)

• Software Only (Minimise Outage)• 90% time this works 100% of the time #Anchorman

Software Only Upgrade

• Step 1: Install the new middleware home (no outage)

• ./em13100_linux64.bin -J-Djava.io.tmpdir=/oracle/home/oraomsd1/stage

• Use the Java flag unless you have 10GB of /tmp space!

• It’s a wizard ‘simples’

• Step 2: Configure the new middleware home (outage)

Software Only Upgrade

• Step 2: Configure the new middleware home (outage)

• ./oracle/product/13.1.0.0/sysman/install/ConfigureGC.sh

• It’s a wizard again ‘simples’

Software Only Upgrade

• Step 2: Configure the new middleware home (outage)

• ./oracle/product/13.1.0.0/sysman/install/ConfigureGC.sh

• It didn’t check this just recommends you check it

Software Only Upgrade

• Step 2: Configure the new middleware home (outage)

• ./oracle/product/13.1.0.0/sysman/install/ConfigureGC.sh

• It will then run the pre-reqs again in the background as per:

./em13100_linux64.bin -silent EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE

• Step 2: Configure the new middleware home (outage)

• The rest is just a wizard (do you want to see a load of screenshots?) ask me after; there is nothing complicated about it!

Software Only Upgrade

Upgrade Failure Which Required Rollback!

• Known Issue: EM 13c: Checklist for Upgrading Enterprise Manager Cloud

Control from Version 12.1.0.3/4/5 to 13c (Doc ID 2095192.1)

I’m not using Cloud or Cost Centre Management??? (Doesn’t matter)Fix is hashing out a REM line in a script (slightly bizarre)

Upgrade Error Which WON’T Require Rollback!

• Issue: Upgrade will create a new user with the password currently used for

SYSMAN, therefore ensure your current database profile will still allow that password

You’ve Upgraded Well Done

• What about those agents?

• The ones which were patched were fine!• The ones which weren’t on the latest release were fine!• The ones on Windows were fine!• The ones which were down were fine!• The ones in blackout were fine!

• The ones I didn’t patch on AIX weren’t (but now I know what the issues were and how to resolve them)

• EM 12c : Agents On AIX Servers Cannot Secure / Upload to OMS Configured to Accept only TLS1 Connections (Doc ID 1965676.1)

Post Upgrade

• This took about two minutes….

To gather overall upgrade timings look at $MIDDLEWARE_HOME/cfgtoollogs/oui

To gather repository upgrade timings look at /oracle/product/13.1.0.0/sysman/log/schemamanager/…/../em_repos_modify.log

EM13c New Features

Alta Skin Re-Touch – Databases Overview

EM13c New Features

Alta Skin Re-Touch – Databases Overview

EM13c New Features

Alta Skin Re-Touch – Database Page

EM13c New Features

Alta Skin Re-Touch – Database Page

EM13c New Features

Incident Compressionhttp://docs.oracle.com/cd/E63000_01/EMADM/incident_mgmt.htm#EMADM15277

EM13c New Features

Incident Compression (Without Compression)http://docs.oracle.com/cd/E63000_01/EMADM/incident_mgmt.htm#EMADM15277

Generic Incident Rules without thought will be a pain in the OEM

Incidents in OEM once resolved will automatically be removed, not the case with EMAIL

EMAIL (50+ For Stopping the OMS Agent) INCIDENT MANAGER (9 In Incident Manger)

EM13c New Features

Incident Compression (With Compression)http://docs.oracle.com/cd/E63000_01/EMADM/incident_mgmt.htm#EMADM15277

EMAIL (50+ For Stopping the OMS Agent) INCIDENT MANAGER (1 In Incident Manger)

If you are still using email after that this then you should (Insert Suggestion…)

EM13c New Features

Incident Compression (With Compression)

EM13c New Features

Export and Import of Incident Rules

Export and Import….

Configuration ExtensionsMetric Extensions

Monitoring TemplatesCompliance Frameworks, Standards and Rules

EM13c New Features

Always On Monitoringhttp://docs.oracle.com/cd/E63000_01/EMADM/em_mon_svc.htm#EMADM15489

Key Install Notes:

emsca zip file is located in the sysman directory of your Middleware Home

emsca requires JDK 7 to run, JDK 7 is located in your Middleware Home

under Oracle Common

The connection strings to the repository in the documentation reference

some very strange port but it’s actually wanting the database listener port

If you haven’t added the BIN directory to of your JAVA home to your PATH

you will get an error below with regards to the KEYTOOL (PKI)

If you get the error below the emsca is clever enough to re-run and then

finish off the bit with the keys

/u05/ems/ems/scripts/emsKeystoreCreator: line 7: keytool: command not found

Oracle PKI Tool : Version 12.1.3.0.0

Copyright (c) 2004, 2014, Oracle and/or its affiliates. All rights reserved.

/u05/ems/ems/scripts/emsKeystoreCreator: line 9: keytool: command not found

You have new mail in /var/spool/mail/oracle

EM13c New Features

Always On Monitoringhttp://docs.oracle.com/cd/E63000_01/EMADM/em_mon_svc.htm#EMADM15489

[oracle@gc13beta scripts]$ ./emsctl start

Oracle Enterprise Manager Cloud Control 13c Release 1

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

------------------------------------------------------------------

Starting Always-On Monitoring.

[oracle@gc13beta scripts]$ ./emsctl status

Oracle Enterprise Manager Cloud Control 13c Release 1

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

------------------------------------------------------------------

Always-On Monitoring Version : 13.1.0.0.0

Always-On Monitoring Home : /u05/ems/ems

Started At : January 10, 2016 12:41:36 AM GMT

Last Repository Sync : January 10, 2016 12:36:53 AM GMT

Upload URL : https://gc13beta.redstk.com:8081/upload

Always-On Monitoring Process ID : 27743

Always-On Monitoring Repository : gc13beta.redstk.com:1530:AOM

Enterprise Manager Repository : gc13beta.redstk.com:1521:OMR

Notifications Enabled : false

Total Downtime Contacts Configured : 2

EM13c New Features

Always On Monitoringhttp://docs.oracle.com/cd/E63000_01/EMADM/em_mon_svc.htm#EMADM15489

[oracle@gc13beta scripts]$ ./emsctl enable_notification

Oracle Enterprise Manager Cloud Control 13c Release 1

Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.

------------------------------------------------------------------

Notifications have been enabled. There are downtime contacts configured.

Connecting to Always-On Monitoring repository.

Starting synchronization with EM.

Synchronizing with EM repository: sysman@gc13beta.redstk.com:1521:OMR

Synchronizing Targets data.

Synchronizing Alerts and Availability data.

Synchronizing Notification Metadata data.

Synchronizing Target Metric Metadata data.

Synchronization complete at : Sun Jan 10 00:43:57 GMT 2016

Synchronization is done:• Once per day by an automated job• When you enable notifications

EM13c New Features

Securityhttps://docs.oracle.com/cd/E63000_01/EMSEC/app_a.htm#EMSEC13126

https://docs.oracle.com/cd/E63000_01/EMSEC/app_privs.htm#EMSEC13195

Roles: Non-Target Specific Roles (EM_ALL_DESIGNER, EM_COMPLIANCE_DESIGNER)Target Privileges: Administer Operations on a Target (All or Specific) (Full Operator View)Resource Privileges: Non-Target Specific Operations (Fine Grained Control)

EM13c New Features

Security Example 1: Roles EM_USER, PUBLIC

EM13c New Features

Security Example 2: (Use of a Role (T&R Privileges) Roles EM_USER, PUBLIC, Patch Operator

EM13c New Features

Security Example 3: (added target privileges)Roles EM_USER, PUBLIC,

EM13c New Features

Security Example 4: (added resource privileges)Roles EM_USER, PUBLIC

Target and Resource Privileges (you’re effectively making your own roles!)

EM13c New Features

Security Example 4: (added resource privileges)Roles EM_USER, PUBLIC

Simples, target and resourceprivileges……

EM13c New Features

Security: So what’s new????? https://docs.oracle.com/cd/E63000_01/EMSEC/sec_best.htm#EMSEC15121

Predefined and FGA

18 to 159!

Approximately 300+ New Verbs

EM13c – EMCLI Verbs

EM13c – EMCLI Verbs

EM13c New Features

EM13c New Features

./emcli update_db_password -target_name=“DB1" -user_name="SYSTEM" -change_at_target="yes"

Enter value for old_password :

Enter value for new_password :

Enter value for retype_new_password :

./emcli update_db_account_status -target_name="DB1" -user_name="SYSTEM" -action=LOCK -connect_as="DBUserName:sys;DBPassword:XXXXXXX;DBRole:sysdba"Success!! Account status for SYSTEM has been updated.

./emcli update_db_account_status -target_name="DB1" -user_name="SYSTEM" -action=UNLOCK -connect_as="DBCredsOwner:sysman;DBNamedCreds:SYS_DB1"Success!! Account status for SYSTEM has been updated.

EM13c New Features

Great NEWS EVERYONE!!!!

OEM Now Supports……… CHEF

Tumbleweed……..

You know CHEF…Jenkins, Scrum, Stories..

Tumbleweed……..

DEVOPS!

EM13c New Features

New Target Type: Database Services

• Not enabled out the box• Ensure your agent is upgraded to 13.1.0.0!

• Update OEM Setting• $ ./emctl set property -name oracle.sysman.db.discovery.dbservice -value

“ALL“• NONE, NON_SYS, ALL

EM13c New Features

System Broadcast

https://docs.oracle.com/cd/E63000_01/EMCLI/cli_verb_ref.htm#CHECFJDD

$ ./emcli publish_message -toOption="SPECIFIC" -to="dbapb" -message_type="INFO" -message"There is a snake in the server room"

Error: The command name "publish_message" is not a recognized command.

EM13c New Features

Why you should upgrade NOW?

• Out the box it works• It’s easy to upgrade• You have already paid to have it developed• 12.1.0.5 is now legacy• 12.2 RDBMS

The longer you wait the closer it is to the next upgrade…

Get on Twitter…. Get your blog on…

@courtneyllamas@dbasushi@dbakevlar@oracle_em@harisrinivasan@petesharman@adeeshF@subh_here@pbedba

Any Questions?

Philip Brown

@pbedba

Red Stack Tech27 – 30 Railway StreetChelmsfordEssexUnited KingdomCM1 1QS