OCI - incident & escalation procedure

Oracle Cloud Infrastructure

Incident Management & escalation - Standard Process

For OCI incidents (outages, planned/unplanned downtime), general support and
escalations, a standard process (in escalation order of below) must be adhered to.

1.Oracle Cloud Support - https://support.oracle.com

Log a Service Request (SR) using your OCI CSI (Customer Support ID), ensuring you are in Cloud Support (not My Oracle Support).

Using Oracle support for the First Time using the customer Support ID

https://docs.cloud.oracle.com/en-us/iaas/Content/GSG/Tasks/usingsupportfirsttime.htm#Using_Oracle_Support_for_the_First_Time

Logging a ticket from inside OCI console https://docs.cloud.oracle.com/en-us/iaas/Content/GSG/Tasks/contactingsupport.htm

Don’t be afraid to assign as Severity 1 or 2 to help get expedited service/attention

Regularly keep your SRs up-to-date (SRs can self-close in 5 days if left unattended)

2.Request Management Attention on an SR (if needed)

How To Request Management Attention on a Service Request (SR) with Oracle Support Services (Doc ID 199389.1)

Request Duty Manager attention – call 0870 4000900

3.Oracle Solutions Consulting (if 1 & 2 above are “failing”)

Get access/help from product specialists by contacting your OCI Account team.

4.Contact your Technical Account Management (if 1, 2 & 3 above are “failing”)
 

Ensure you have the following available : 

Cloud Services Account Name:
Customer Account:
OCID:
Order ID
Subscription ID:
CSI Number:
Home Region:
Identity Domain:

Oracle OEM 13.5

Not going to spend an age on this, just to say 13.5 is now available - a lot of information on the web already :

https://www.markusdba.net/2021/04/10/upgrade-enterprise-manager-cloud-control-to-13-5/

Going to upgrade my "sandbox" OEM to 13.5 and will post on that instead.

Recently moved to 13.4 - mainly as the Adobe Flash end of support was at the end of 2020. 

The migration from 13.2 to 13.4 was pretty painless but did hit a problem when moving the agents.  

EM 13c: OMS Communication to all Agents Failing with "[handshake has no peer]" but Agents are able to Upload Successfully to the OMS (Doc ID 2381313.1

/u02/app/oracle/middleware2/oracle_common/jdk/jre/lib/security

Was

# jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048

jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \

EC keySize < 224, 3DES_EDE_CBC, anon, NULL

As per the doc from the original 13.2 version - this works

# jdk.tls.disabledAlgorithms=MD5, SSLv3, DSA, RSA keySize < 2048

jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 768


Not exactly sure what “revert back the changes made to disable the MD5withRSA algorithm” – I read it as per 13.2 ?


After a stop / start of OMS it was then ok.

Hopefully 13.5 should be easy enough - not entirely sure what advantages over 13.4 but we will see.

Oracle New Features

 

This is an excellent video on probably the two big features going forward with Oracle 19.

 

 
 
 
Planning to run some Oracle 19 installations and patch at the same time and use the read only feature of the Oracle Home. Will post updates and let you know how I get on but in the meantime suggest you watch this video.