Oracle EBS Instance Clone Request Template
A clone is routine for a DBA but risky for everyone else: it can overwrite test data, send real emails from the wrong system, or expose production data. This request form makes the scope, timing, data handling and post-clone steps explicit before the work starts.
Fill in
Oracle EBS Instance Clone Request Template
Instance Clone Request
Requested by: Tom Alvarez Date: 2026-10-20 EBS release: 12.2.x
Scope
Source instance: PROD Target instance: TEST Source data point: RMAN backup of 2026-10-18 02:00 Requested window: 2026-10-24 18:00 to 2026-10-25 06:00 Reason: Refresh TEST with current production data before the quarterly patch cycle regression test.
Data protection
Data scrambling: Yes, scramble personal and bank data If production data lands in a lower instance, access to the target must match production controls.
Preserve on target
Profile options for URLs and printers, custom integrations endpoints, test user accounts, concurrent manager node setup.
Post-clone activities
| Activity | Owner | Done |
|---|---|---|
| Run adcfgclone and confirm services start | DBA | |
| Reset APPS and application passwords | DBA | |
| Update site name, URLs and profile options | DBA | |
| Disable or repoint outbound integrations and email | Integration lead | |
| Cancel scheduled concurrent requests that must not run | DBA | |
| Reapply preserved settings and test users | Functional lead | |
| Smoke test login, a report and one transaction | Tester |
Approvals
Outline only. Follow Oracle's cloning documentation for your exact release, since the 12.2 online patching file system and the preclone and clone steps differ from 12.1. Check licensing and data privacy rules before copying production data.
Reduce the need for production copies
Optional discussion of private on-prem AI that works on controlled ERP data instead of full test copies.
Optional. The tool and every export work without this. No spam.
How to use the form
The requester fills the source, target, data point and window. The DBA adds the technical notes, and the owners of both instances sign. Export to PDF or Word and attach it to the change request. The preserve field matters most: list anything on the target that must survive the refresh, because a clone replaces the target database with the source copy.
What a clone involves
In broad terms, the source is prepared with a pre-clone step, the database and application file system are copied or restored, and the target is configured with the clone utilities, such as adcfgclone.pl, using the new host and instance values. After that the post-clone tasks reset passwords, profile options, workflow mailer settings and integrations. In 12.2 the dual file system adds steps, so use the release specific notes from Oracle.
- Confirm backup validity before overwriting the target
- Plan the outage window for the target users
- Disable outbound email and integrations early
- Record the clone date for audits
Common mistakes
The costliest mistakes are customers receiving emails from a test system, scheduled requests that post transactions to real partners, and unscrambled personal data left accessible to a wide test team. Others are forgetting to repoint the workflow notification mailer and losing test user set up. A written post-clone list, signed off, prevents most of these.
Frequently Asked Questions
What is Rapid Clone in Oracle EBS?
Rapid Clone is Oracle's supported utility set for copying an EBS environment to another host or instance. It prepares the source and reconfigures the copy using tools such as adpreclone.pl and adcfgclone.pl. Always follow the guide for your release.
What must be done after cloning EBS?
Typical steps include resetting passwords, updating profile options and site URLs, pointing integrations and email to test endpoints, cancelling scheduled requests, and configuring workflow mailers. Use a signed post-clone checklist for repeatability.
Should production data be scrambled in test?
Often yes, especially personal, bank and payroll data. Scrambling reduces privacy and compliance exposure, though it needs care to keep referential integrity. Follow your data protection policy and applicable law.
How long does an EBS clone take?
It depends on database size, storage and network speed, and ranges from several hours to more than a day for large systems. Plan the window with the DBA based on your last clone, not on a generic figure.
If clones and refreshes consume your DBA time, we can discuss a private, read-only AI layer that avoids copying production data to run analysis. Happy to explain.
Related Tools
Oracle EBS Profile Option Change Log Worksheet
Track every profile option change with its level, old and new value, reason and approver, so clones, upgrades and audits stop being guesswork.
OracleOracle EBS Tablespace Growth Forecast Calculator
Project compound growth of an EBS tablespace or database, find when it crosses an alert threshold and how much storage to add.
OracleOracle EBS User Access Review Template
A periodic access review record for EBS users and responsibilities, with scope, evidence, exceptions and reviewer sign-off.
OracleOracle EBS Custom Code Inventory Worksheet
Catalog reports, interfaces, conversions, extensions and forms with a disposition and effort estimate so you can size an EBS upgrade or retirement.
More Oracle tools
See all- Oracle EBS Inventory Tables Reference
- Oracle EBS WIP Tables Reference
- Oracle EBS Cycle Count Workload Calculator
- Oracle EBS Discrete Manufacturing Go-Live Checklist
- Oracle EBS Inventory Accuracy Readiness Assessment
- Oracle EBS Concurrent Request Phase and Status Reference
- Oracle EBS Responsibility Design Worksheet
- Oracle EBS GL Period Close Checklist
- Oracle EBS AP Invoice Interface Template