Help Center > > 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?
Updated at: Jun 09, 2021 GMT+08:00
- 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.
The submitted database port is occupied.
Change the database port to the new port again. For details, see Changing a Database Port.
- 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.