After you register an instance in Data Management (DMS), you can edit its Instance Owner, DBA, basic information (such as the database account, Security Hosting, and Security Rules), or advanced information (such as the Environment Type, Lock-free Schema Change, and query and export timeouts).
This page covers the following tasks:
Prerequisites
Before you begin, ensure that you have:
-
The Administrator or DBA system role in DMS
Change instance owner or DBA
Before you change ownership:
-
The new Instance Owner must be a registered DMS user. To add a user, see User Management.
-
The new DBA must be a registered DMS user with the DBA system role.
-
An instance can have multiple Instance Owners but only one DBA.
-
Log on to the DMS console V5.0.
-
In the database instance list on the left, find the target instance.
-
Right-click the instance name and change the DBA or Instance Owner.
Enable or disable Security Hosting
Change the environment type
Environment types
The Environment Type of an instance takes effect only in DMS. DMS provides eight environment types in two categories:
| Category | Environment type | Environment ID |
|---|---|---|
| Test | Development | dev |
| Test | Test | test |
| Test | SIT | sit |
| Test | UAT | uat |
| Test | Performance test | pet |
| Test | Staging | stag |
| Production | Production | product |
| Production | Pre-production | pre |
Steps
-
Log on to the DMS console V5.0.
-
In the database instance list on the left, find the target instance.
-
Right-click the instance name and choose Edit.
-
In the Advanced Information section, find Environment Type and select the target type from the drop-down list.
-
Click Save.
Export instance configurations
Export instance configurations—such as Control Mode, Environment Type, and instance source—to manage instance resources offline.
For security reasons, exported configurations do not include the database account or password.
-
Log on to the DMS console V5.0.
-
In the top navigation bar, choose Data Assets > Instances.
NoteIf you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner and choose .
-
On the Instance List tab, select the target instances.
-
Choose More > Export Configuration.
Your browser downloads an Excel file named instances.
Batch edit instance information
-
Log on to the DMS console V5.0.
-
In the top navigation bar, choose Data Assets > Instances.
NoteIf you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner and choose .
-
On the Instance List tab, select the target instances and click Batch edit.
NoteAll selected instances must be of the same database type, for example, all MySQL.
-
In the dialog box, select the checkboxes for the configuration items you want to change and edit the instance information.
FAQ
-
Why do I get an "Access denied for user 'example_user'@'%' to database 'example_db'" error when creating a database in DMS?
The database account lacks permission to create databases. Either grant the necessary permissions in the instance console, or log on to DMS with a more privileged account. For details, see Modify account permissions.
-
Why are permissions lost after I change the IP address of a VPC-connected instance?
DMS binds permissions to the instance ID, not the IP address. When you change the host IP to an address previously used by a deleted instance, DMS treats the change as a restoration of that deleted instance—it marks your current instance as "deleted" and reactivates the historical one. Because the reactivated instance has a different instance ID, the permissions bound to your original instance are lost.
-
Does the DMS instance ID change after I modify the IP address of a VPC-connected instance?
It depends on whether the new IP address has a history in DMS:
-
New IP address with no prior history in DMS: DMS updates the IP address for the current instance. The instance ID and permissions remain unchanged.
-
New IP address previously used by a deleted instance: DMS restores the historical instance and deletes the current one. The active instance ID changes to that of the historical instance, and the original permissions are lost.
-