Complete the prerequisites and then perform the following procedures.
Before initiating the cloning process, perform these steps to retrieve the schema names:
1. Log in to the Source Config Schema.
2. Execute the following query to retrieve the Config Schema name and Atomic Schema name:
select dbuserid from db_master;
In the expdp and impdp database utilities, you can use the schema names in the SCHEMAS attribute.
Subsequent steps for cloning are described in the subsections in this topic and Table 1 acts as a quick start with a summary view of the cloning process.
Table 1: Quick Start for Cloning
|
Sl. No. |
Cloning Process (click the links to go to the specific steps in the document) |
|
1. 1 |
Export the complete Configuration and Atomic Schemas from the source environment. |
|
2. 2 |
Restore the complete exported schema dumps into the target environment database. · Restore the complete exported schema dumps into the target environment database with a different database user name (schema). |
|
3. 3 |
Provide grants and set passwords using the SysDBA user login: 4. Provide the select grants permission on the sys.V_$parameter view to the Config and Atomic Schemas of the target environment database. 5. When you import into different schema names, set the passwords for the Config and Atomic Schemas of the target environment database the same as that of the password in the source. |
|
6. 4 |
Copy and restore the OFSAA file system. |
|
7. 5 |
Run the Port Changer utility. |
|
8. 6 |
Run the EncryptC.jar utility to change the key and encryption strings. |
|
9. 7 |
Perform the post-cloning configurations. |
|
10. 8 |
Create and deploy the .ear/.war files. |
|
11. 9 |
Access the UI. |