Technology Stack - EBS (MOSC)

MOSC Banner

R12.2.4 : adop fails in a cloned environment

edited Jul 6, 2015 7:39PM in Technology Stack - EBS (MOSC) 1 commentAnswered

Hi ,

We cloned a R12.2.4 DEV envrionment from a TEST environment backup.   Cloning was successful.     we have 3 nodes

database - node1

concurrent manger/admin - node 2   (master)

web/forms - node 3 -  (slave).

However, adop -status is not reflecting correctly

adop -status

Enter the APPS password:

==============================================================
ADOP (C.Delta.6)
Session Id: 21
Command: status
Output: /u01/applmgr/fs_ne/EBSapps/log/status_20150706_151037/adzdshowstatus.out
===============================================================

Node Name       Node Type  Phase           Status          Started             Finished      Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
fin-dev-app-2   slave      FS_CLONE        FAILED          2015/06/25 04:14:14

File System Synchronization Type: Full

INFORMATION: Patching cycle aborted, so fs_clone will run automatically on fin-dev-app-2,fin-stage-app-1 nodes in prepare phase of next patching cycle.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center