R12.2 Clone Execution Steps

27-May-2014

Sudhakar Allamsetti

Table of Contents

1. verview............................................................................................................ 4

2. Source & Target System Information ..................................... 4

2.1 Targer system uers and Groups............................................................... 4

2.2 Targer Linux server should have all the OS packages of R12.2
minimum requirements.......... ........................ 4

2.3 Target server should have Minimum Swap Space.................................. 4

2.4 Collect Source Instance Credintials......................................................... 5

2.5 Target system OS Credintials & Path to configure Database and application
Servers.... .................................... 5

3. Cloning Process Source System:..... .................................................... 6

4..... Cloning process of Target Server........ ................................. 7

4.1 Configure Target RUN Filesystem... ..................................................... 7

4.2 Configure Target Patch filesystem..... .................................... 8

5..... Post Clone Configuration Changes :.............................................................................................. 9

1 Overview

The document provides information for E_business suite 12.2 Clone Execution steps

This document contains of the hardware ( Disk Space, CPU and Memory), OS pre-requsites and Clone execution Steps

This document applies to 64-bit Linux operating systems on the x86-64 hardware architecture.

2 Source & Target System Information.

Source System	Name	memory	Disk Space	CPU
Database Server	oadbup	16 GB	1800 GB*	8 CPU (Intel(R) Xeon(R) CPU X5650 @ 2.67GHz)
Application Server	oacmup	8 GB	296 GB	4 CPU (Intel(R) Xeon(R) CPU X5650 @ 2.67GHz)

Target Server
Database Server	oadb12	16 GB	1800 GB*	8 CPU (Intel(R) Xeon(R) CPU X5650 @ 2.67GHz)
Application Server	oacm12	8 GB	296 GB	4 CPU (Intel(R) Xeon(R) CPU X5650 @ 2.67GHz)

· *Disk space size varies depends on Database size.

2.1 Targer system uers and Groups

Usernames = apploa12 , oraoa12

Group = dba

· Oraoa12 user is the account that owns the database node technology stack (11gR2

Oracle Home) and the database files.

· Apploa12 user is the account that owns the Applications node technology stack (APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, and Oracle Fusion Middleware Oracle Home)

2.2 Targer Linux server should have all the OS packages of R12.2 minimum requirements

· Refer the R12.2 Minimum requirements document

2.3 Target server should have Minimum Swap Space

· Swap space shouled be minimum of 16GB or More.

· Before cloning to a new server, ensure the Source System has enough free disk space. Oracle Fusion Middleware cloning tools require 6GB in /tmp and 6GB under $COMMON_TOP.

2.4 Collect Source Instance Credintials

a. Apps password

b. System schema password

c. Weblogic admin password

2.5 Target system OS Credintials & Path to configure Database and application Servers

Target System Details	DB Server Values
Database Server Name	OADB12
username	oraoa12
Oracle Base Path	/oa12/oracle/dbnode/
Oracle Data path	/oa12/oracle/oa12data
Oracle Home	/oa12/oracle/dbnode/11.2.0
Database Port	1571
Oracle SID	OA12

Target System Details	Application Server Values
Application Server Name	OACM12
username	apploacm12
Application Base Path	/oa12/oracle/oa12appl
Database Port	8050
Oracle SID or TWO_TASK	OA12

Create the below three directories in target application server :

Change to Application Base directory

cd /oa12/oracle/oa12appl

mkdir -p /oa12/oracle/oa12appl/fs1/
mkdir -p /oa12/oracle/oa12appl fs2/
mkdir -p /oa12/oracle/oa12appl /fs_ne/

3. Cloning Process Source System:

a) connect to the oraoaup account on oadbup server, change directory to $ORACLE_HOME/appsutil/scripts/OAR2_oadbup and execute

“perl ./adpreclone.pl dbTier”.

b) Log on to the "Run Edition File System" in the Source System as the apploaup user, and run the following commands on each Node that contains an APPL_TOP:

$ cd <INST_TOP>/admin/scripts or $ADMIN_SCRIPTS_HOME

$ perl adpreclone.pl appsTier

1. Shutdown the Apps tier

Connect to the appl[tgsid] account on the oacm[dv|tst] server and execute the following:

cd $ADMIN_SCRIPTS_HOME

./adstpall.sh apps/<Appspassword> # after 5 minutes, kill remaining process

2. Shutdown the database tier

Connect to the ora[tgsid] account on the oadb[dv|tst] server and execute the following:

cd $ORACLE_HOME/appsutil/scripts/<SID_hostname>

lsnrctl stop <Listner_name>

Eg: lsnrctl stop OAR2

3. Copy Oracle Home and Datafiles. ( prefer to use tar.gz to save source softlinks and time to copy)

a) Database Server :

cd $ORACLE_HOME

scp –pr 11.2.0 oraoa12@oadb12: /oa12/oracle/dbnode/

