My Oracle Support Banner

SRDC - Exadata Cloud Mandatory Data Collection for VM Cluster Node Unexpected Reboot (Doc ID 2756413.1)

Last updated on APRIL 12, 2024

Applies to:

Gen 2 Exadata Cloud at Customer - Version All Versions to All Versions [Release All Releases]
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Oracle Database Cloud Exadata Service - Version N/A to N/A [Release 1.0]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Information in this document applies to any platform.

Purpose

The process outlined below will guide the Exadata Cloud Customer through collecting diagnostic data from their Virtual Database Node environment, which will help Exadata Support narrow down the cause of your problem.

In Exadata Cloud Service environments including Gen 1 & Gen 2 Exadata Cloud at Customer and Exadata Cloud Services OCI and OCI-C customers manage the software that directly affects their application, in this case, DOMU.

This document is tagged as a Service Request Data Collection (SRDC) document; this means that it has been specially designed to provide the reader with the necessary instructions to identify the data collection forVM Cluster Node Unexpected Reboot / Crash in an Exadata Cloud environment

Oracle highly recommends that you maintain the latest version of AHF and Dbass tooling across your Exadata Cloud environment. References:
Doc ID 2550798.1 Autonomous Health Framework (AHF) - Including TFA and ORAchk/EXAChk (Doc ID 2550798.1)
Doc ID 2404336.1 DBaaS Tools - Cloud Tooling RPM Release Notes

Please note that Support may also request data collection from the internal Cloud Operations team for the analysis.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.