ODA Primary Note for a Crash, Hang or Eviction
(Doc ID 2563180.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database Appliance X7-2 HA Hardware - Version All Versions to All Versions [Release All Releases]Oracle Database Appliance Software - Version 2.10.0.0 to 18.3.0.0.0 ODAVP
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
It is important to consider the scope and granularity of the problem.
When researching your problem make sure you have a good understanding what the problem is regarding, and what is not related!
For Example: Crash, Hang, Eviction my be interpreted differently depending on the perspective of the user.
What one person considers an "outage" may be anything from a complete failure due to a hardware issue to a failed query, or even problems logging on.
A "Crash" can be for the database, a server, CRS, OS (kernel panic), a power outage or hardware issue or even a middle tier problem from the user perspective.
A "Hang" and "Spin" have very different sources, but to the user have the same symptom as a connection problem.
An "Eviction" can occur for a RAC instance on a single-node, but be due to Hardware, Firmware, OS, Resources, Database or CRS issues.
The point:
Take time to isolate the scope of the problem based on the errors seen.
Working from the session or process level can often be easily identified when a second attempt for the operation works.
When nothing works for any user, start at the SYSTEM level including:
Application: what is running and what is not? Server? Database? Application?
Resources (memory, storage, and CPU),
Network and connectivity (Do local connections work but the application or external connections fail?)
When researching your problem make sure you have a good understanding what the problem is regarding, and what is not related!
For Example: Crash, Hang, Eviction my be interpreted differently depending on the perspective of the user.
What one person considers an "outage" may be anything from a complete failure due to a hardware issue to a failed query, or even problems logging on.
A "Crash" can be for the database, a server, CRS, OS (kernel panic), a power outage or hardware issue or even a middle tier problem from the user perspective.
A "Hang" and "Spin" have very different sources, but to the user have the same symptom as a connection problem.
An "Eviction" can occur for a RAC instance on a single-node, but be due to Hardware, Firmware, OS, Resources, Database or CRS issues.
The point:
Take time to isolate the scope of the problem based on the errors seen.
Working from the session or process level can often be easily identified when a second attempt for the operation works.
When nothing works for any user, start at the SYSTEM level including:
Application: what is running and what is not? Server? Database? Application?
Resources (memory, storage, and CPU),
Network and connectivity (Do local connections work but the application or external connections fail?)
Crash, Hang or Eviction
Generic
- Database
- Query
- Connection for single user: Others users work
- Server
High Availability
An ODA in a high availability ( two node ) configuration
- Crash ( server or database)
- Hang ( server or database)
- Node eviction (server)
- Outage (single or both nodes)
- Inaccessible (single or both nodes)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Crash, Hang or Eviction |
| Generic |
| Cause |
| Solution |
| Generic |
| ODA HA ( two node ) configuration |
| References |