What you will learn
Copying an Oracle home copies software, not a recoverable database. The old notes used archive copies and clone.pl. This 19c lesson uses the installer image workflow and keeps database activation separate from installation.
Before you begin
Use an isolated Oracle Database 19c Linux lab with a certified patch level. Names host1.sample.com and host2.sample.com identify distinct lab hosts; replace them consistently with your own addresses. Use oracle for database software and grid for Grid Infrastructure where ownership is separated. Connect through local operating-system authentication or a configured wallet; no example includes a password. Preserve a tested backup and record the database identity before changes. Prepare a tested Linux source home, compatible destination, empty destination directory, staging capacity, and an approved response file for silent installation if used. This database-home procedure does not apply to Grid Infrastructure.
1. Record the source baseline
"$ORACLE_HOME/OPatch/opatch" lsinventory
"$ORACLE_HOME/bin/sqlplus" -v
df -h /u02/stage
Record ownership, operating-system prerequisites, and deployment type. Review the home for secrets and host-specific artifacts. A copied password file is not an appropriate credential-provisioning mechanism.
2. Generate an installer image
cd "$ORACLE_HOME"
./runInstaller -createGoldImage -destinationLocation /u02/stage
Read the output to identify the generated image. Verify successful completion and record a checksum for that exact file. Use documented exclusions; do not assume an archive with permission errors is complete.
3. Install at the destination
Transfer the approved image to host2.sample.com and verify its checksum. Extract into the designated empty home and run its installer using the correct software-only single-instance or RAC configuration. Complete prerequisite checks and privileged scripts when instructed. Then set ORACLE_HOME to the destination and inspect:
"$ORACLE_HOME/OPatch/opatch" lsinventory
"$ORACLE_HOME/bin/sqlplus" -v
For RAC inspect every intended node. Installer registration is required; copying files and editing inventory node lists are not interchangeable with installation.
4. Plan activation separately
Compare patch inventories and installer logs, then validate network settings and wallets. Repointing a database requires its own tested patch or upgrade procedure. Starting it from another home can require database-side changes, even when the files look similar.
5. Read the example output
The following is illustrative, normalized output, not a transcript from a customer system. Values depend on your release and lab state.
Image creation: successful
Transferred checksum: matches
Destination inventory: registered
Expected patches: present
Database home switch: not performed
Matching directory sizes alone cannot establish a valid installation.
Verify the result
Confirm installer and inventory agree on the same absolute home and expected software level on all required nodes. Retain the checksum with the installation log.
Troubleshooting
Investigate imaging permission failures instead of assuming root scripts recreate every missing file. Registration failures can leave a usable-looking but incomplete installation. Resolve ownership and inventory pointers through the supported installer workflow.
Recovery and next steps
Keep the active home unchanged. If provisioning fails, retain logs and use documented cleanup for that destination only. Home activation and rollback are separate from image creation.