Adoption to R12.1

Hi all

I understand online apply patches adoption-/ hotpatch is only available in R12.2.

It is available both in R12.1?

Kind regards

JC

Hello

adoption is a feature that is available from 12.2.

12.1, adpatch options = /hotpatch to apply patches without activating the maintenance mode, but is not recommended.

Kind regards

Hugues

Tags: Oracle Applications

Similar Questions

  • Apply the hotfix using ADOPTION in R12.2.4

    Hi all

    EBS R12.2.4

    OEL 6.5

    11 GR 2

    The consultant encoutered issue in the setup and asked me to apply the p18955265_R12 patch. HZ. C_R12_GENERIC.

    I want to apply this fix by using "adoption." I understand that in R12.2.4, you can not apply a patch using adpatch? but only adopt?

    Patch adoption cycles mentioned the following:

    Phases:

    adoption phase = prepare-> copy the code of the application

    adoption phase =-> apply patch in PATCH environment

    adoption phase = finalize-> makes it ready for the failover system

    adoption phase = failover-> bounce the transition to the system of system files and. FS2 becomes runtime environment.

    adoption phase = cleaning-> withdrawal of obsolete objects.

    adoption phase = fs_clone-> synchronize file systems

    Do I have to perform the steps above to apply the p18955265_R12 hotfix. HZ. C_R12_GENERIC?

    Thanks a lot for your kind cooperation.

    MK

    MariaKarpa (MK) wrote:

    Thanks hussein,.

    I think that these phases are carried out in complete sequence if you apply major patches as 12.2.2 12.2.3 and 12.2.4?

    Well, these phases are applicable to the 12.2.x

    Thank you

    Hussein

  • /Hotpatch adoption EBS R12.2 = yes

    Hi all

    When you apply /hotpatch in R12.2, do we still need backup applications first?

    For the reason that the patch could break the apps? Or /hotpatch can be rolledback?

    It is sometimes tideous a patch of 'small' 20KO must in order to stop the instance to support, so that it can be applied.

    It seems that it defeats / depletes the purpose of a /hotpatch

    Thank you very much

    JC

    I think that you put it back in the wrong direction. If the patch is small and you know that all files it will copy and rollback is easy, you don't need to take backup. And especially apply us patches in /hotpatch mode which just copy a few files here and there and don't do much structural change. It depends on the patches.

    concerning

    Pravin

  • How do I abort or kill or cancel suspended adoption patch run? (EBS R12.2.4)

    Hi all

    EBS R12.2.4

    OEL 6.5

    Check patches (adoption-status) without previous state, I applied a fix to help:

    phase of adoption $ = patch = 20059164 patchtop = / home/applcrp2/patch_for_application

    But I got the following error:

    Successful validation. All are called nodes are listed in the table ADOP_VALID_NODES.

    [EVENT]     [EARLY 2015/05/25 15:28:41] Mental health of high-performance database controls

    [EVENT]     [END 2015/05/25 15:28:41] Completed the database sanity checks

    [UNEXPECTED] Apply the phase cannot be performed in a fixed cycle, i.e. after prepare phase.

    Log file: /home/applcrp2/CRP2/fs_ne/EBSapps/log/adop/adop_20150525_152806.log

    [STATEMENT] Run adopscanlog utility, by using the command

    "adopscanlog-latest = yes".

    for a list of the log files as well as the snippet corresponding to each log file error message.

    adopted out with status = 2 (failure)


    I tried to run adoption-status and I discovered that there was previous patch hanging series

    How do I kill/clear/demolition and clean up the patch suspended?

    $ adop-status

    Enter the password for APPS:

    Current patch ID of Session: 7

    Name of node node Type Phase status started completed elapsed

    --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

    Master CRP2 PREPARE NOT APPLICABLE

    APPLY ASSETS 23 MARCH 15 13:15:35 + 08:00

    FINALIZE NOT APPLICABLE

    COMMISSIONING DON'T IS NOT APPLICABLE

    CLEANING NOT STARTED

    Folder synchronization system used in this Patching Cycle: None

    For more information, run ADOPTION Status Report using - option detail

    Generating the ADOPTION status report to the location: /home/applcrp2/CRP2/fs_ne/EBSapps/log/status_20150525_153549/adzdshowstatus.out

    Please wait...

    Done...!

    Help, please...

    Thank you very much

    MK

    Lol demolition Phase is not necessary.

    Don't run cleaning or if you want to apply another /hotpatch so you can continue with the current adoption session.

  • adoption of Patching EBS R12.2 error

    Hi all

    EBS R12.2.4

    RHEL6.6

    phase of adoption $ [appcrp@ip-10-0-0-216 MobileApps] = apply patches = 20049473 patchtop = / u01/MobileApps

    Enter the password for APPS:

    Enter the password:

    Enter the password for WLSADMIN:

    Please wait. Validating credentials...

    RUN the file system context: /u01/appcrp/CRP/fs1/inst/apps/CRP_ip-10-0-0-216/appl/admin/CRP_ip-10-0-0-216.xml

    Context file system PATCH file: /u01/appcrp/CRP/fs2/inst/apps/CRP_ip-10-0-0-216/appl/admin/CRP_ip-10-0-0-216.xml

    Run the SYSTEM command: / u01/appcrp/CRP/fs2 df

    Determination of worker of County...

    Successful validation. All are called nodes are listed in the table ADOP_VALID_NODES.

    [EVENT]     [EARLY 2015/03/20 19:29] Mental health of high-performance database controls

    [EVENT]     [END 2015/03/20 19:29] Completed the database sanity checks

    [UNEXPECTED] Apply the phase cannot be performed in a fixed cycle, i.e. after prepare phase.

    Log file: /u01/appcrp/CRP/fs_ne/EBSapps/log/adop/adop_20150320_192839.log

    [STATEMENT] Run adopscanlog utility, by using the command

    "adopscanlog-latest = yes".

    for a list of the log files as well as the snippet corresponding to each log file error message.

    adopted out with status = 2 (failure)

    [appcrp@ip-10-0-0-216 MobileApps] $ adopscanlog-latest = yes

    Analyzing the log u01/appcrp/CRP/fs_ne/EBSapps/log/adop/adop_20150320_192839.log file...

    /U01/appcrp/CRP/fs_ne/EBSapps/log/adop/adop_20150320_192839.log:

    ----------------------------------------------------------------

    #(27-31) lines:

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Staging of the current session

    [PROCEDURE] [END 2015/03/20 19:29:01] Staging of the current session

    [UNEXPECTED] Apply the phase cannot be performed in a fixed cycle, i.e. after prepare phase.

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Unlock sessions table

    [STATEMENT] Unlock ad_adop_sessions table for ip-10-0-0-216 with wait 60 seconds interval and number of tent 2

    =============

    [ec2-user@ip-10-0-0-216 ~] $ vi /u01/appcrp/CRP/fs_ne/EBSapps/log/adop/adop_20150320_192839.log

    Log file: /u01/appcrp/CRP/fs_ne/EBSapps/log/adop/adop_20150320_192839.log

    [EARLY 2015/03/20 19:28:40] Arguments passed to adoption

    phase = patch = 20049473 patchtop = / u01/MobileApps

    [END 2015/03/20 19:28:40] Arguments passed to adoption

    [EARLY 2015/03/20 19:28:40] Check the settings

    [END 2015/03/20 19:28:58] Check the settings

    [STATEMENT] Sourcing of the editing of run environment: /u01/appcrp/CRP/fs1/EBSapps/appl/APPSCRP_ip-10-0-0-216.env

    [EVENT]     [EARLY 2015/03/20 19:28:59] Verification of the requirements of ENV

    [EVENT]     [END 2015/03/20 19:29] Verification of the requirements of ENV

    [STATEMENT]  With the help of 4 workers (default: 4, recommended maximum limit: 62)

    [PROCEDURE] [EARLY 2015/03/20 19:29] Determine the admin node

    [STATEMENT] Node admin: "ip-10-0-0-216.

    [PROCEDURE] [END 2015/03/20 19:29] Determine the admin node

    Successful validation. All are called nodes are listed in the table ADOP_VALID_NODES.

    [EVENT]     [EARLY 2015/03/20 19:29] Mental health of high-performance database controls

    [EVENT]     [END 2015/03/20 19:29] Completed the database sanity checks

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Acquisition of a lock on the sessions table

    [STATEMENT] Locking ad_adop_sessions table for ip-10-0-0-216 with wait 60 seconds interval and the number of tent 2

    [PROCEDURE] [END 2015/03/20 19:29:01] Acquisition of a lock on the sessions table

    [EVENT]     [EARLY 2015/03/20 19:29:01] Check that the waiting for sessions

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Control assets /hotpatch session

    [STATEMENT] Fetch the number of incomplete cycles for ip-10-0-0-216 with appltop_id = 195.

    [STATEMENT] value of incomplete_session: "0".

    [PROCEDURE] [END 2015/03/20 19:29:01] Control assets /hotpatch session

    [STATEMENT] Master Session ID: UNDEFINED

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Staging of the current session

    [PROCEDURE] [END 2015/03/20 19:29:01] Staging of the current session

    [UNEXPECTED] Apply the phase cannot be performed in a fixed cycle, i.e. after prepare phase.

    [PROCEDURE] [EARLY 2015/03/20 19:29:01] Unlock sessions table

    [STATEMENT] Unlock ad_adop_sessions table for ip-10-0-0-216 with wait 60 seconds interval and number of tent 2

    [PROCEDURE] [END 2015/03/20 19:29:01] Unlock sessions table


    ==============


    [appcrp@ip-10-0-0-216 ~] $ adop-status

    Enter the password for APPS:

    Current patch ID of Session: 3

    Name of node node Type Phase status started completed elapsed

    --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

    CRP2 slave FS_CLONE COMPLETED 5 November 14 03:59:33 - 04:00 November 5, 14 04:54:56 - 04:00 0:55:23

    PREPARE NOT APPLICABLE

    APPLY NOT APPLICABLE

    COMMISSIONING DON'T IS NOT APPLICABLE

    CLEANING DON'T IS NOT APPLICABLE

    Folder synchronization system used in this Patching Cycle: full

    For more information, run ADOPTION Status Report using - option detail

    Generating the ADOPTION status report to the location: /u01/appcrp/CRP/fs_ne/EBSapps/log/status_20150320_194359/adzdshowstatus.out

    Please wait...

    Done...!

    Please see

    ORA-20001: unable to set editing ORA-06512: has the jump "APPS.ad_zd" job: egosdaci.sql on the appsad_zd build (Doc ID 1989739.1)

    https://support.Oracle.com/epmos/faces/PatchDetail?RequestId=18488991&_afrLoop=191137541272365&patchId=20183051%3AR12.ego.D&_afrWindowMode=0&_adf.CTRL-State=5jicoeb2j_165

    AppsMAsti
    sharing is caring

  • Error using patch R12.2 ADOPTION

    Hi guys,.

    The below error seems pretty obvious, but I am still unable to work on what is wrong... and ideas, please?  I'm under adoption to apply patch 17204589 for R12.2.0: CONSOLIDATED SEED TABLE UPGRADE PATCH.

    phase of adoption $ [oraappl@ebs1224 apps] = apply patches = /hotpatch 17204589 = yes

    Enter the password for APPS:

    Enter the password:

    Enter the password for WLSADMIN:

    Please wait. Validating credentials...

    Enter the file name of context to PERFORM file system [/ u04/oracle/VIS/fs1/inst/apps/VIS_ebs1224/appl/admin/VIS_ebs1224.xml]:

    [STATEMENT] [END 2014/09/17 04:54:59] Check the settings

    [STATEMENT] [BEGINNING 2014/09/17 04:55] Verification of the requirements of ENV

    [STATEMENT] [END 2014/09/17 04:55] Verification of the requirements of ENV

    Start of session *.

    version: 12.2.0

    starts at: Wed Sep 17-2014 04:55

    APPL_TOP is set to/u04/oracle/SCREWS/fs1/EBSapps/appl

    [STATEMENT] [BEGINNING 2014/09/17 04:55:01] Determine the admin node

    FATAL ERROR *.

    PROGRAM: (/ u04/oracle/VIS/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)

    TIME: Fri Sep 17 04:55:02 2014

    FUNCTION: TXK::IO:open [level 3]

    MESSAGES:

    error = cannot open file

    errorno = permission denied

    file = > > plus_Wed_Sep_17_04_55_02_2014_0340060363955BFDE0530100007FBD54.sql

    STACK TRACE

    in /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/Error.pm on line 168

    TXK::error:Abort ('TXK::Error', 'HASH (0x139b9fb8)') called at /U04/Oracle/vis/FS1/EBSapps/Appl/au/12.0.0/perl/TXK/Common.pm Line 299

    TXK::common:doError ('TXK:IO = HASH (0x14ecddf0)', 'HASH (0x147d3f48)', undef) called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/Common.pm line 314

    TXK::common:SetError ('TXK:IO = HASH (0x14ecddf0)', 'HASH (0x147d3f48)') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/IO.pm line 291

    TXK::IO:open ('TXK:IO = HASH (0x14ecddf0)', 'HASH (0x14ae2d80)') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/FileSys.pm line 854

    TXK::filesys:_processAccessList ('TXK:filesys = HASH (0x1545a740)', 'plus_Wed_Sep_17_04_55_02_2014_0340060363955BFDE0530100007FBD5... (', 10, 1) called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/FileSys.pm line 354

    TXK::filesys:create ('TXK:filesys = HASH (0x1545a740)', 'HASH (0x14ed35c0)') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/SQLPLUS.pm line 660

    TXK::sqlplus:_doExecute ('TXK:sqlplus = HASH (0 x 15205650)', 0) called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/SQLPLUS.pm line 234

    TXK::sqlplus:Execute ('TXK:sqlplus = HASH (0 x 15205650) ',' HASH (0x14dcffd0)') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/TechstackDB.pm line 618

    TXK::TechstackDB:_getSQLValue ('TXK:TechstackDB = HASH (0x154c47d8) ',' declare\x {a} begin\x {a} ad_zd_log.message(\'ad.bin.adop\ '...') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/TXK/TechstackDB.pm line 573

    TXK::TechstackDB:GetSqlValue ('TXK:TechstackDB = HASH (0x154c47d8) ',' declare\x {a} begin\x {a} ad_zd_log.message(\'ad.bin.adop\ '...') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/ADOP/Phase.pm line 262

    ADOP::phase:executeSQL ('ADOP:CommonBusinessRoutines = HASH(0x14547628) ',' declare\x {a} begin\x {a} ad_zd_log.message(\'ad.bin.adop\ '...') called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/ADOP/Phase.pm line 196

    ADOP::phase:LogMessage ('ADOP:CommonBusinessRoutines = HASH(0x14547628)', '[START] determination admin node', 1) called at /u04/oracle/VIS/fs1/EBSapps/appl/au/12.0.0/perl/ADOP/CommonBusinessRoutines.pm line 196

    ADOP::CommonBusinessRoutines:getAdminNode ('ADOP:CommonBusinessRoutines = HASH(0x14547628)') called at /u04/oracle/VIS/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl line 699

    Home:: adopMain() called at /u04/oracle/VIS/fs1/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl line 872

    adopted out with status = 13 (Fail)

    Thanks for the reply.  I have now moved this, but suspect I have has not correctly set permissions for group I was moving autour patches using the root.  Subsequent patches that I took care and chown, chgrp properly and they all went through fine.

  • Problem with fs_clone adoption after upgrade to R12.2.3 on the instance of SCREWS

    I installed instance EBS R12.2.0 Vision on Oracle Linux Server version 6.5 x 86-64 with Unbreakable Enterprise Kernel Module 3 (3.8.13 - 16.2.2.el6uek.x86_64) and then updated to R12.2.3.  Everything went smoothly with the initial installation, the AD and T2K patches and the adoption patch cycle to 12.2.3 update.  I'm having a problem with the fs_clone running, which is the first step of the subsequent update of doc 1586214.1.  The other phases of the adoption ran OK see below.  Also here is the error I get and you want to know if anyone has experienced this or ideas?  I searched google and MOS but couldn't find a direct hit.  I'm new to adoption and struggling to solve it... any help would be appreciated. I ran to the stage of fs_clone once or twice but I got the same result.

    adoption-status-detail (it is the cycle of update R12.2.3).  Every step seems OK here.

    Current patch ID of Session: 4

    Name of node node Type Phase status started completed elapsed
    --------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------
    HN-s-sb13 master PREPARE ENDED December 27, 13 09:27:31 - 05:00 27 December 13 09:55:35 - 05:00 0:28:04
    APPLY FULL 27 DECEMBER 13 10:11:53 - 05:00 27 DECEMBER 13 09:35:53 - 05:00 11:24
    FINALIZE ENDED 28 DECEMBER 13 09:28:46 - 05:00 DECEMBER 28, 13 09:29:52 - 05:00 0:01:06
    FAILOVER COMPLETED 28 DECEMBER 13 09:32:12 - 05:00 28 DECEMBER 13 10:05:35 - 05:00 0:33:23
    CLEANING ENDED 28 DECEMBER 13 10:25:22 - 05:00 28 DECEMBER 13 10:48:31 - 05:00 0:09:23


    Folder synchronization system used in this Patching Cycle: None
    Generate full ADOPTION status report to the location: /u01/oracle/VIS/fs_ne/EBSapps/log/status_20131229_120910/adzdshowstatus.out
    Please wait...
    Done...!

    adopted out with status = 0 (success)

    From txkADOPPreparePhaseSynchronize_Sat_Dec_28_12_40_05_2013.log:

    ---------------------------------------------------------------------------------------------

    ==========================
    SetCloneStatus() inside...
    ==========================

    Generation SQL file: /u01/oracle/VIS/fs_ne/EBSapps/log/adop/5/fs_clone_20131228_123623/VIS_hn-s-sb13/TXK_SYNC_create_Sat_Dec_28_12_40_05_2013/5_DEREGISTER-ORACLE-HOMES.sql
    SQL command: UPDATE ad_adop_session_patches SET clone_status = "cancel the REGISTRATION-ORACLE-HOMES ' WHERE State = ' no AND numero_de_bogue = 'CLONE' AND node_name = 'hn-s-sb13' AND adop_ses
    sion_id = 5;
    Run the SYSTEM command: sqlplus * @/ u01/oracle/SCREWS/fs_ne/EBSapps/log/adoption/5/fs_clone_20131228_123623/VIS_hn-s-sb13/TXK_SYNC_create_Sat_Dec_28_12_40_05_2013/5_DEREGI
    STER-ORACLE - HOMES.sql
    EXIT STATUS: 1
    SQL execution went through successfully.
    LOG FILE: / U01/ORACLE/SCREWS/FS_NE/EBSAPPS/LOG/ADOPTION/5/FS_CLONE_20131228_123623/VIS_HN-S-SB13/TXK_SYNC_CREATE_SAT_DEC_28_12_40_05_2013/5_DEREGISTER-ORACLE-HOMES. OUT.
    FATAL ERROR *.
    PROGRAM: (/ u01/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)
    TIME: Sat Dec 28 12:42:54 2013
    FUNCTION: main::runFSCloneApply [level 1]
    ERRORMSG: /u01/oracle/VIS/fs2/EBSapps/comn/clone/bin/adclone.pl does not pass successfully.

    From adop_20131228_123623.log:

    -----------------------------------------------

    ADOPTION Session ID: 5
    Phase: fs_clone
    [BEGINNING 2013/12/28 12:39:57] fs_clone phase
    [EVENT]     [BEGINNING 2013/12/28 12:40:01] Clone BY following the steps
    [EVENT]     [BEGINNING 2013/12/28 12:40:02] Patch CLONE of the file system to perform file system
    [EVENT]     The call: /u01/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
    [STATEMENT] Output directory: / u01/oracle/SCREWS/fs_ne/EBSapps/log/adoption/5/fs_clone_20131228_123623/VIS_hn-s-sb13
    [UNEXPECTED] Error occurred during execution of < perl /u01/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl - contextfile = / u01/oracl
    e/VIS/fs2/inst/apps/VIS_hn-s-sb13/appl/admin/VIS_hn-s-sb13.xml-patchcontextfile=/u01/oracle/VIS/fs1/inst/apps/VIS_hn-s-sb13/appl/admin/VIS_hn-s-sb13.xml - promptmsg = hide - co
    mark = off - mode = create - sessionid = 5 - timestamp = 20131228_123623 - outdir = / u01/oracle/SCREWS/fs_ne/EBSapps/log/adoption/5/fs_clone_20131228_123623/VIS_hn-s-sb13 >
    [UNEXPECTED] Error occurred while CLONE Patch File System to run file system using the command: perl /u01/oracle/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOP
    PreparePhaseSynchronize.pl-contextfile=/u01/oracle/VIS/fs2/inst/apps/VIS_hn-s-sb13/appl/admin/VIS_hn-s-sb13.xml - patchcontextfile = / u01/oracle/SCREWS/fs1/inst/apps/VIS_hn-s-sb1
    3/appl/Admin/VIS_hn-s-SB13.XML - promptmsg = hide - console = off - mode = create - sessionid = 5 - timestamp = 20131228_123623 - outdir = / u01/oracle/SCREWS/fs_ne/EBSapps/log/adoption/5/fs_clone_20
    131228_123623/VIS_hn-s-sb13 >.
    [PROCEDURE] [BEGINNING 2013/12/28 12:42:55] Check and stop Patch Server Admin
    [STATEMENT] select count (1) of ad_adop_session_patches
    where applied_file_system_base = ' / u01/oracle/SCREWS/fs2 ' and
    patch_file_system_base = ' / u01/oracle/SCREWS/fs1 "and
    numero_de_bogue IN ('CLONE', 'CONFIG_CLONE') and
    status (', 'F')

    [STATEMENT] There is a clone session waiting for/u01/oracle/SCREWS/fs1.
    [STATEMENT] Jumping to check and stop the Patch Server Admin step.
    [PROCEDURE] [END 2013/12/28 12:43:01] Check and stop Patch Server Admin
    [UNEXPECTED] fs_clone phase completed with errors/warnings. Check the log files
    [PROCEDURE] [BEGINNING 2013/12/28 12:43:03] Unlock sessions table
    [STATEMENT] SQL stmt: start
    AD_ZD_ADOP. UNLOCK_SESSIONS_TABLE('hn-s-sb13',60,2);
    end;
    >

    [PROCEDURE] [END 2013/12/28 12:43:07] Unlock sessions table
    Log file: /u01/oracle/VIS/fs_ne/EBSapps/log/adop/5/adop_20131228_123623.log

    Randy,

    Looks like you need to add more space to the directory/tmp, I see the following entries in the CLONE*.error file.

    CLONE2013-12-28_12-41-01 PM .error:

    =================================

    SEVERE: 28 December 2013 12:42:46 - ERROR - CLONE-20275 not enough space to create/tmp/CLONINGCLIENT8522798570339051663.

    SEVERE: 28 December 2013 12:42:46 - CAUSE - CLONE-20275 minimum required space was at '1 798' Mo, but only '1 737' MB was available for use.

    SEVERE: December 28, 2013 12:42:46 - ACTION - CLONE-20275, make sure that the minimum required space is available for use.

    GRAVE: 28 December 2013 12:42:46 - ERROR - CLONE-20233 restoration Middleware House for sourceid 'mwhome1@FMW_Home' failed.

    GRAVE: 28 December 2013 12:42:46 - CAUSE - CLONE-20233 an internal operation failed.

    Thank you

    Hussein

  • Correct way to run adoption patch cycle - EBS R12.2

    Hi all

    What is the right way to run the patch adoption cycle?

    $ . EBSapps.env < EBS_ROOT > run

    phase of adoption $ = prepare

    $ . patch EBSapps.env < EBS_ROOT >

    phase of adoption $ = apply patches = 123456

    phase of adoption $ = complete

    $ . EBSapps.env < EBS_ROOT > run

    $ Shutdown if apps run?

    phase of adoption $ = failover

    phase of adoption $ = cleaning

    Thank you all,

    JC

    I think these are the right steps for each phase.

    The last of them is not necessary that the synchronization will be performed the next time you run the preparation phase.

    Kind regards

    Bashar

  • adoption phase = prepare error R12.2

    Hello, I'm going to install a patch in 12.2 EBS server. LIVE demo version

    I use adoption. but initially when I'm in: adopted phase = prepare I got the I got an ERROR:

    error_adop_prepare.png

    Someone can help me.

    I have attached the log.

    Thank you!

    Hi . Bashar and Kj - Kiran jawad

    Finally, I found the solution.

    I checked anoter newspaper found in:

    / D01/Oracle/screws/fs_ne/EBSapps/log/adoption/4/fs_clone_20150520_105729/VIS_ebs122/TXK_SYNC_create_Wed_May_20_10_58_31_2015

    'CloneContext_FSCloneApplyAppsTier_05201058.log '.

    This log shows:

    Check if the EBS_LOGON trigger is enabled

    Disable the EBS_LOGON trigger.

    Fusion Middleware House value: / d01/oracle/SCREWS/fs2/FMW_Home

    Value of the Oracle Home tools: /d01/oracle/VIS/fs2/EBSapps/10.1.2

    Web Oracle Home value: / d01/oracle/SCREWS/fs2/FMW_Home/webtier

    Appl TOP value: / d01/oracle/SCREWS/fs2/EBSapps/appl

    COMMON HIGH value: / d01/oracle/SCREWS/fs2/EBSapps/comn

    Default Base instance: / d01/oracle/SCREWS

    srcJDKDirName = util/jdk32

    s_fmw_jdktop for the 64-bit platform is = / d01/oracle/SCREWS/fs2/EBSapps/comn/util/jdk64

    Determination of ConfigHome...

    ERROR: Could not clone the file of execution because of the following exception context:

    AC-00005: no write permission to create the folder context - /tmp/temp.xml

    Asked by oracle.apps.ad.context.AppsContext

    ERROR: Failed to clone the runtime context file to refresh the context of Patch file

    Then, the solution was in / tmp, the permissions:

    with the root user:

    chmod 777-r/tmp

    And now I can do: "adoption phase = prepare."

    Thanks for your help.

  • R12.2 Online help patch Failed

    We are modernizing EBS 11i to R12.2.4. and the following Oracle document Reference No.. E48834-15, we are in Chapter - 5, 'Applications technology missions ".

    6. install online help (recommended), pg no: 107.

    When applying on-line help patch get below error.

    phase of adoption $ = apply patchtop = $AU_TOP/patch/115 patches = driver: u10201000.drv options = nocopyportion, nogenerateportion, forceapply /hotpatch = yes

    Enter the password for APPS:

    Enter the password:

    Enter the password for WLSADMIN:

    Validation of credentials.

    During initialization.

    Run the editing context: /oracle_homes/archr12/fs2/inst/apps/ARCH_archapp1/appl/admin/ARCH_archapp1.xml

    Patch editing context: /oracle_homes/archr12/fs1/inst/apps/ARCH_archapp1/appl/admin/ARCH_archapp1.xml

    Driver file (up to 50000000 bytes).

    Free patch file system space: 65,66 GB

    Validate the configuration of the system.

    Registry node is valid.

    Audit of existing sessions of adoption.

    Continuing with the existing session [ID of Session: 17]

    [UNEXPECTED] Cannot use /hotpatch while a patchwork of existing cycle is running.

    [UNEXPECTED] Fatal error has occurred. Leaving current adoption session.

    [STATEMENT] Run adopscanlog utility, by using the command

    "adopscanlog-latest = yes".

    for a list of the log files as well as the snippet corresponding to each log file error message.

    adopted out with status = 2 (failure)

    Thank you

    Jeremy

    You try to apply the patch using /hotpatch option when a cycle existing adoption is ongoing. This is not allowed. Either you apply the patch to fix file system online help (phase of adoption fair use = apply patches =) or you can fill out/drop current patch cycle, then apply using /hotpatch.

  • adoption phase = failure of the commissioning

    Hi all

    EBS R12.2.4

    11 GR 2

    OL6.5

    I apply a patch and almost finished, until failover failed

    How can I fix this error?

    Thank you

    JC

    $ adop-status

    Enter the password for APPS:

    Current patch ID of Session: 9

    Name of node node Type Phase status started completed elapsed

    --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

    Master fitr12 PREPARED COMPLETE February 7, 16 16:51:38 + 08:00 February 7, 16 17:01:29 + 08:00 0:09:51

    APPLY DULY FILLED

    FINALIZE FILLED FEBRUARY 7, 16 17:35:53 + 08:00 FEBRUARY 7 16 17:36:05 + 08:00 0:00:12

    COMMISSIONING HAS NOT 7 FEBRUARY 16 17:35:47 + 08:00 FEBRUARY 7 16 17:50:08 + 08:00 0:14:21

    CLEANING NOT STARTED

    Folder synchronization system used in this Patching Cycle: light

    For more information, run ADOPTION Status Report using - option detail

    Generating the ADOPTION status report to the location: /u01/appvis/VIS/fs_ne/EBSapps/log/status_20160207_175725/adzdshowstatus.out

    $ adopscanlog-latest = yes

    Scan/directory/u01/appvis/SCREWS/fs_ne/EBSapps/log/adoption/9...

    /U01/appvis/vis/fs_ne/EBSapps/log/adop/9/adop_20160207_173516.log:

    ------------------------------------------------------------------

    #(244-248) lines:

    [STATEMENT] Sourcing of the Patch editing environment: /u01/appvis/VIS/fs1/EBSapps/appl/APPSVIS_fitr12.env

    [EVENT]     [EARLY 2016/02/07 17:46:30] Starting the Services of intermediate level

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /u01/appvis/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPCutOverPhaseCtrlScript.pl-contextfile=/u01/appvis/VIS/fs2/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml-patchcontextfile=/u01/appvis/VIS/fs1/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml - promptmsg = cacher - console = off - sessionid = 9 - timestamp = 20160207_173516 - outdir = / u01/appvis/VIS/fs_ne/EBSapps/journal/adop/9/cutover_20160207_173516/VIS_fitr12 - action = forcestartup »

    [UNEXPECTED] Implementation phase completed with errors/warnings. Check the log files

    [STATEMENT] Phase SHIFT END TIME: 02/07/2016-17:50:08

    #(245-249) lines:

    [EVENT]     [EARLY 2016/02/07 17:46:30] Starting the Services of intermediate level

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /u01/appvis/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPCutOverPhaseCtrlScript.pl-contextfile=/u01/appvis/VIS/fs2/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml-patchcontextfile=/u01/appvis/VIS/fs1/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml - promptmsg = cacher - console = off - sessionid = 9 - timestamp = 20160207_173516 - outdir = / u01/appvis/VIS/fs_ne/EBSapps/journal/adop/9/cutover_20160207_173516/VIS_fitr12 - action = forcestartup »

    [UNEXPECTED] Implementation phase completed with errors/warnings. Check the log files

    [STATEMENT] Phase SHIFT END TIME: 02/07/2016-17:50:08

    [PROCEDURE] [EARLY 2016/02/07 17:50:08] Unlock sessions table

    /U01/appvis/vis/fs_ne/EBSapps/log/adop/9/cutover_20160207_173516/VIS_fitr12/TXK_CTRL_forcestartup_Sun_Feb_7_17_46_31_2016/txkADOPCutOverPhaseCtrlScript_Sun_Feb_7_17_46_31_2016.log:

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    #(78-80) lines:

    TIME: Sun Feb 7 17:50:07 2016

    FUNCTION: main::forceStartupServices [level 1]


    FATAL ERROR *.

    PROGRAM: (/ u01/appvis/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPCutOverPhaseCtrlScript.pl)

    TIME: Sun Feb 7 17:50:07 2016

    FUNCTION: main::forceStartupServices [level 1]

    ERRORMSG: 1

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /u01/appvis/VIS/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPCutOverPhaseCtrlScript.pl-contextfile=/u01/appvis/VIS/fs2/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml-patchcontextfile=/u01/appvis/VIS/fs1/inst/apps/VIS_fitr12/appl/admin/VIS_fitr12.xml - promptmsg = cacher - console = off - sessionid = 9 - timestamp = 20160207_173516 - outdir = / u01/appvis/VIS/fs_ne/EBSapps/journal/adop/9/cutover_20160207_173516/VIS_fitr12 - action = forcestartup »

    [UNEXPECTED] Implementation phase completed with errors/warnings. Check the log files

    Log file: /u01/appvis/VIS/fs_ne/EBSapps/log/adop/9/adop_20160207_173516.log




    Hello Jenna.

    An alternative is to try "adoption phase = failover mtrestart = no" if we can confirm that the issue is w.r.t. starting services.

    Thus, the failover can be completed and starting the services can be looked in or fixed once the failover successfully completed.

    Kind regards

    Hugues

  • adoption phase = prepare failed

    Hi all

    EBS R12.2.4

    11 GR 2

    OL6.5

    I'm running adoption phase = prepare but I got error

    Please help how to solve problems.

    Thank you

    JC

    $ adop-status

    Enter the password for APPS:

    Current patch ID of Session: 7

    Name of node node Type Phase status started completed elapsed

    --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

    fitr12 master PREPARE failed February 3-16 15:12:58 + 08:00 February 3-16 15:16:09 + 08:00 0:03:11

    APPLY NOT STARTED

    FINALIZE NOT STARTED

    COMMISSIONING IS NOT STARTED

    CLEANING NOT STARTED

    Folder synchronization system used in this Patching Cycle: light

    $ adopscanlog-latest = yes

    Directory/scanning/u02/TEMP/appcrp/CRP/fs_ne/EBSapps/log/adoption/7...

    /U02/temp/appcrp/CRP/fs_ne/EBSapps/log/adop/7/adop_20160203_151059.log:

    -----------------------------------------------------------------------

    #(166-170) lines:

    [EVENT]     The call: /u01/appcrp/CRP/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl

    [STATEMENT] Output directory: / u01/appcrp/CRP/fs_ne/EBSapps/log/adoption/7/prepare_20160203_151059/CRP_fitr12

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /u01/appcrp/CRP/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl-contextfile=/u01/appcrp/CRP/fs1/inst/apps/CRP_fitr12/appl/admin/CRP_fitr12.xml-patchcontextfile=/u01/appcrp/CRP/fs2/inst/apps/CRP_fitr12/appl/admin/CRP_fitr12.xml - promptmsg = cacher - console = off - patchtop = / u01/appcrp/CRP/fs_ne/EBSapps/patch - mode = mise à jour - sessionid = 7 - timestamp = 20160203_151059 - workercount = 4 - outdir = / u01/appcrp/CRP/fs_ne/EBSapps/journal/adop/7/prepare_20160203_151059/CRP_ fitr12 - autoskip = no ".

    [UNEXPECTED] Error then that subroutine runSyncFS called

    [PROCEDURE] [EARLY 2016/02/03 15:15:57] Check and stop Patch Server Admin

    #(167-171) lines:

    [STATEMENT] Output directory: / u01/appcrp/CRP/fs_ne/EBSapps/log/adoption/7/prepare_20160203_151059/CRP_fitr12

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /u01/appcrp/CRP/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl-contextfile=/u01/appcrp/CRP/fs1/inst/apps/CRP_fitr12/appl/admin/CRP_fitr12.xml-patchcontextfile=/u01/appcrp/CRP/fs2/inst/apps/CRP_fitr12/appl/admin/CRP_fitr12.xml - promptmsg = cacher - console = off - patchtop = / u01/appcrp/CRP/fs_ne/EBSapps/patch - mode = mise à jour - sessionid = 7 - timestamp = 20160203_151059 - workercount = 4 - outdir = / u01/appcrp/CRP/fs_ne/EBSapps/journal/adop/7/prepare_20160203_151059/CRP_ fitr12 - autoskip = no ".

    [UNEXPECTED] Error then that subroutine runSyncFS called

    [PROCEDURE] [EARLY 2016/02/03 15:15:57] Check and stop Patch Server Admin

    [EVENT]     [EARLY 2016/02/03 15:15:58] Check and stop Patch FS Server Admin

    #(177-181) lines:

    [STATEMENT] Skip the check and Stop Patch Node Manager step.

    [PROCEDURE] [END 2016/02/03 15:16:09] Check and stop the Patch Node Manager

    [ERROR]     Prepare phase completed with errors or warnings. Check the log files.

    [STATEMENT] SQL statement: "update ad_adop_sessions".

    set status = 'F'

    /U02/temp/appcrp/CRP/fs_ne/EBSapps/log/adop/7/prepare_20160203_151059/CRP_fitr12/TXK_SYNC_update_Wed_Feb_3_15_15_38_2016/txkADOPPreparePhaseSynchronize_Wed_Feb_3_15_15_38_2016.log:

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    #(316-318) lines:

    TIME: Kills Feb 3 15:15:57 2016

    FUNCTION: main::validatePatchLocation [level 1]

    ERRORMSG: / u01/appcrp/CRP/fs_ne/EBSapps/patch/18955265 directory does not exist.

    I mean to the point where you have cloned the source environment.

    When clone you your source environment, which is your level of apps, / U01/U02.

    Why you have 2 level apps mount points.

    According to my understanding, this leads to confusion.

    Kind regards

    Hugues

  • adoption phase = error in prepare

    Hi all

    EBS r12.2.4

    oel6

    I apply a patch.

    I start by

    phase of adoption $ = prepare


    But I got error


    = START OF THE VALIDATION REPORT =.

    Results of the validation for node: crp2

    ---------------------------------------

    [ERROR]: value set to JDK_TOP (context variable s_jdktop) is not valid.

    [WARNING]: there may be problems when validating the ports used for the instance of the E-Business Suite with ports used in/etc/services. See the log file for more details.

    [ERROR]: some of the ports specified for the file system of the fix are not available.

    [WARNING]: some necessary entries in the file/etc/hosts may be absent (e.g. localhost, or the host name) OR the file/etc/hosts could not be read.

    Some validations failed, please visit /home/applcrp2/CRP2/fs_ne/EBSapps/log/adop/9/prepare_20150913_011329/CRP2_crp2/ADOPValidations_Sun_Sep_13_01_14_11_2015.log

    = END OF VALIDATION REPORT =.

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /home/applcrp2/CRP2/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl-contextfile=/home/applcrp2/CRP2/fs1/inst/apps/CRP2_crp2/appl/admin/CRP2_crp2.xml-patchctxfile=/home/applcrp2/CRP2/fs2/inst/apps/CRP2_crp2/appl/admin/CRP2_crp2.xml-phase = préparer - logloc = / home/applcrp2/CRP2/fs_ne/EBSapps/journal/adop/9/prepare_20150913_011329/CRP2_crp2 - promptmsg = cacher »

    [UNEXPECTED] Error 1 occurred while Executing txkADOPValidation script on crp2

    Log file: /home/applcrp2/CRP2/fs_ne/EBSapps/log/adop/9/adop_20150913_011329.log

    [STATEMENT] Run adopscanlog utility, by using the command

    "adopscanlog-latest = yes".

    for a list of the log files as well as the snippet corresponding to each log file error message.

    adopted out with status = 1 (failure)


    Help, please...


    Thank you very much

    JC

    Hello

    See "3. Controls related to S_JDKTOP and S_FMW_JDKTOP"in the following MOS: Oracle E-Business Suite Release 12.2: Validations performed by the adoption online Patching Utility (Doc ID 1678355.1)

    Coco - M

  • adoption apply phase failed. market to follow

    We are in the middle of the patching recommended on EBS R12.2.4 instance with 12.1.0.2.0 db. We conducted under activities up to now:

    adoption phase = prepare

    adoption phase = apply patches = 1

    adoption phase = patch = 2

    adoption phase = patch = 3

    .

    .

    .

    .

    .

    One of the patch failed:

    adoption phase = patch = 20592764

    We applied 30 patches up to now in adoption apply phase an and I still have to apply other hotfixes. Patch 20592764 failed due to incompatibility with the line of code R12.2 C.


    Error: AutoPatch error:
    --------
    This patch is not compatible with your current codelines.

    This patch is compatible with: "ad" - line of code entity ' R12. AD. B'.
    Your line of code on the current site for the entity 'ad' is: ' R12. AD. C

    It comes to the current state of the adoption:

    bash - $4.1 adop-status

    Enter the password for APPS:

    Current patch ID of Session: 75

    Name of node node Type Phase status started completed elapsed

    --------------- --------------- --------------- --------------- ------------------------------ ------------------------------ ------------

    appsnodex master PREPARE FINISHED 1st Aug 15 20:27:59-05:00 1 August 15 20:52:23 - 05:00 0:24:24

    APPLY THE FAILURE 1 AUG 15 20:57:48 - 05:00 2 AUGUST 15 05:05:53 - 05:00 08:08:05

    FINALIZE NOT STARTED

    COMMISSIONING IS NOT STARTED

    CLEANING NOT STARTED

    Folder synchronization system used in this Patching Cycle: full

    For more information, run ADOPTION Status Report using - option detail

    Generating the ADOPTION status report to the location: /dhdr2i/applmgr/fs_ne/EBSapps/log/status_20150802_072959/adzdshowstatus.out

    Please wait...

    Done...!

    adopted out with status = 0 (success)

    We do not use cancel that we already applied 30 patches and it will start the cycle from scratch. We are yet to apply the fixes over 40. Also several times giving up is leading to corruption of data dictionary in our case and a bug is already raised with Support from Oracle.
    We can use: adopted phase = apply restart no = no = yes patches abandonment = 20592764

    Please suggest how to proceed with patching. Now we're stuck.

    Concerning

    Purnima Johari

    I suggest you start with the next patch using the 'abandonment = yes"parameter.

    It seems that I forgot to mention that in my previous post!

    Furthermore, why apply AD. Delta.6 instead of delta.5?

    Kind regards

    Bashar

  • ADOPTION = fs_clone error

    I finally got Delta 6 running process.

    Apply process has been a success for

    Those who went fine.

    Then by:

    $ . EBSapps.env < EBS_ROOT > run
    phase adoption $ = complete
    phase adoption $ = failover
    $. EBSapps.env < EBS_ROOT > run
    phase adoption $ = cleaning

    Everything was fine.

    Now, do fs_clone, I see these errors:

    Allows the shutter EBS_LOGON

    ERROR when running FSCloneApply...

    Sat Apr 4 19:28:56 2015

    FATAL ERROR *.

    PROGRAM: (/ DATA/NFS_SHARE/D01/ORACLE/PROD/FS2/EBSAPPS/APPL/AD/12.0.0/PATCH/115/BIN/TXKADOPPREPAREPHASESYNCHRONIZE.PL)

    TIME: Sat Apr 4 19:28:56 2015

    FUNCTION: main::runFSCloneApply [level 1]

    ERRORMSG: /data/nfs_share/d01/oracle/PROD/fs2/EBSapps/comn/adopclone_ebswl/bin/adclone.pl does not pass successfully.

    [UNEXPECTED] Erreur s'est produite lors de l'exécution « perl /data/nfs_share/d01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl-contextfile=/data/nfs_share/d01/oracle/PROD/fs2/inst/apps/PROD_ebswl/appl/admin/PROD_ebswl.xml-patchcontextfile=/data/nfs_share/d01/oracle/PROD/fs1/inst/apps/PROD_ebswl/appl/admin/PROD_ebswl.xml - promptmsg = cacher - console = off - mode = créer - sessionid = 23 - timestamp = 20150704_190011 - outdir = / data/nfs_share/d01/oracle/PROD/fs_ne/EBSapps/journal/adop/23/fs_clone_20150704_190011 / PROD_ebswl ".

    [UNEXPECTED] Error occured while CLONE Patch File System de courir de système de fichiers à l'aide de la commande : « perl /data/nfs_share/d01/oracle/PROD/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl-contextfile=/data/nfs_share/d01/oracle/PROD/fs2/inst/apps/PROD_ebswl/appl/admin/PROD_ebswl.xml-patchcontextfile=/data/nfs_share/d01/oracle/PROD/fs1/inst/apps/PROD_ebswl/appl/admin/PROD_ebswl.xml - promptmsg = cacher - console = off - mode = créer - sessionid = 23 - timestamp = 20150704_190011 - outdir = / data/nfs_share/d01/ Oracle/PROD/fs_ not/EBSapps/log/adoption/23/fs_clone_20150704_190011/PROD_ebswl.

    Free managed servers ports...

    Journal: /data/nfs_share/d01/oracle/PROD/fs_ne/EBSapps/log/adop/23/fs_clone_20150704_190011/PROD_ebswl/txkCloneAcquirePort.log

    Stopping services on the patch file system...

    Stopping admin server...

    You are running version 120.10.12020000.2 adadminsrvctl.sh

    Environment file /data/nfs_share/d01/oracle/PROD/fs1/EBSapps/appl/APPSPROD_ebswl.env is not found.

    /Data/nfs_share/D01/Oracle/prod/FS1/inst/apps/PROD_ebswl/Admin/scripts/adadminsrvctl.sh: line 90: $LOGFILE: ambiguous redirect

    [UNEXPECTED] Error occurred while executing "/data/nfs_share/d01/oracle/PROD/fs1/inst/apps/PROD_ebswl/admin/scripts/adadminsrvctl.sh stop sh - nopromptmsg.

    [UNEXPECTED] Error running adadminsrvctl

    [STATEMENT] Run adopscanlog utility, by using the command

    "adopscanlog-latest = yes".

    for a list of the log files as well as the snippet corresponding to each log file error message.

    adopted out with status = 2 (failure)

    the FS_CLONE is not optional.  It needs to be fixed or if you rerun the PREPARATION phase, it will lift the same error.

    I've corrected that the error was related to the JRE.

    I copied the CLONE of FS_2 in FS_1 dir and then now CLONE FS completed successfully.

Maybe you are looking for