Adcfgclone AppsTier Failing During Clone Into When Source And Target Are On Same Host

Applies to:

Oracle Applications Manager – Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

E-Business Suite 12.2 Applications Manager, Rapidclone related issues

Cloning the applications tier fails with the following error:

SEVERE : Jan 12, 2015 6:26:12 AM – ERROR – CLONE-20372 Server port validation failed.
SEVERE : Jan 12, 2015 6:26:12 AM – CAUSE – CLONE-20372 Ports of following servers – oacore_server2(7226),forms_server2(7
426),oafm_server2(7626),forms-c4ws_server2(7826) – are not available.
SEVERE : Jan 12, 2015 6:26:12 AM – ACTION – CLONE-20372 Provide valid free ports.
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.

The command that fails is the following:

perl adcfgclone appsTier

This solution is applicable to the following scenarios:

  1. Cloning where target host is one of the source nodes and all services on target node are shutdown
  2. Cloning where target host is one of the source nodes and all services on target node are running
  3. Cloning on a target host where another cloned instance uses the same ports as the source system

Solution

To implement the solution test the following steps:

1. Shutdown the process which is blocking the port.

2. Retry instance clone steps and ensure that env variable T2P_JAVA_OPTIONS  is set before executing adcfgclone.pl on target.

   export T2P_JAVA_OPTIONS=”-Dt2p.temporary.port.range=5001-5050″

Note: The variable T2P_JAVA_OPTIONS is used to provide a temporary port range which can be used by T2P utilities while cloning WebLogic domain.

Depending on the number of servers certain free ports from the range provided will be used temporarily while creating the new instance.
This range should be set by user depending on their current port usage which can vary from user to user.3. Once the target Oracle E-Business Suite instance is created the process that was shutdown in step #1 can be brought up.

3. Once the target Oracle E-Business Suite instance is created the process that was shutdown in step #1 can be restarted.

 

Recent Posts