My Oracle Support Banner

Troubleshooting RAC RapidClone issues with Oracle Applications R12.0 & R12.1 (Doc ID 1303962.1)

Last updated on FEBRUARY 07, 2019

Applies to:

Oracle Applications Manager - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Oracle E-Business Suite Technology Stack - Version 12.0.6 to 12.1.3 [Release 12.0 to 12.1]
Oracle Applications DBA - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
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 the Database Tier phase only of cloning
E-Business Suite Release 12.0 & 12.1 with Real Application Clusters.

This Note is NOT a replacement for <Document 559518.1> - Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone.
That document must be followed when performing a clone of Oracle Applications R12 running on RAC.


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.

Note:  This Note does not cover 11.2.0 Grid specific functionality such as the SCAN listener.

This note only covers the Database Tier(s).

For the Application Tier, refer to <Document 603104.1> - Troubleshooting RapidClone issues with Oracle Applications R12.0 & R12.1.

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
 This note only covers the Database Tier(s).
Troubleshooting Steps
 This note only covers the Database Tier(s).
 Section 1: Cloning log files required by Support
 Source System log files
 Target System log files
 Section 2: Preparation - How it works
 Before starting to clone
 Copy and extract the appsutil.zip to the RDBMS ORACLE_HOME
 Run AutoConfig on the DB Tier
 Create Oracle Home Clone stage
 Check Archive Log mode
 Create Database Image
 Create Oracle Home Archive
 Section 3: Configuration - How it works
 About Non-RAC clone steps
 Extract Oracle Home Archive
 Create pairsfile.txt File for Primary Node
 Create Primary Node context file
 Configure the Target Primary Oracle Home
 Restore the Database (Primary node)
 1. First phase of RMAN restore
 2. Second phase of RMAN restore
 3. Third phase of RMAN restore
 4. Final DB Startup
 Clean FND tables and Topology Model
 Create pairsfile.txt File for Secondary Node(s)
 Create Secondary Node context file
 Configure the Target Secondary Oracle Home(s)
 AutoConfig
 Section 4: Known Issues
 a) Final DB Startup fails if Flash Recovery is enabled
 Cause:
 Potential Solution/Workaround:
 b) On Secondary nodes, adclonectx.pl fails with Instance Number n used by host
 Cause:
 Solution:
 c) RAC to RAC : Inventory Registration still references the source cluster nodes
 Problem:
 Cause:
 Solution:
 d) RAC to non-RAC : Inventory Registration still contains the source cluster nodes
 Problem: RAC to non-RAC
 Cause:
 Solution:
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.