|
# |
Step |
Estimated duration |
| 1. | Prepare the test machine (echo) that shall be used as the new production machine for cloning:Remove any existing E-Business Suite instance on the machine. Ideally, reinstall the operating system, apply any required service packs, install the additional software such as JDK, Visual C++, MKS Toolkit etc. The software should be installed to the same directory paths as those on the production instance.If the test machine will not reinstalled, then remove the Oracle-related keys from the registry. |
1 day |
| 2. | Carry out the pre-clone steps for the production instance (adpreclone.pl). |
½ day |
| 3. | Shutdown the production E-Business Suite instance (application and database tier services) and copy the files from the production machine (delta) to the test machine (echo). |
1 day |
| 4. | Disconnect the production server from the network. Change the name and IP address of the test machine (echo) to that of the production machine (delta). Update the ‘hosts’ file on the new production server, so that it now contains the new IP address and hostname. |
1 hour |
| 5. | Clone the new production server. Run the clone scripts on the new production server (adcfgclone.pl). |
½ day |
| 6. | Perform stress-testing of the new server to ensure that it responds suitably to the load. |
1 day |
| 7. | Backup and test recovery of the instance on another server. |
1 day |
Please note:
1. Ensure that the Database processes are properly shut down before proceeding to copy the files; if files aren’t copied correctly, the cloning process would not be executed correctly.
2. Do not run the Gather Schema Statistics concurrent job on the new PROD instance.
0 Comments.