cd /oaup/oracle/

scp –pr oaupdata oraoa12@oadb12: /oa12/oracle/dbnode/

b) Application Server:

Note: You need to make sure which is the run file system before we initiate a copy i.e. FS1, FS2 and also we should be make sure that we ran adpreclone.pl on this FS.

[apploaup@oacmup scripts]$ echo $FILE_EDITION

run

[apploaup@oacmup scripts]$ echo $RUN_BASE

/oaup/oracle/oaupappl/fs1

cd /oaup/oracle/oaupappl/fs1

scp –pr EBSapps /oa12/oracle/oa12appl/fs1

Note: Don’t copy the other two directories under “fs1” inst , FMW_Home

If the Target server is not having the destination directories then please create

4. Cloning process of Target Server

4.1 Configure Target RUN Filesystem

a) Configure application Tier (RUN)

cd /oa12/oracle/oa12appl/fs1/comn/clone/bin

perl adcfgclone.pl appsTier

post completion of adcfgclone appsTier , please start the services

b) RUN the ENV for the Applciation tier

. /oa12/oracle/oa12appl/fs1/EBSapps/appl/APPSOA12_oacm12.env

c) Start the application Services

cd $ADMIN_SCRIPTS_HOME

adstral.sh apps/<Appspassword>

Provide Weblogic Password:

d) Complete basic sanity check

a) Login to applications

b) Launch forms

c) Submit concurrent request

4.2 Configure Target Patch filesystem

a) adpreclone on TARGET RUN FILESYSTEM

cd $ADMIN_SCRIPTS_HOME

adpreclone.pl appsTier

b) SHUTDOWN THE APPLICATION which is running on RUN FILESYSTEM

cd $ADMIN_SCRIPTS_HOME

adstpall.sh apps/<Appspassword>

c) COPY THE TARGET RUN FILESYSTEM to TARGET PATCH FILESYSTEM (OACM12)

cd /oa12/oracle/oa12appl/fs1

cp –pr EBSapps /oa12/oracle/oa12appl/fs2/

d) Configure application Tier (PATCH)

cd /oa12/oracle/oa12appl/fs2/EBSapps/comn/clone/bin

perl adcfgclone.pl appsTier

Important parameter values to remember:

Do you want to add a node (yes/no) [no] : no

Target System File Edition type [run] : patch

Enter the full path of Run File System Context file : < We should provide the target RUNFS xml file complete path >

Eg:/oa12/oracle/oa12appl/fs1/inst/apps/OA12_oacm12/appl/admin/OA12_oacm12.xml

Target System Port Pool [0-99] :8051 (“Runedition port+1” i.e. 8050+1)

e) Start the application Services from RUN Filesystem

. /oa12/oracle/oa12appl/fs1/EBSapps/appl/APPSOA12_oacm12.env

cd $ADMIN_SCRIPTS_HOME

adstral.sh apps/< apps password >

5. Post Clone Configuration Changes:

Search for ‘JAVA COLOR SCHEME’. Change the color to match the following: DEV – blaf, TEST – red, OPMS – blaf, FINX – blue, OPMR – blue, OPMC – purple, TEMP – purple, OADV – blaf, OATST – red, OATR - titanium.

tSearch for ‘ICX:Session Timeout’ and change the timeout setting to 240.

Change the following 4 BNE system profiles where the “TO:” can be oadv, oatst, upgr, oatr, etc.

BNE Debug Log Directory

From: /dev/oracle/devcomn/temp

To: /test/oracle/oadvcomn/temp

BNE Redirect Portal URL:

From: http://dev.sudha.com:8020/pls/DEV/OracleNavigate.Responsibility

To: http://test.sudha.com:8030/pls/OADV/OracleNavigate.Responsibility

BNE UIX Physical Directory

From: /dev/oracle/devcomn/html/cabo

To: /test/oracle/testcomn/html/cabo

BNE Upload Staging Directory

From: NULL

To: /tmp

you might see the below error when you run adop phase=prepare

Error:

ARNING: [CVM Error Report]
The following report lists errors encountered during CVM Phase
<filename> <return code where appropriate>
/oard/oracle/oardappl/fs1/EBSapps/appl/fnd/12.0.0/patch/115/bin/txkUpdateEBSDomain.pl -1

No. of scripts failed in CVM phase: 1

I have taken the below action plan :

1) Run autoconfig manually and verify the issues.

Below are the two scripts got failed and fixes are here as follows:

1) bisdblrp.sql

2) txkappsprf.sql

Issues & Fixes :

==========

Error 1:

WARNING: [AutoConfig Error Report]

The following report lists errors AutoConfig encountered during each

phase of its execution. Errors are grouped by directory and phase.

The report format is:

[PROFILE PHASE]

AutoConfig could not successfully execute the following scripts:

