3.Cloning Errors,Considerations and Limitations

3.1   Recovering from Cloning Errors

            While executing the pasteBinary or pasteConfig scripts with incorrect information in
            the move plan, the scripts return an error. In some cases, the scripts may have
            partially completed the paste operation. To recover, take the following actions,
            depending on the script that returned the error:

1.       If the pasteBinary script returns an error during cloning the Middleware home directory at the target:

·         Delete the target Middleware home.

·         Remove the Oracle home entry from the Oracle inventory, if it is present.

·         For Windows, remove the shortcut for the Middleware home and Oracle home.

2.       If the pasteConfig script returns an error during cloning Java components:

·         Stop all processes related to the domain.

·         Delete the following directories:

·         MW_HOME/user_projects/domains/domain_home

·         MW_HOME/user_projects/applications/domain_name

·         Drop the schemas and recreate them using RCU.

In addition, if the Oracle Platform Security reassociation failed:

§  For an LDAP store, delete the domain node or specify a different value in the move plan.

§  For a database-based store, drop the schema and recreate it using RCU.

3.       If the pasteConfig script returns an error during cloning system components:

·         Deinstall the instance.

·         If you cannot deinstall the instance, stop all processes related to that instance and delete the Oracle instance.

3.2   Considerations and Limitations for Cloning

            Important additional considerations about cloning:

1.       Cloning does not carry over all the dependencies of the source Middleware home, WebLogic Server home, and Oracle homes, such as loadable modules or application-specific libraries to the cloned home, because cloning proceeds by copying the Middleware home and the entire source WebLogic Server home and Oracle homes to the destination Middleware home. Any files outside the source WebLogic Server or Oracle home are not automatically copied. Hence, any applications that refer to files outside the source WebLogic Server or Oracle home may not work properly in the cloned home.

The Oracle home cloned as a part of the Middleware home contains only the binary files.

2.       When you clone a Middleware home, only the read-only portions of the Middleware home are cloned. Any user configuration files, such as the user_projects directory, are excluded from the cloned image. The WebLogic Server domain is not cloned.

3.       One must ensure that components, such as Oracle WebLogic Server and Oracle Coherence, are installed in the directory structure of the source Middleware home.

4.       One cannot clone a Middleware Home if its path is a symbolic link.

5.       If one has created symbolic links to files or applications outside the source WebLogic Server or Oracle home, you must re-create the link manually in the cloned home for your applications to work properly.

6.       If anyone applying the clone of a Middleware home on a host that does not yet have Oracle Fusion Middleware installed, the host must have JDK 1.6.04 or higher installed. In addition, the PATH, CLASSPATH, and JAVA_HOME environment variables must point to the JDK.

7.       If a custom application uses an internal data source (for example, the application was created and deployed with an internal data source using JDeveloper), the internal data source is not migrated during the clone operation.
Note**:
To work around this, create an external data source in the domain, modify the application to use that data source, and deploy the application again.

8.       If an Oracle Internet Directory component is cloned with the same database credentials as the source component, the name of the cloned OID component should be different than the source component to avoid conflicts in the OID schema.

9.       If an Oracle Internet Directory component is cloned with different database credentials from the source component, the name of the cloned Oracle Internet Directory component should be the same as the source component to avoid conflicts in the OID schema.

10.    You cannot clone Oracle Directory Integration Platform and Oracle Directory Service Manager. You must install them on the target.

11.    Cloning the AIA environment is not supported. You can clone the SOA that you want to use for AIA, but you must reinstall AIA on that instance for it to work properly (reference).

12.    If there is not enough space in the temporary directory when you are cloning an entity, an error is returned, noting the space needed. To work around this problem, specify a different location for the temporary directory by using the T2P_JAVA_OPTIONS environment variable as described below:

On Linux or UNIX:
    setenv T2P_JAVA_OPTIONS "-Djava.io.tmpdir=/home/t2p/temp"
    export T2P_JAVA_OPTIONS