ApsaraDB RDS:Create a database

When creating a database on the Databases page of an RDS SQL Server instance, the error message The current database name is incorrect. Please reset the database name. appears with error code InvalidDBName.Duplicate.

The database cannot be created because a database with the same name already exists.

The Databases page of an RDS SQL Server instance only displays databases with ONLINE status. Databases with non-ONLINE status (such as RESTORING, RECOVERING, OFFLINE, etc.) are not displayed in the console. This might lead users to mistakenly believe that the database does not exist, resulting in creation failure.

1. Connect to the SQL Server instance using SSMS.

2. Execute the following SQL to view non-system databases and their status:

   SELECT
       [name] AS DatabaseName,  -- Database name
       state_desc AS StateDescription,  -- Current database status (such as ONLINE, OFFLINE, RECOVERING, etc.)
       recovery_model_desc AS RecoveryModel  -- Database recovery model (such as SIMPLE, FULL, etc.)
   FROM
       sys.databases
   WHERE
       database_id > 4; -- Filter out system databases

   As shown below, the query results will confirm whether a database with the same name exists and its current status.

   

3. For databases with non-ONLINE status that have the same name, resolve the issue based on different scenarios:

   • Scenario 1: OSS backup data recovery to cloud with the option to not open the database

     • Cause

       When using OSS backup data recovery to RDS SQL Server, if you select the Access Pending (Incremental Backup) option, the database will be in a non-ONLINE state.

       

     • Solution

       If you need to continue uploading incremental backup files, you need to open the database from the Cloud Migration Records of Backup Data tab after the recovery is complete. If you no longer need incremental recovery, you can open the database directly.

       

       If this database is no longer needed and you want to recreate it, you can open the database and then delete the database. After deletion, you can create a new database.

   • Scenario 2: Database enters RECOVERING state due to log space being full

     • Cause

       When log space is full, logs cannot be written, and the database enters the RECOVERING state. You can confirm this by checking the instance error logs:

       

     • Solution

       • If the instance space is full and log space cannot be expanded, you need to expand the instance storage space and then manually restart the instance. After restart, the RECOVERING process will continue, and when recovery is complete, the database will return to ONLINE status.

       • If the database log file has a growth limit set and the log space is full, but the instance space is not full, you only need to adjust the database log space limit without restarting the instance. The steps to adjust the database file limit are as follows:

         

         

         

       If this database is no longer needed and you want to recreate it, wait until the database status becomes ONLINE, then delete the database. After deletion, you can create a new database.

   • Scenario 3: Database manually set to OFFLINE status

     • Cause

       The database might have been manually set to OFFLINE status by an administrator.

     • Solution

       Use the sp_rds_set_db_online stored procedure to set the database back to ONLINE status:

       USE master;
       GO
       EXEC sp_rds_set_db_online 'database_name';
       GO

       If this database is no longer needed and you want to recreate it, wait until the database status becomes ONLINE, then delete the database. After deletion, you can create a new database.