# Oracle EBS Rapid Clone Checklist > Source: https://netray.co/tools/oracle-ebs-rapid-clone-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step-by-step checklist for cloning an EBS instance with Rapid Clone, including the post-clone scrubbing that protects production data and integrations. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - Oracle EBS DBA - Oracle apps administrator - Release manager ## Tool **Kind:** checklist **Groups:** #### Plan and prepare the source **Items:** **Text:** Agree the clone request: source, target, date, who approves, and data scrubbing required **Critical:** true Confirm the target has enough disk space for database, application tier and staging Check Rapid Clone patch level on source against the current Oracle recommendation in My Oracle Support Confirm the target OS, Oracle home versions and kernel settings match the source requirements Record the current source patch level and customizations list for later comparison **Text:** Ensure the source has a valid, recent database backup before starting **Critical:** true Notify users and integration owners of the clone window **Text:** Run adpreclone.pl dbTier on the source database node as the database owner **Critical:** true **Text:** Run adpreclone.pl appsTier on the source application node as the application owner **Critical:** true #### Copy and restore **Items:** **Text:** Create a consistent copy of the source database via RMAN duplicate, backup restore or cold copy **Critical:** true Copy the application tier file system to the target nodes, including the non-editioned and shared areas Verify file ownership and permissions on the target **Text:** Confirm no process on the target can reach production endpoints before configuration runs **Critical:** true #### Configure the target **Items:** **Text:** Run adcfgclone.pl dbTier on the target database node and answer the prompts accurately **Critical:** true Check the database opens and listener registers with the new SID or service **Text:** Run adcfgclone.pl appsTier on the target application node **Critical:** true For Release 12.2, confirm the dual file system choice and the run and patch file systems Confirm the context file shows the correct host names, ports and domain Run AutoConfig on the database tier then the application tier and check for errors Start the application services and confirm the Apache, Forms and Oracle WebLogic components are up #### Post-clone scrubbing **Items:** **Text:** Run fnd_conc_clone.setup_clean as APPS to clear old node and manager information **Critical:** true Run AutoConfig again so nodes register correctly after the setup_clean step **Text:** Disable or redirect outbound email so test users and suppliers do not receive mail **Critical:** true **Text:** Set the Workflow mailer to a test address or leave it stopped **Critical:** true Change the SITENAME profile option so users see this is not production Update APPS_WEB_AGENT, APPS_SERVLET_AGENT and related profile URLs **Text:** Change the SYSADMIN, APPS and other privileged passwords using FNDCPASS or the supported method **Critical:** true **Text:** Cancel or hold scheduled concurrent requests inherited from production **Critical:** true **Text:** Repoint or disable integrations: EDI, banks, payment files, tax engines, middleware **Critical:** true **Text:** Mask or remove sensitive data such as bank accounts, tax IDs and personal data as policy requires **Critical:** true Reset printers and output post processor settings #### Verify and hand over **Items:** Log in as a normal user and open Forms and self-service pages Submit a standard concurrent request such as Active Users and confirm it completes Confirm concurrent managers are running with the expected processes Run adop -status for 12.2 and confirm there is no pending patching cycle Compare invalid objects count to the source and recompile where needed Run the key business smoke tests agreed with the finance and supply chain owners Document the clone, record the date of data and hand over to testers **Scoring Note:** Mark every item before releasing the environment. Items flagged critical protect production data and integrations, so none should be skipped. Commands and options vary by release and patch level, so use the current Oracle cloning documents on My Oracle Support for exact syntax. ## Content **Intro:** A clone is routine until an unscrubbed test instance emails real suppliers or submits a bank file. This checklist walks through Rapid Clone from preparation to the post-clone steps people forget. **Sections:** #### How to use the checklist **Body:** Work from top to bottom and tick items as you go. Group one covers the source preparation and the adpreclone step, group two the copy, group three the adcfgclone configuration, group four the scrubbing of data and integrations, and group five verification. Export the completed list as evidence for your change record. **Bullets:** - Critical items protect production data and partners - Keep the same order on every clone for repeatability - Attach the export to the change ticket #### What Rapid Clone does **Body:** adpreclone.pl prepares the source by creating templates and information the target needs, one run for the database tier and one for the application tier. After you copy the files, adcfgclone.pl on the target rebuilds the context files and configures the environment, with separate calls for dbTier and appsTier. It uses AutoConfig to apply the new host names and ports. Cloning copies data, so any scrubbing must be an explicit step after configuration. #### Why the scrub matters **Body:** A cloned instance contains production email addresses, supplier bank accounts, scheduled concurrent requests and integration endpoints. If the Workflow mailer starts, notifications reach real people. If a scheduled payment request runs, a file may be sent to a bank. Treat the post-clone group as mandatory and complete it before opening the instance to users. #### Common mistakes **Body:** Skipping fnd_conc_clone.setup_clean leaves old node entries that stop managers from starting. Forgetting to change passwords leaves test with production credentials. Not recording the data date makes testers argue about missing transactions. In 12.2, forgetting the file system state means the first patching cycle can fail. **Cta:** Netray can help you script and verify the post-clone scrub so every refresh is identical, and keep test data private on your own servers. **Faq:** #### What is the difference between adpreclone and adcfgclone? **Answer:** adpreclone.pl runs on the source to prepare it for copying. adcfgclone.pl runs on the target after the copy to configure the cloned file system and database with the new host and ports. Each has separate runs for the database and application tiers. #### Why run fnd_conc_clone.setup_clean? **Answer:** It clears node and concurrent processing information inherited from the source, such as old FND_NODES entries, so the target registers its own nodes after AutoConfig. Skipping it often leaves managers that cannot start. #### Do I need to change the APPS password after a clone? **Answer:** Yes, if policy says test and production must not share credentials, which is the usual rule. Use the supported FNDCPASS or the documented method and update the context files so AutoConfig stays consistent. #### How long does an EBS clone take? **Answer:** From a few hours to more than a day. The time depends on database size, copy method, network and storage, and on how much scrubbing and verification you do. Plan the window from your own past clones. ## Search terms oracle ebs clone checklist, adcfgclone.pl steps, adpreclone.pl dbTier appsTier, oracle ebs post clone steps, oracle apps rapid clone, oracle ebs refresh test from production, fnd_conc_clone.setup_clean, oracle ebs 12.2 clone dual file system --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json