Help Center/ Relational Database Service/ User Guide (Paris Region) / FAQs/ Capacity Expansion and Specification Change/ Why Does the DB Instance Become Faulty After the Original Database Port Is Changed?

Updated on 2022-12-08 GMT+08:00

View PDF

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

Previous topic: Are My RDS DB Instances Available When Scaling?

Next topic: Database Parameter Modification

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.