Cloning OAS 10.1.3 SOA - Configuration Files Not Updated With New DB Connection Details

(Doc ID 744590.1)

Last updated on JULY 29, 2017

Applies to:

Oracle Fusion Middleware - Version to [Release AS10gR3]
Information in this document applies to any platform.


When cloning an Oracle Application Server 10g Release 3 ( 10.1.3 ) SOA Suite instance,  a new database and connect string are given in the clone script, but the cloning script does not pick up the new DB connection details.

Example parameters passed to

perl ORACLE_HOME=/myoraclehome \
ORACLE_HOME_NAME=mybpelinstall \
-instance mybpelinstance \
-db_vendor oracle \
-db_user SYS \
-db_password xxxxxxx \
-db_string mydbhost2:1521 \
-db_sid MYBPELDB2 \
-oc4jadmin_old_password xxxxxxx \
-oc4jadmin_new_password yyyyyyy

The values for -db_string and -db_sid are not the same database that is used by the source installation.

The clone script completes successfully, but the new database information is not reflected in any of the configuration files of the clone.

This is a list of the files under the cloned ORACLE_HOME that still contain the old ORACLE_SID. 

./bpel/system/services/install/config/data-sources_oracle_fragment.xml ./bpel/system/services/install/ant-tasks/ ./bpel/system/services/install/ant-tasks/



Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms