Oracle Analytics and AI

Sushanta Chakraborty-Oracle

Hello,

Customer has provisioned FDI in a wrong tenancy. Currently, only the non-prod instance have been provisioned. Therefore we are seeing "0 non-prod instances are available", and "1 prod instance is available". Questions:

1. How to de-provision the non-prod instance? Is it as simple as just deleting the non-prod instance?
2. If we delete the non-prod instance, I am expecting to see "1 non-prod instances are available", and "1 prod instance is available" - is this right?
3. The next step would be to de-active FDI from this tenancy. What are the steps?
4. Finally, we need to locate that welcome email and activate FDI again in the right tenancy. Is this right? We should still be able to use the FDI license there, correct?

Thanks,

Sushanta

Sumanth V -Oracle

@Sushanta Chakraborty-Oracle -

Please find the answers inline below:

1. How to De-Provision the Non-Prod Instance?
→ Deleting the non-prod instance should be sufficient.

2. Expected Behavior After Deleting the Non-Prod Instance
Once you delete the non-prod instance, the availability should reset, and you should see:

• 1 Non-Prod instance available
• 1 Prod instance available

This will allow you to provision FDI in the correct tenancy.

3. Steps to Deactivate FDI from the Wrong Tenancy
To fully remove FDI from the wrong tenancy, follow these steps:

• Go to Fusion Data Intelligence Instances in OCI.
• Ensure that all instances are deleted.
• Remove any associated IAM roles, policies, and application roles that were created for FDI.

4. Activating FDI in the Correct Tenancy
After deactivating FDI in the wrong tenancy, follow these steps to activate it in the correct one:

• Find the welcome email that was sent when FDI was first provisioned.
• Use the activation link provided in the email to set up FDI in the correct tenancy.
• If the email is lost, you may need to contact Oracle Sales to request a new activation email.

5. Can You Reuse the FDI License?
Yes, the FDI license remains valid. Since no instances are running in the wrong tenancy, you should be able to provision FDI in the correct tenancy using the same license.