After long time I am updating my blog with R12.2.5 cloning.
There is a slight difference between R12.2.4 and R12.2.5.
With the introduction of dualfs in R12.2.5 we can even configure patch filesystem with single run of adcfgclone on the target node.
Here in the above picture, if run filesystem is on fs2 on the source then on the target also we should configure fs2 as run filesystem and automatically fs1 will become patch filesystem
we copy only EBSApps folder from source fs2 filesystem which is RUN filesystem, to target fs2 filesystem
NOTE: DO NOT COPY EBSApps folder from source fs2 run filesystem to target fs1 folder, this resulted in error.
IF FS2 FILESYSTEM IS RUN THEN WE SHOULD COPY SOURCE EBSApps FOLDER FROM FS2 of source TO TARGET FS2. THIS SHOULD BE DONE AFTER RUNNING adpreclone.pl ON SOURCE RUN FILESYSTEM.
[applcrp4@crp4app1 fs2]$ cd /d01/oracle/CRP1/fs1
[applcrp4@crp4app1 fs1]$ ls -l
drwxr-xr-x 5 applcrp4 dba 4096 Nov 6 04:49 EBSapps
[applcrp4@crp4app1 bin]$ perl adcfgclone.pl appsTier dualfs
Copyright (c) 2002, 2015 Oracle Corporation
Redwood Shores, California, USA
Oracle E-Business Suite Rapid Clone
adcfgclone Version 120.63.12020000.56
Enter the APPS password :
Enter the Weblogic AdminServer password :
Do you want to add a node (yes/no) [no] :
Running: Context clone...
Log file located at /d01/oracle/CRP1/fs2/EBSapps/comn/clone/bin/CloneContext_1116040449.log
Provide the values required for creation of the new APPL_TOP Context file.
Target System Hostname (virtual or normal) [crp4app1] :
Target System Database SID : CRP1
Target System Database Server Node [crp4app1] : crp4db1
Target System Database Domain Name [ora.ad] :
Target System Base Directory : /d01/oracle/CRP1
Target System Base Directory set to /d01/oracle/CRP1
Target System Current File System Base set to /d01/oracle/CRP1/fs2
Target System Other File System Base set to /d01/oracle/CRP1/fs1
Target System Fusion Middleware Home set to /d01/oracle/CRP1/fs2/FMW_Home
Target System Other File System Fusion Middleware Home set to /d01/oracle/CRP1/fs1/FMW_Home
Target System Web Oracle Home set to /d01/oracle/CRP1/fs2/FMW_Home/webtier
Target System Other File System Web Oracle Home set to /d01/oracle/CRP1/fs1/FMW_Home/webtier
Target System Appl TOP set to /d01/oracle/CRP1/fs2/EBSapps/appl
Target System Other File System Appl TOP set to /d01/oracle/CRP1/fs1/EBSapps/appl
Target System COMMON TOP set to /d01/oracle/CRP1/fs2/EBSapps/comn
Target System Other File System COMMON TOP set to /d01/oracle/CRP1/fs1/EBSapps/comn
Target System Instance Home Directory [/d01/oracle/CRP1] :
Target System Current File System Instance Top set to /d01/oracle/CRP1/fs2/inst/apps/d01_crp4app1
Do you want to preserve the Display [app-upg-app1:0.0] (y/n) : n
Target System Display [crp4app1:0.0] :
Target System Root Service [enabled] :
Target System Web Entry Point Services [enabled] :
Target System Web Application Services [enabled] :
Target System Batch Processing Services [enabled] :
Target System Other Services [disabled] : enabled
Do you want the target system to have the same port values as the source system (y/n) [y] ? : n
Target System Port Pool [0-99] : 0
Checking the port pool 0
done: Port Pool 0 is free
Report file located at /d01/oracle/CRP1/fs2/inst/apps/CRP1_crp4app1/admin/out/portpool.lst
UTL_FILE_DIR on database tier consists of the following directories.
Choose a value which will be set as APPLPTMP value on the target node  :
The new APPL_TOP context file has been created :
Check Clone Context logfile /d01/oracle/CRP1/fs2/EBSapps/comn/clone/bin/CloneContext_1116040449.log for details.
Creating Patch file system context file.....
Log file located at /d01/oracle/CRP1/fs2/EBSapps/comn/clone/bin/CloneContextPatch_1116040654.log
Target System Other File System Instance Top set to /d01/oracle/CRP1/fs1/inst/apps/CRP1_crp4app1
Target System Port Pool [0-99] : 1
Checking the port pool 1
done: Port Pool 1 is free
Report file located at /d01/oracle/CRP1/fs1/inst/apps/CRP1_crp4app1/admin/out/portpool.lst
The new APPL_TOP context file has been created :
Check Clone Context logfile /d01/oracle/CRP1/fs2/EBSapps/comn/clone/bin/CloneContextPatch_1116040654.log for details.
FMW Pre-requisite check log file location : /d01/oracle/CRP1/fs2/EBSapps/comn/clone/FMW/logs/prereqcheck.log
Running: FMW pre-req check...
Configuring: Run file system....
LogFile located at /d01/oracle/CRP1/fs2/inst/apps/CRP1_crp4app1/admin/log/clone/run/RCloneApplyAppstier_11160407.log
Configuring: Patch file system....
LogFile located at /d01/oracle/CRP1/fs2/inst/apps/CRP1_crp4app1/admin/log/clone/patch/RCloneApplyAppstier_11160433.log
Do you want to startup the Application Services for CRP1? (y/n) [n] : n
Services not started
In the proces of upgrading from R12.1.3 to R12.2.4. I encountered an issue with autoconfig on database side
Below is the excert from error log
afdbprf.sh started at Mon May 4 23:09:23 PDT 2015
The environment settings are as follows …
ORACLE_HOME : /dev/oracle/product/11.2.0
ORACLE_SID : dev
PATH : /dev/oracle/product/11.2.0/perl/bin:/dev/oracle/product/11.2.0/perl/bin:/dev/oracle/product/11.2.0/bin:/usr/bin:/usr/sbin:/dev/oracle/product/11.2.0/appsutil/jre/bin:/bin:/usr/bin/X11:/usr/local/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracrp1/bin:.
Library Path : /dev/oracle/product/11.2.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/dev/oracle/product/11.2.0/lib:/usr/dt/lib:/dev/oracle/product/11.2.0/ctx/lib
Executable : /dev/oracle/product/11.2.0/bin/sqlplus
SQL*Plus: Release 18.104.22.168.0 Production on Mon May 4 23:09:23 2015
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Enter value for 1: Enter value for 2: Enter value for 3: Connected.
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at “APPS.ADX_PRF_PKG”, line 83
ORA-01403: no data found
ORA-06512: at line 7
Disconnected from Oracle Database 11g Enterprise Edition Release 22.214.171.124.0 – 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ERRORCODE = 1 ERRORCODE_END
.end std out.
.end err out.
1. Run adadmin–>Recreate Grants and Synonyms
2. Compile Apps Schema
This has resolved the issue with autoconfig on the database side.
The WordPress.com stats helper monkeys prepared a 2014 annual report for this blog.
Here’s an excerpt:
The Louvre Museum has 8.5 million visitors per year. This blog was viewed about 240,000 times in 2014. If it were an exhibit at the Louvre Museum, it would take about 10 days for that many people to see it.
Click here to see the complete report.
Operating System: OEL 5.5.
Oracle EBS Version: R12.1.3
Oracle EBS Database Version 126.96.36.199(Before Upgrade)
Ref: Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 (Doc ID 1524398.1)
Apply Below ApplicationPatches:
If you already on R12.1.3 then non need to apply Patch 9239090 – Oracle E-Business Suite 12.1.3
Apply Patch 12923944
Apply Patch 13473483
Apply Patch 16289505 – 12c Release 1 interoperability patch for Release 12.1
Apply Patch 18843706
Apply Patch 19558309
Step1:Prepare to create the 12.1.0 Oracle home
-Install Oracle Software 12c
mkdir -p /d01/oracle/PROD/db/tech_st/12c
Download below patchsets for 12c database
Unzip and run the runInstaller
Step2: Install Examples CD
Create nls/data/9idata directory
On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the following command to create the $ORACLE_HOME/nls/data/9idata directory.
$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl
Apply additional 188.8.131.52 RDBMS patches
Apply the following patches:
For all UNIX/Linux platforms:
Step5:Shut down Applications server processes and database listener
On each application tier server node, shut down all server processes or services. On the database tier server node, shut down the Oracle Net or Net8 database listener in the old Oracle home.
Note: The Applications will be unavailable to users until all remaining tasks in this section are completed.
Attention: Make sure that you do not have the LOCAL_LISTENER initialization parameter set to ensure that the database does not inadvertently point to a non-existent listener during upgrade.
Step6:Drop SYS.ENABLED$INDEXES (conditional)
If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it:
SQL> drop table sys.enabled$indexes;
Remove the MGDSYS schema (conditional)
If you are upgrading from an RDBMS version prior to 12c, on the old database server node, use SQL*Plus to connect to the database as SYSDBA and run the $ORACLE_HOME/md/admin/catnomgdidcode.sql script. This drops the MGDSYS schema.
$ sqlplus “/ as sysdba” @?/md/admin/catnomgdidcode.sql
Step7:Prepare to upgrade
Run FIX and Check Again…If there are any errors…….
Compile the Invalids
Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration server node to the database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:
$ sqlplus “/ as sysdba” @adgrants.sql (or adgrants_nt.sql)
[APPS schema name]
Step15:De-register Database and Implement Autconfig
Run Autoconfig on the application side as well…..
Start the application tier services…..
This finishes the R12 EBS Database 184.108.40.206 to 220.127.116.11
Autoconfig Log shows below error
AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora
AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora. [ID 1324667.1]
There is no information in the table FND_NODES for the database node.
This means that autoconfig has not been executed in the database tier or there was a problem
when it was executed in the database tier.
So you need to run autoconfig on the database tier to gather the information.
There is no database node declared in the FND_NODES table
To implement the solution, please execute the following steps:
1. Ensure that you have taken a backup of your system before applying the recommended solution.
2. Clean the Data Topology Model
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
3. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables
If you see OPP is Down with Actual Process is 0 And Target Process is 1 then do the following
1. Shutdown concurrent server via command adcmctl.sh under $COMMON_TOP/admin/scripts/<context_name>
3. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep applmgr | grep FNDLIBR
4. Run adadmin to relink FNDSVC executable.
a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type “FND” When prompted; ( Enter list of products to link (‘all’ for all products) [all] : FND )
e. Ensure adrelink is exiting with status 0
5. Start Concurrent Managers using adcmctl.sh
The “Parallel Run” feature enables AutoConfig to be executed simultaneously across multiple nodes of an Oracle E-Business Suite instance. Certain AutoConfig configurations of one node depend on the configurations of other nodes. When running in parallel mode, AutoConfig uses dbms_locks so that the configuration of one node does not interfere with the configuration of other nodes. During the instantiation (INST) phase, locking is done at the script level. During the execution (EXEC) phase, locking is done at the product_top level.
AutoConfig can be run in parallel mode on the application tier with the following command:
perl $AD_TOP/bin/adconfig.pl contextfile=<CtxFile> [product=<product_top>] –parallel
Where <CtxFile> is the absolute path of the applicaton tier context file, and <product_top> is the short name of the product to be configured.
AutoConfig can be run in parallel mode on the database tier with the following command:
perl $ORACLE_HOME/appsutil/bin/adconfig.pl contextfile=<CtxFile> -parallel
Where <CtxFile> is the absolute path of the database tier context file.
In parallel mode, AutoConfig must be invoked with the “–parallel” option on all nodes of a multi-node environment.