ATP DB Schema Rename

Summary:

I am seeking your expert advice on a significant change that we are planning to take. Could you kindly share any recommendations regarding the following scenario?

In the initial days of our project, we made the decision to implement two Autonomous Databases: one designated for production and the other for non-production purposes. The production database features a dedicated schema named XXPROD. In contrast, the non-production database comprises multiple schemas, such as XXDEV, XXTST, and XXUAT, which were established initially to facilitate segregation of environments. We use these schemas in Oracle Integration Cloud applications.

As we have progressed, we have encountered challenges associated with utilizing different schema names for different DBs. In light of these difficulties, we decided to introduce two additional databases to our infrastructure. This transition will allow us to allocate separate databases for each application, thereby eliminating the environment-specific schema names that were previously employed. Our objective is to establish a unified schema (something like XXAPP), across all databases, while ensuring that the database names reflect their respective environments.