On this page
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?

Updated on 2022-09-21 GMT+08:00

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.
Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback