Oracle EBS Clone Checklist (adcfgclone)

0%

0 of 38 items complete

15 critical items still open - these are the highest-risk gaps.

Download checklist:

Plan and prepare the source

Agree the clone request: source, target, date, who approves, and data scrubbing requiredCRITICALConfirm the target has enough disk space for database, application tier and stagingCheck Rapid Clone patch level on source against the current Oracle recommendation in My Oracle SupportConfirm the target OS, Oracle home versions and kernel settings match the source requirementsRecord the current source patch level and customizations list for later comparisonEnsure the source has a valid, recent database backup before startingCRITICALNotify users and integration owners of the clone windowRun adpreclone.pl dbTier on the source database node as the database ownerCRITICALRun adpreclone.pl appsTier on the source application node as the application ownerCRITICAL

Copy and restore

Create a consistent copy of the source database via RMAN duplicate, backup restore or cold copyCRITICALCopy the application tier file system to the target nodes, including the non-editioned and shared areasVerify file ownership and permissions on the targetConfirm no process on the target can reach production endpoints before configuration runsCRITICAL

Configure the target

Run adcfgclone.pl dbTier on the target database node and answer the prompts accuratelyCRITICALCheck the database opens and listener registers with the new SID or serviceRun adcfgclone.pl appsTier on the target application nodeCRITICALFor Release 12.2, confirm the dual file system choice and the run and patch file systemsConfirm the context file shows the correct host names, ports and domainRun AutoConfig on the database tier then the application tier and check for errorsStart the application services and confirm the Apache, Forms and Oracle WebLogic components are up

Verify and hand over

Log in as a normal user and open Forms and self-service pagesSubmit a standard concurrent request such as Active Users and confirm it completesConfirm concurrent managers are running with the expected processesRun adop -status for 12.2 and confirm there is no pending patching cycleCompare invalid objects count to the source and recompile where neededRun the key business smoke tests agreed with the finance and supply chain ownersDocument the clone, record the date of data and hand over to testers

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.

Safe test data from production

Ask about masking and private AI testing on cloned EBS data that never leaves your network.

Optional. The tool and every export work without this. No spam.

How to use the checklist

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.

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

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

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

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.

Frequently Asked Questions

What is the difference between adpreclone and adcfgclone?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Oracle EBS Rapid Clone Checklist