Directory: /oaph/oracle/oaphappl/fs1/FMW_Home/webtier/perl/bin/perl -I /oaph/oracle/oaphappl/fs1/FMW_Home/webtier/perl/lib/5.10.0 -I /oaph/oracle/oaphappl/fs1/FMW_Home/webtier/perl/lib/site_perl/5.10.0 -I /oaph/oracle/oaphappl/fs1/EBSapps/appl/au/12.0.0/perl -I /oaph/oracle/oaphappl/fs1/FMW_Home/webtier/ohs/mod_perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /oaph/oracle/oaphappl/fs1/inst/apps/OAPH_oacmph/admin/scripts/adexecsql.pl sqlfile=/oaph/oracle/oaphappl/fs1/inst/apps/OAPH_oacmph/admin/install

bisdblrp.sql INSTE8_PRF 1

Solution:

Drop the duplicate DB Links and then manually run the bisdblrp.sql script and the re-run autoconfig.

drop database link APPS_TO_APPS.WORLD (which is owned by obt_aa)

drop database link EDW_APPS_TO_WH.WORLD (which is owned by obt_aa)

Run the failing script (bisdblrp.sql) manually:

# cd /oaph/oracle/oaphappl/fs1/inst/apps/OAPH_oacmph/admin/install/

# sqlplus apps/<passwd>

SQL>@bisdblrp.sql

when prompted define the apps username, apps password and the DBNAME for this instance

Error 2:

adcvmlog.xml renamed to /oaph/oracle/oaphappl/fs1/inst/apps/OAPH_oacmph/admin/log/08051619/adcvmlog.xml.08051627

WARNING: [AutoConfig Error Report]

The following report lists errors AutoConfig encountered during each

phase of its execution. Errors are grouped by directory and phase.

The report format is:

[PROFILE PHASE]

AutoConfig could not successfully execute the following scripts:

txkappsprf.sql INSTE8_PRF 1

AutoConfig is exiting with status 1

AutoConfig execution completed on Tue Aug 5 16:27:42 2014

Time taken for AutoConfig execution to complete : 7 mins 56 secs

Solution:

adop phase=fs_clone -- finished sucessfully

adop phase=prepare Erroring out

I found metalink note 784254.1

but solution provided there did not worked

SELECT DISTINCT substr(object_name, 1, length(object_name)-2) q_name

FROM dba_objects

WHERE object_type = 'RULE SET'

AND object_name like 'WF%'

AND owner in ('APPLSYS', 'APPS')

AND status = 'INVALID';

still returns

WF_JAVA_ERROR

WF_JAVA_DEFERRED

WF_WS_JMS_OUT

WF_WS_SAMPLE

WF_WS_JMS_IN

WF_JMS_OUT

WF_JMS_JMS_OUT

WF_JMS_IN

Type: ODM Question

How to recreate 'APPLSYS.WF_JAVA_DEFERRED_R' subscriber?

Type: ODM Answer

1. Ensure that you have taken a backup of your system before applying the recommended solution.

2. Run the following scripts in a TEST environment first:

declare

l_wf_schema varchar2(200);

lagent sys.aq$_agent;

l_new_queue varchar2(30);

begin

l_wf_schema := wf_core.translate('WF_SCHEMA');

l_new_queue := l_wf_schema||'.WF_JAVA_DEFERRED';

lagent := sys.aq$_agent('WF_JAVA_DEFERRED',null,0);

dbms_aqadm.remove_subscriber(queue_name=>l_new_queue, subscriber=>lagent);

end;

commit;

declare

l_wf_schema varchar2(200);

lagent sys.aq$_agent;

l_new_queue varchar2(30);

begin

l_wf_schema := wf_core.translate('WF_SCHEMA');

l_new_queue := l_wf_schema||'.WF_JAVA_DEFERRED';

lagent := sys.aq$_agent('WF_JAVA_DEFERRED',null,0);

dbms_aqadm.add_subscriber(queue_name=>l_new_queue, subscriber=>lagent,rule=>'1=1');

end;

commit;

3. Once the scripts complete, confirm that the OBJECT is VALID.

You can use the following SQL to confirm:

select object_name, object_type, status from dba_objects where object_name='WF_JAVA_DEFERRED_R' ;

AppsDBA-Sallamsetti

Wednesday, 13 August 2014

R 12.2.3 Cloning Steps

1 Overview

2 Source & Target System Information.

2.1 Targer system uers and Groups

2.2 Targer Linux server should have all the OS packages of R12.2 minimum requirements

2.3 Target server should have Minimum Swap Space

2.4 Collect Source Instance Credintials

2.5 Target system OS Credintials & Path to configure Database and application Servers

3. Cloning Process Source System:

4. Cloning process of Target Server

4.1 Configure Target RUN Filesystem

4.2 Configure Target Patch filesystem

5. Post Clone Configuration Changes:

12.2 Autoconfig Issue/Fixes