Relocating a Service Entitlement to Another Identity Domain

The provisioning of identity domains for service entitlements is based on service availability and capacity constraints in data centers. When you activate orders, typically, they are activated in a default identity domain or account.

As an account administrator, you can use the My Account application to move a service entitlement (if supported by the service type) without instances or data to another identity domain that you have access to. For example, you can move a service entitlement (S1) in an identity domain (ID1) to another identity domain (ID2) per your service requirement.

However, when moving a service entitlement, ensure the following:

• For service entitlements, the target identity domain must belong to the same customer account ID in any data center. However, you must be the account administrator in both the identity domains (source and target).

• The target identity domain should not contain other entitlements of the same type as those that are being moved. For example, if you want to move Oracle Database Cloud Service (Oracle DBCS) and its dependent services (such as Oracle Database Backup, Compute, or Storage) to another identity domain, the target identity domain should not have existing Oracle DBCS entitlements.

• You are an account administrator for the dependent services, which should also be relocated to the same target identity domain. For example, if you are trying to move Oracle DBCS to another domain, then you must be an account administrator for the dependent services as well.

• The selected service entitlement must be in an active or suspended state.

During relocation, the primary service administrator for the selected service entitlement is automatically added to the target identity domain. You must add other users and administrators and assign roles.

To move a specific service entitlement to a different identity domain:

1. Sign in to My Account.
2. Navigate to the appropriate service listing.
3. Click the service entitlement name to open the details page for that service.
4. Click the Identity Domain Administration tile in the details page.
5. Click the Relocate Service tab.
6. Select an identity domain from the list. Domains that contain only trial services are not displayed in the list.
7. Alternatively, you can specify a new target identity domain to move the service. Select Create New Identity Domain and enter a unique domain name.
8. Specify a service name in the Service Name field. If the service you are moving already exists in the target domain, the system prompts you to change the service name. For example, if you are moving a service entitlement S1 from the domain ID1 to ID2 that already has S1, then you can rename S1 to something like S1-new. For services that come in pairs and contain production or test as suffixes, ensure that the new service name you provide continues to have these corresponding suffixes.
9. Click Submit. The system prompts you for confirmation. Click Ok to proceed.

Relocation of a service entitlement is not immediate. You can see the relocation status on the My Account dashboard when you hover over the status icon. The primary service administrator gets an email with the relocated service details when the service relocation is complete.

While the service status is still pending relocation, you can’t perform other actions such as service lock, service association, domain rename, or domain administrator creation.

Note:

You can’t submit another relocation request for the selected service entitlement while one request is still in progress.

Relocation of the selected service entitlement can fail if:

• You’re not an account administrator to any of the dependent services that must be relocated.

• The target identity domain does not belong to the same account.

• The target identity domain contains services that are of the same type as those being moved.

Note:

The Relocate Service tab is enabled only for service entitlements that support service relocation and is disabled for trial services.