Troubleshooting Rapid Clone issues with Oracle Applications R12.0 & R12.1
(Doc ID 603104.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle E-Business Suite Technology Stack - Version 12.1.3 to 12.1.3 [Release 12.1]Oracle Applications Manager - Version 12.0 to 12.0.6 [Release 12]
Information in this document applies to any platform.
Purpose
This troubleshooting note is intended as a guide to help determine the cause of some problems that may arise during a Rapid Clone of E-Business Suite Release 12.0. & R12.1
For issues with 11i, please refer to <Note 364565.1> - 'Troubleshooting Rapid Clone issues with Oracle Applications 11i'
This Note is NOT a replacement for <Note 406982.1>.
<Note 406982.1> - 'Cloning Oracle Applications Release 12 with Rapid Clone' must be followed when performing a clone of Oracle Applications R12.
The idea is to provide a detailed explanation into what each step is trying to achieve making it easier to identify which part of the clone has failed and why.
Locations of log files are listed in Section 1, and are explained in each section. These should be uploaded when reporting a cloning issue to Oracle Support.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| Section 1: Cloning log files required by Support |
| Section 2: Different Components |
| Section 3: Before starting to clone |
| Section 4: Preparing the Source System |
| - Section 4a: Preparing the Source System - Database Tier |
| - Section 4b: Preparing the Source System - Applications Tier |
| - Section 4c: The "Clone Stage" area |
| Section 5: Copying the Source System to the Target System |
| Section 6: Configuring the Target System |
| - Section 6a: Configuring the Target System - Database Tier |
| - Section 6b: Configuring the Target System - Application Tier |
| Section 7: Inventory Registration |
| Section 8: Common Issues when cloning the Database Tier |
| How to prevent DB recovery issues when running adcfgclone |
| Troubleshooting DB recovery issues while running adcfgclone |
| Section 9: Known issues |
| - Some files and symbolic links still contain references to the source system |
| - Cloning fails at 50% with RC-00118 or RC-50004 after creating control files |
| - adcfgclone.pl appsTier fails with "ERROR: OUI files not found at their expected location" |
| - ouicli.pl fails with: "NON-COMPLIANT: <$ORACLE_HOME>/oraInst.loc does not point to an inventory inside the current ORACLE_HOME" or or "Timed out( 3750000 ): Interrupted Exception" |
| - adrelink.sh fails after cloning due to missing PRODUCT_TOP library files |
| - RC-50004: Fatal: Error occurred in ApplyAppsTechStack: |
| - RC-50013: Fatal: Failed to instantiate driver <10.1.2 ORACLE_HOME>/appsutil/driver/regclone.drv |
| - Application Tier clone fails with RC-50004 when Database Tier is in different domain |
| - 11.1.0.6 Database Tier clone fails with adlnkoh.sh on 64bit machines |
| - CloneContext.log shows "Hot Clone Mode Detected" in when not using "HotClone" |
| References |