OCI: Action Required To Prevent Node Termination For Tenant: MyTenant - [CN-XXXXXX] - Reboot Notification
(Doc ID 2816500.1)
Last updated on AUGUST 09, 2024
Applies to:
Oracle Cloud Infrastructure - Database Service - Version N/A and laterInformation in this document applies to any platform.
Goal
Sometimes Oracle Cloud customers receive an email like below one:
Oracle Cloud Infrastructure Customer,
The Oracle Cloud Infrastructure Team detected one or more of your databases as unstable due to an error in the underlying infrastructure. At the time listed below, Oracle Cloud Infrastructure will attempt to move your database(s) to different infrastructure. However, in some cases, databases may need to be terminated as part of the repair. It is critical that you move your database(s) before the time listed below to avoid potential termination.
Details related to affected instance(s), timing, and instructions on how to move your affected database(s) can be found below. Action Required
Action Required By: October 30, 2021 22:30 UTC
Tenant Name: MyTenant
How do I move my database(s)?
DB Systems can be moved with a simple reboot. For more details, please check our online documentation here: https://docs.cloud.oracle.com/iaas/Content/Database/Tasks/managingDBsystem.htm
What should I do if I am still having an issue?
Please contact support to create a Service Request and provide the Reference Number and Tenant ID shown below.
Reference Number: CN-123456
Tenant ID: ocid1.tenancy.oc1..aaaaaaaaaaaaa......
Region DB Node DB System
US East (Ashburn) hostname ocid1.dbsystem.oc1.iad.abcdxxxxx.........
Due to that, the following questions could arise:
QUESTIONS
==========
1. Can you please tell what is this issue regarding?
2. Shall I just go ahead and reboot the DB system to resolve this issue?
3. Do we need to take a full backup of the database before rebooting?
4. Are there any risks with rebooting DB System?
5. If I take full backup, will that incur any kind of additional cost?
6. After the reboot, will the node name or IP address change?
7. Do we need to shutdown database before rebooting the node?
8. Why can't Oracle reboot the node since the issue is on its infrastructure?
9. How does someone shutdown the CDB from OCI?
10. How long will the reboot take?
11. If we reboot earlier on our own terms, Will a reboot still be scheduled by Oracle?
12. How to confirm the reboot is valid.?
Solution
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
| Goal |
| Solution |
| References |