Learn about troubleshooting common issues with Managed Databases (also called Cloud Databases).
OVHcloud Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance. Each service is powered by third-party database management systems (DBMS), maintained by third-party companies or communities such as PostgreSQL community, Oracle, RedisLab, Apache Foundation, and others.
I can't connect to Cloud Databases
If you are unable to connect to Cloud Databases, please ensure the following:
- Your database instance is up and running: When you create a new database instance, you have to wait a few minutes before getting your service up and ready to use. You can verify the status of your service in the Control Panel. It should be in a "running" state. Please note that when you modify database instances, such as adding nodes or modifying the version of the DBMS, your service can switch from a "running" state to "updating". You may experience connection issues during this time.
- At least one user is created: Please verify that you have at least one user created for your service, with sufficient user roles. If you are unsure about the password, create a new user with a newly generated password.
- At least one IP address is authorized: By default, a database instance can not be reached from the outside. You need to specify, in the Control Panel, at least one IP address to trust (authorize). You need to trust the IP address from which the connection request will be initiated. Tip: For a short lap of time, you can try to allow an IP address wild card 0.0.0.0/0. This rule will allow any IP connection. Please use it carefully.
- Correct Service URI syntax is used: Be sure to copy the exact Service URI provided in your Control Panel to avoid syntax issues. Connect to the default port for each DBMS.
- Up-to-date client and/or coding framework: Each DBMS client provides a compatibility matrix for software versions. Be sure to follow official DBMS prerequisites, such as Linux package versions, PHP or Python versions, etc.
To help you through your connection journey, we detail the exact procedures in our Managed Databases documentation. Don't hesitate to browse the guides for more details.
Cloud Databases - lost password
OVHcloud does not store passwords for Cloud Databases. You can't retrieve a password. If you forget your password, you have two solutions:
Regenerate password: In the Control Panel, select the
userstab in your database service. For the desired user, on the right side of the table line, you will find an action button. Select
Regenerate password. Once regenerated, the new password will be shown in your web browser. Please copy it and store it securely. Tips: By doing this, ALL existing connections made with this user will be stopped. You will have to modify the password in all scripts using this user.
Create a new user: In the control panel, select the
userstab in your database service. Create a new user with the desired roles. A password will be generated and will be shown in your web browser. Please copy and store it securely.
To help you through user management, please feel free to read our guides for more details in the Managed Databases documentation.
Cloud Databases - running out of storage
We recommend monitoring your Cloud Databases metrics as much as you can, especially for storage space. If you are running low on storage space, OVHcloud will:
- Send an alert to your main email contact (NIC-Admin) when reaching 80% of storage capacity.
- Put your database instance(s) in "DISK_FULL" state and read-only+delete mode when reaching 95% of storage capacity.
- Put back your database instance in read-write mode once storage capacity goes under 80%.
If you are reaching the storage capacity limits, you have two options:
- Upgrade to higher flavors: Cloud Databases come with included storage inside each node flavor. Depending on the DBMS, you may be able to change the flavor model to a higher one, with a bigger storage capacity.
- Clean up data: Remove useless data in your database instance, allowing you to reach an acceptable level of storage capacity.
Cloud Databases - experiencing slowness
Several reasons may cause a database instance to slow down. To start troubleshooting:
- Verify metrics dashboard: The first step is to understand if slowness is punctual or periodic. Many metrics can help you to understand if this phenomenon happens each hour, each day, or is non-cyclical.
- Configure metrics to your needs: If the experienced slowness matches with a high level of metrics, such as CPU or RAM usage, it means that your database instance is reaching its maximum performance. If you reach max performance, it can be related to legitimate operations on your side or code malfunctions. OVHcloud is not responsible for the scripts used.
- Check the slow queries: Major DBMS allow you to investigate slow queries, meaning investigating the queries made on databases that take too much time. Reducing the time of queries is always a performance benefit.
- Verify OVHcloud health statuses: OVHcloud may experience network or database issues. We list them on https://status.us.ovhcloud.com.
If the slowness persists, please contact our support team.
Cloud Databases - outage or reboot
A database instance outage can occur when lower layers (software or hardware) do not work in optimal conditions.
Depending on the outage, your usage of the service can be affected by:
- overall slowness;
- a reboot;
- being unable to connect to the databases;
- being unable to read or write data.
To troubleshoot an outage :
- Check database instance status: Connect to your Public Cloud Control Panel and explore your database services. Verify the status. Nominal status is Running.
- Check OVHcloud health statuses: When major outages occur, they are listed on https://status.us.ovhcloud.com.
A database instance reboot can occur when:
- A major maintenance operation is planned. Verify your maintenance window directly on the Public Cloud Control Panel;
- A modification on the cluster is requested. Depending on the chosen DBMS and service plan, a reboot can be required even if we try to avoid it as much as we can. When a modification is required, we inform customers about it via the Control Panel.