Help Center/ Relational Database Service/ FAQs/ Capacity Expansion and Specification Change/ Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?
Updated on 2022-09-21 GMT+08:00
Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?
Symptom
- The DB instance is in Faulty state after the original database port is changed.
- The DB instance cannot be connected using the new database port.
Possible Causes
The submitted database port is occupied.
Procedure
- If the database port is changed successfully, the previous change failed because the submitted database port was occupied.
- If the original database port still fails to be changed, contact technical support.
Parent topic: Capacity Expansion and Specification Change
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
