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?
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
Change the original DB port to the new port again. For details, see Changing the Database Port.
- If the original database port is changed successfully, the previous change failed because the submitted database port is occupied.
- If the original database port still fails to be changed, contact technical support.
Parent topic: Capacity Expansion and Specification Change
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.