Search This Blog

Thursday, December 6, 2018

AD Administration error: adptaskGetTaskStatusID: Error while selecting from table AD_TASK_STATUS : ORA-03114: not connected to ORACLE

Hi,

Below error encountered while generating product jar files in adadmin. We are able to perform other adadmin operations successfully except this one. After the fix we were able to run adadmin without any issue.

ERROR 
-----------------------
AD Administration error:
adptaskGetTaskStatusID: Error while selecting from table AD_TASK_STATUS

AD Administration error:
ORA-03114: not connected to ORACLE


AD Administration error:
adptaskPostpatchTiming: Error calling adptaskGetTaskStatusID()


Fix :

Check the profile for apps and system users.

SQL> SELECT profile FROM dba_users WHERE username = 'APPS';

PROFILE
------------------------------
EBS_APPS

SQL> SELECT profile FROM dba_users WHERE username = 'SYSTEM';

PROFILE
------------------------------
DEFAULT

Make sure IDLE_TIME is set to unlimited for both the profiles.

SQL> SELECT * FROM dba_profiles WHERE profile = 'EBS_APPS' and resource_name in ('IDLE_TIME','CONNECT_TIME');

PROFILE                        RESOURCE_NAME                    RESOURCE
------------------------------ -------------------------------- --------
LIMIT
----------------------------------------
EBS_APPS                       IDLE_TIME                        KERNEL
UNLIMITED

EBS_APPS                       CONNECT_TIME                     KERNEL
UNLIMITED





SQL> SELECT * FROM dba_profiles WHERE profile = 'EBS_APPS' and resource_name in ('IDLE_TIME','CONNECT_TIME');

PROFILE                        RESOURCE_NAME                    RESOURCE
------------------------------ -------------------------------- --------
LIMIT
----------------------------------------
EBS_APPS                       IDLE_TIME                        KERNEL
UNLIMITED

EBS_APPS                       CONNECT_TIME                     KERNEL
UNLIMITED

Also please check the below parameter set to TRUE in pfile.

SQL> sho parameter resource_limit;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
resource_limit                       boolean     FALSE

For my environment it was set to FALSE and thus we were getting error while generating product jar files. 

SQL> alter system set resource_limit=TRUE scope=both;

System altered.

SQL> sho parameter resource_limit;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
resource_limit                       boolean     TRUE

Make sure IDLE_TIME is set unlimited.

--Re-run adadmin. Fix worked perfectly for our environment.

Thanks!
Sikky



Tuesday, December 4, 2018

Enable FND : Diagnostics from backed if login page is not working in ebs r12.2

Hi,

Please find the steps below to enable trace for login page from backend if login page is inaccessible. 


FND: Diagnostics = Yes  : - 

DECLARE 
stat boolean; 
BEGIN 
dbms_output.disable; 
dbms_output.enable(100000); 
stat := FND_PROFILE.SAVE('FND_DIAGNOSTICS', 'Y', 'SITE'); 
IF stat THEN 
dbms_output.put_line( 'Stat = TRUE - profile updated' ); 
ELSE 
dbms_output.put_line( 'Stat = FALSE - profile NOT updated' ); 
END IF; 
commit; 
END; 


2> Enable debugging: 

a) Log into R12.2 middle tier and source the 'run' file system environment file. 

b) Backup file $INST_TOP/appl/admin/oacore_wls.properties 

c) Add following lines to $INST_TOP/appl/admin/oacore_wls.properties file (in all middle tiers, if needed) 

AFLOG_ENABLED=TRUE 
AFLOG_LEVEL=STATEMENT 
AFLOG_MODULE=% 
AFLOG_FILENAME=/tmp/Login.log (this is an example; just make sure that this is a writable directory) 

d) Bounce all middle tier services for change in steps #2 and #4 to take effect: 

$INST_TOP/admin/scripts/adstpall.sh 

$INST_TOP/admin/scripts/adstrtal.sh 

3> Reproduce the issue. This time you will receive "details" below the error message from the screenshot uploaded by you. 
Click on that and update the complete error message. 


Trace will be logged in "/tmp/Login.log" and you can check this file for error details.

Tuesday, November 27, 2018

Cannot identify any valid application tier nodes in ADOP_VALID_NODES table. Ensure AutoConfig has been run on all nodes.

Hello,

I got the below error while running adop and the issue has been fixed after i followed note id 2064223.1

I would suggest to read 2282694.1 also and see whether it applies to your issue. 

Error :

Initializing.
    Run Edition context  : /a01/appsclone/CLONE/fs2/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
    Patch edition context: /a01/appsclone/CLONE/fs1/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
*******FATAL ERROR*******
PROGRAM : (/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/bin/adzdoptl.pl)
TIME    : Wed Nov 28 08:38:28 2018
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: Cannot identify any valid application tier nodes in
          ADOP_VALID_NODES table. Ensure AutoConfig has been run on all nodes.



Fix :

1. Backup the fnd_oam_context_files, fnd_nodes, and adop_valid_nodes tables, and if on AD/TXK 8 or higher; ad_nodes_config_status in the EBS env nodes:

      Linux#> sqlplus applsys/<pwd>

      SQLPlus#> create table fnd_oam_context_files_bkp as select * from fnd_oam_context_files;

      SQLPlus#> create table fnd_nodes_bk as select * from fnd_nodes;

        SQLPlus#> create table adop_valid_nodes_bk as select * from adop_valid_nodes;

      If on AD/TXK 8 or higher:

      SQLPlus#> create table ad_nodes_config_status_bk as select * from ad_nodes_config_status;



 2. Truncate the following tables (Continue from step 1):

      SQLPlus#> truncate table fnd_oam_context_files;

      SQLPlus#> truncate table fnd_nodes;

      SQLPlus#> truncate table adop_valid_nodes;

      If on AD/TXK 8 or higher:

      SQLPlus#> truncate table ad_nodes_config_status;



3.  Run AutoConfig on the DB tier:

Source the <RDBMS_ORACLE_HOME> home.

Linux#> cd <RDBMS_ORACLE_HOME>/appsutil/scripts/<SID>_<HOSTNAME>/

Linux#> ./adautocfg.sh

              ... Confirm Autoconfig completes successfully.

              ... If RAC, Repeat step 3 on all RAC nodes.



4.  Run Autoconfig on the run file system.

Linux#> source <EBS_BASE>/EBSapps.env run

Linux#> cd $ADMIN_SCRIPTS_HOME

Linux#> ./adautocfg.sh

      ... Confirm Autoconfig completes successfully.

      ... If more than one EBS node, repeat step 4 on all EBS nodes.



5.  Run Autoconfig on the patch file system

Before running Autoconfig on the patch file system the ebs_login trigger MUST be disabled
... After the successful completion of Autoconfig the ebs_login trigger MUST be re-enabled.


a. Disable the ebs_login trigger using the following SQL.

Linux#> sqlplus system/<pwd>

SQLPlus#> alter trigger ebs_logon disable;



b. At this time Run autoconfig with the patch env sourced .       

Linux#> source <EBS_BASE>/EBSapps.env patch

Linux#> cd $ADMIN_SCRIPTS_HOME

Linux#> ./adautocfg.sh

... Confirm Autoconfig completes successfully

... If more than one EBS node, repeat step 5.b on all EBS nodes.


c. Enable the ebs_login trigger using the following SQL.

Linux#> sqlplus system/<pwd>

SQLPlus#> alter trigger ebs_logon enable;


 6.  After Autoconfig has been run successfully on all nodes, run the following two (2) queries in order to verify the tables have been correctly populated:

SQL>    set pagesize 5
        set linesize 132
        col node_name format a15
        col server_id format a8
        col server_address format a15
        col platform_code format a4
        col webhost format a12
        col domain format a20
        col virtual_ip format a12

        select node_id, platform_code, support_db D, support_cp C, support_admin A, support_forms F, support_web W, node_name, server_id,
               server_address, domain, webhost, virtual_ip, status
          from fnd_nodes order by node_id;



SQL>    set pagesize 5
        set linesize 132
        col NAME format A20
        col VERSION format A12
        col PATH format A110
        col STATUS format A10

        select NAME,VERSION,PATH, STATUS from FND_OAM_CONTEXT_FILES;


After the fix i was able to run adop without any issue.


Thanks!

Monday, November 12, 2018

How to enable trace in ebs r12.2 from backend (if login page is not accessible)

Hi,

Test the following steps to enable FND Debug and / or AF Logging in E-Business Suite:

1. Source the run file system environment file.
2. Backup file:
   $INST_TOP/appl/admin/oacore_wls.properties

If you dont see the parameters, you can add them. 
3. Edit $INST_TOP/appl/admin/oacore_wls.properties and add the following lines (adjust the variables accordingly):
AFLOG_ENABLED=true
AFLOG_LEVEL=statement
AFLOG_MODULE=%
AFLOG_FILENAME=/tmp/aflog.txt

4. Re-start Middle tier services.
5. Reproduce the issue.
6. Collect the log file.
7. Disable logging by removing the lines which were addded to oacore_wls.properties and re-start services.

 
Thanks!
Sikky

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

Hello,

I got the issue below while running prepare phase. I was able to fix the issue with the solution below and thus i am sharing it here.

Cause :

Query the below parameter in db context file.

grep  s_patch_service entry $CONTEXT_FILE

(This is was not present in my context file, thus the error was tripping)

Soultion :


1. Ensure that the below parameters in the database context file are set to: $ORACLE_HOME/appsutil/jre

"s_jretop , s_jdktop

Parameter "ADJVAPRG" needs to be set to $ORACLE_HOME/appsutil/jre/bin/java</ADJVAPRG>

2. Execute admkappstil.pl on the apps node.

3. Copy the generated appsutil.zip to db node and unzip.

4. Execute autoconfig on the database tier.

5. Ensure s_patch_service entry exists in the db context file. 

6. Re-test adop prepare phase.

7. Migrate the solution as appropriate to other environments.

Thats it.

Monday, November 5, 2018

EBS login analyzer

E-Business Suite Applications Login Analyzer (Doc ID 2319360.1)


 perl checkLogin.pl



  Enter the "APPS" password:


  Enter the "APPLSYSPUB" password:


  Prompt: Enter the Application User Name
  If you experiencing a login issue for a single, *specific* E-Business
  Suite User Account, please enter that user account name here.
  Otherwise press [Enter] if the issue affects all users.



Sunday, November 4, 2018

how to apply driver in adop in R12.2.4


Hello,

Below driver file was supposed to apply during database migration from solaris to linux. As i felt the step provided in MOS note id does not have much detail. I thought it will be better if i provide steps in detail, it will be helpful for someone. This task seriously ate lot of time.


Create ConText objects

Certain ConText objects are not preserved by the import process. The consolidated export/import utility patch that you applied to the source administration server node in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch driver file. You use this driver file to call the scripts that create these objects. Run the following command:

bash-3.2$ perl $AU_TOP/patch/115/bin/dpost_imp.pl dpost_imp.drv 11

dpost_imp.drv --> User defined. you can choose any name with .drv extension.
11 --> version of your database. I used 11 since mine was 11.2.0.4

bash-3.2$ ls
dpost_imp.drv  dpost_imp.pl

driver file created as you can see above ls command.

Now copy "dpost_imp.drv"   to $AU_TOP/patch/115/driver

You must mention the driver file location like below. Below is the command to apply driver in adop in 12.2.4.

adop phase=apply options=nocopyportion,,nogenerateportion patchtop=$AU_TOP/patch/115/bin patches=driver:dpost_imp.drv hotpatch=yes

Thats it. you must be able to apply the driver.

Thanks!








Friday, October 26, 2018

rapidwiz log file locations in R12.2 from MOS


Rapidwiz log file location in R12.2 :

Before the installation starts:
$TMP/<MMDDHHMM>/<MMDDHHMM>.log
$TMP/<MMDDHHMM>/<hostname>_<SID>.xml
$TMP/<MMDDHHMM>/<hostname>_<SID>_apps.xml
The Rapidwiz Configuration File is saved in the following four locations:
$TMP/<MMDDHHMM>/conf_<SID>.txt
Primary $INST_TOP/conf_<SID>.txt
Secondary $INST_TOP/conf_<SID>.txt
<RDBMS ORACLE_HOME>/appsutil/conf_<SID>.txt

Preinstall System Check Logs:

$TMP/<MMDDHHMM>/<MMDDHHMM>.log 
$TMP/dbPreInstCheck.xxxxx.log
$TMP/wtprechk.xxxx/wtprechk.xxxx.log 

<Global Inventory>/logs/installActions<timestamp>.log

Database Tier:

Main installation log:

RDBMS $ORACLE_HOME/appsutil/log/$CONTEXT_NAME/<MMDDHHMM>.log

Oracle Home installation logs:

RDBMS $ORACLE_HOME/temp/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.install0.log
RDBMS $ORACLE_HOME/temp/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.default0.log
<Global Inventory>/logs/<timestamp>.log
<Global Inventory>/logs/cloneActions<timestamp>.log
<Global Inventory>/logs/install<timestamp>.log
<Global Inventory>/logs/installActions<timestamp>.log
<Global Inventory>/logs/installProfile<timestamp>.log
<Global Inventory>/logs/installSummary<timestamp>.log
<Global Inventory>/logs/OPatch<timestamp>.log
<Global Inventory>/logs/oraInstall<timestamp>.log
<Global Inventory>/logs/silentInstall<timestamp>.log

RMAN restore scripts (Install mode only):

<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac1.rman
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac2.sql
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-single2.sql
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac21.sql
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-single21.sql
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac3.rman

RMAN restore logs (Install mode only):

<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac1.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac2.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-rac3.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-single1.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-single2.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/restore-single3.log
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/LogOff.sql
<RDBMS Oracle Home>/appsutil/out/$CONTEXT_NAME/fndClean.sql

Database characterset conversion (Install mode only):

<ORACLE_HOME>/appsutil/log/<Context Name>/addbccnv.txt

AutoConfig context file:

<RDBMS ORACLE_HOME>/appsutil/<Context Name>.xml

AutoConfig logs:

<RDBMS ORACLE_HOME>/appsutil/log/<Context Name>/<MMDDHHMM>/adconfig.log
<RDBMS ORACLE_HOME>/appsutil/log/<Context Name>/<MMDDHHMM>/NetServiceHandler.log
<RDBMS ORACLE_HOME>/temp/$CONTEXT_NAME/RACAutoConfig_nnnnn.log

Listener log:

<RDBMS ORACLE_HOME>/appsutil/log/$CONTEXT_NAME/addlnctl.txt

Applications Tier(s):

Both primary (run) and secondary (patch) edition file systems will each contain these logs:

Main installation log:

$INST_TOP/logs/<MMDDHHMM>.log

FMW and OHS TechStack Installation/Patching logs:

$APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ebsfmwlayout.log
$APPL_TOP/admin/$CONTEXT_NAME/log/NetServiceHandler.log
$APPL_TOP/admin/$CONTEXT_NAME/log/adcvmlog.xml
$APPL_TOP/admin/$CONTEXT_NAME/log/executeac.log
$APPL_TOP/admin/$CONTEXT_NAME/log/deploytech.log

$APPL_TOP/admin/$CONTEXT_NAME/logs/wls1036.log
$APPL_TOP/admin/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.default0.log
$APPL_TOP/admin/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.install0.log

<Global Inventory>/logs/<timestamp>.log
<Global Inventory>/logs/cloneActions<timestamp>.log
<Global Inventory>/logs/install<timestamp>.log
<Global Inventory>/logs/installActions<timestamp>.log
<Global Inventory>/logs/installProfile<timestamp>.log
<Global Inventory>/logs/installSummary<timestamp>.log
<Global Inventory>/logs/OPatch<timestamp>.log
<Global Inventory>/logs/oraInstall<timestamp>.log
<Global Inventory>/logs/silentInstall<timestamp>.log

Forms Oracle Home installation logs:

$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log
$INST_TOP/admin/log/ohclone.log
$INST_TOP/admin/log/ApplyAppsTechStack_<MMDDHHMM>.log

Service Control logs:

$INST_TOP/logs/appl/admin/log/adadminsrvctl.txt
$INST_TOP/logs/appl/admin/log/adalnctl.txt
$INST_TOP/logs/appl/admin/log/adapcctl.txt
$INST_TOP/logs/appl/admin/log/adcmctl.txt
$INST_TOP/logs/appl/admin/log/adforms-c4wsctl.txt
$INST_TOP/logs/appl/admin/log/adformsctl.txt
$INST_TOP/logs/appl/admin/log/adnodemgrctl.txt
$INST_TOP/logs/appl/admin/log/adoacorectl.txt
$INST_TOP/logs/appl/admin/log/adoafmctl.txt
$INST_TOP/logs/appl/admin/log/adopmnctl.txt
$INST_TOP/logs/appl/admin/log/adstpall.log
$INST_TOP/logs/appl/admin/log/adstrtal.log
$INST_TOP/logs/appl/admin/log/jtffmctl.txt 

References :

Wednesday, October 24, 2018

Rapidwiz errros while solaris to linux migration at FMW installation

Guys,

This error occurred while migration ebs 12.2 from solaris to linux. This is not complete 12.2 installation instead it was only FMW installation for migration activity.


Fatal Error: TXK Install Service

oracle.apps.fnd.txk.config.ProcessStateException: FileSys OS COMMAND Failed : Exit=1 See log for details. CMD= mv /appstier1/CLONE/fs2/inst/apps/CLONE_prodapp/temp/patches/17239083/jdk32 /appstier1/CLONE/fs2/EBSapps/comn/util/ ## Node=NodeId=484 Type=24 TypeName=filesys_patch_action Name= RefId=424 State=init ConfigDoc=APPS_JAVA_HOME ParentDoc=null Topology=R12 Action=os_cmd

    at oracle.apps.fnd.txk.config.FileSysPatchActionNode.doFileSysOSCmd(FileSysPatchActionNode.java:169)

    at oracle.apps.fnd.txk.config.FileSysPatchActionNode.processState(FileSysPatchActionNode.java:101)

    at oracle.apps.fnd.txk.config.PatchActionNode.processState(PatchActionNode.java:187)

    at oracle.apps.fnd.txk.config.PatchNode.processState(PatchNode.java:338)

    at oracle.apps.fnd.txk.config.PatchesNode.processState(PatchesNode.java:79)

    at oracle.apps.fnd.txk.config.InstallNode.processState(InstallNode.java:68)

    at oracle.apps.fnd.txk.config.TXKTopology.traverse(TXKTopology.java:594)

    at oracle.apps.fnd.txk.config.InstallService.doInvoke(InstallService.java:224)

    at oracle.apps.fnd.txk.config.InstallService.invoke(InstallService.java:237)

    at oracle.apps.fnd.txk.config.InstallService.main(InstallService.java:291)



Cannot install WebLogic Server

    RW-50010: Error: - script has returned an error:   1



solution :

As part of migration step i downloaded jdk 32 and 64 bit directories and kept under $COMMON_TOP/util. When rapidwiz tried to copy jdk from stage its was throwing the error. This log can be seen at the below

$APPL_TOP/admin/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.default0.log 
$APPL_TOP/admin/$CONTEXT_NAME/logs/oracle.apps.fnd.txk.install0.log 

Fix :
- remove jdk directories if exists under $COOMON_TOP/util 

I was able to install successfully after doing the above. 

I am consolidating other fixes too in this post whichever i went through MOS.

1. Make sure you dont have higher version of binutils except 2.25 or 2.23.

   binutils-2.25.1-32.base.el7_4.2.x86_64 or binutils-2.23.52.0.1-16.el7.x86_64

Use the below to downgrade it.

 # yum downgrade binutils

 # rpm -Uvh --oldpackage binutils-2.25.1-32.base.el7_4.2.x86_64.rpm

2. Make sure there is adequate space in /tmp

Thanks!
Sikky




Sunday, October 14, 2018

Step by Step : "How to download stage for ebs R12.2"

Hello DBA's,

This post is all about how to download and build stage for oracle E-business suite R12. I feel this would be really helpful for beginners. 

Go to https://edelivery.oracle.com and sign-in with your support credentials.

Left drop down --> Select download package
You can search Oracle E-business Suite in the search bar.


You can review the below Doc id to know what are all the files should be downloaded.

12.2 E-Business Suite Applications Installation Rapid Install Steps To Create the Stage Directories In Preparation For A 12.2 Installation (Doc ID 1596433.1)

All the mentioned zip files should be downloaded from section A-E.

Files to be downloaded :

V100052-01_1of3.zip
V100052-01_2of3.zip
V100052-01_3of3.zip
V100053-01_1of2.zip
V100053-01_2of2.zip
V100054-01.zip
V100055-01.zip
V100056-01.zip
V100057-01.zip
V100058-01.zip
V100059-01_1of2.zip
V100059-01_2of2.zip
V100060-01_1of3.zip
V100060-01_2of3.zip
V100060-01_3of3.zip
V46095-01_1of2.zip
V46095-01_2of2.zip
V100102-01.zip
V35802-01.zip
V35803-01_1of3.zip
V35803-01_2of3.zip
V35803-01_3of3.zip
V35804-01_1of2.zip
V35804-01_2of2.zip
V100061-01.zip
V29856-01.zip
V75792-01.zip

You dont need to download the rest.











Once downloaded you dont need to unzip all the files.  Please read the step below.

We should unzip only the below zip files :

V100052-01_1of3.zip
V100052-01_2of3.zip
V100052-01_3of3.zip


Enter option 1 to create new stage area
 Select your OS accordingly.


Provide the stage directory where all the zips are present. 

Thats it. The rest will be taken care by buildstage.sh script once this is done our stage is ready for installation.


References :

12.2 E-Business Suite Applications Installation Rapid Install Steps To Create the Stage Directories In Preparation For A 12.2 Installation (Doc ID 1596433.1)

https://docs.oracle.com/cd/E26401_01/doc.122/e22950.pdf

Please leave a comment if you like this post. 

Wednesday, October 3, 2018

How to apply weblogic patch in R12.2



Copy the patches and move to the below location :

$FMW_Home/utils/bsu/cache_dir

Unzip patches in above location. When you unzip the patch you will get the jar file named with 4 character. Ex : B47X. Use these jar files while applying patch. 

Command to apply weblogic patch in R12.2 :

bash-3.2$ bsu.sh -install -patch_download_dir=$FMW_Home/utils/bsu/cache_dir -patchlist=B47X -prod_dir=$FMW_HOME/wlserver_10.3
Checking for conflicts................
Conflict(s) detected - resolve conflict condition and execute patch installation again
Conflict condition details follow:
Patch B47X is mutually exclusive and cannot coexist with patch(es): YIJF,LL4G,D33T,VFS8,Y5AP

Command to rollback the conflicts :

bsu.sh -remove -patchlist=YIJF -prod_dir=$FMW_HOME/wlserver_10.3
bsu.sh -remove -patchlist=LL4G -prod_dir=$FMW_HOME/wlserver_10.3
bsu.sh -remove -patchlist=D33T -prod_dir=$FMW_HOME/wlserver_10.3
bsu.sh -remove -patchlist=VFS8 -prod_dir=$FMW_HOME/wlserver_10.3
bsu.sh -remove -patchlist=Y5AP -prod_dir=$FMW_HOME/wlserver_10.3


Issue :

1.
bash-3.2$ bsu.sh -install -patch_download_dir=$FMW_Home/utils/bsu/cache_dir -patchlist=B47X -prod_dir=$FMW_HOME/wlserver_10.3
Exception in thread "main" Exception in thread "Thread-0" java.lang.OutOfMemoryError: Java heap space
        at org.apache.xmlbeans.impl.store.Cur.createElementXobj(Cur.java:257)

2.

bash-3.2$ bsu.sh -install -patch_download_dir=$FMW_Home/utils/bsu/cache_dir -patchlist=B47X -prod_dir=$FMW_HOME/wlserver_10.3
Checking for conflicts...........Exception in thread "main" java.lang.OutOfMemoryError: GC overhead limit exceeded
        at java.util.Arrays.copyOf(Arrays.java:2367)

Fix :

Update MEM_ARGS parameter in bsu.sh file after taking backup under $FMW_HOME/utils/bsu/
#!/bin/sh

JAVA_HOME="/a01/appsclone/CLONE/fs2/EBSapps/comn/util/jdk"

MEM_ARGS="-Xms2048m -Xmx2048m -XX:+UseParallelGC"

"$JAVA_HOME/bin/java" ${MEM_ARGS} -jar patch-client.jar $*

Monday, October 1, 2018

adop fails with "invalid username/password; logon denied" for custom schema

Below error encountered in the txk delta level 10 patching . Please go through this post to fix this issue.

Scenario :

Applying patch 25828573.
    Log: /a01/appsclone/CLONE/fs_ne/EBSapps/log/adop/34/20180926_150103/apply/ahqtest/25828573/log/u25828573.log

***
Continue as if it were successful :
***

AutoPatch could not find a response to the above prompt
in the defaults file.

The patch has FAILED,
Please check the adpatch logs for more details.

You should check the file
/a01/appsclone/CLONE/fs_ne/EBSapps/log/adop/34/20180926_150103/apply/ahqtest/25828573/log/u25828573.log

for errors.

    [UNEXPECTED]Error occurred executing "adpatch  abandon=yes restart=no workers=16   options=hotpatch     console=no interactive=no  defaultsfile=/a01/appsclone/CLONE/fs2/EBSapps/appl/admin/CLONE/adalldefaults.txt patchtop=/a01/appsclone/CLONE/fs_ne/EBSapps/patch/25828573 driver=u25828573.drv logfile=u25828573.log"
    [UNEXPECTED]Refer to the log files for more information.
    [UNEXPECTED]Apply phase has failed.


[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.



We can get the detailed information from the adop log

/a01/appsclone/CLONE/fs_ne/EBSapps/log/adop/34/20180926_150103/apply/*****/25828573/log/u25828573.log


Error :


sqlplus -s XX***/***** @/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/a01/appsclone/CLONE/fs2/EBSapps/appl/
ad/12.0.0/patch/115/sql/adaddls.pls ***** XX*** *****'
ERROR:
ORA-01017: invalid username/password; logon denied



An error occurred while running a SQL*Plus script.

***
Continue as if it were successful :
***

AutoPatch could not find a response to the above prompt
in the defaults file.

The patch has FAILED,
Please check the adpatch logs for more details.

You should check the file
/a01/appsclone/CLONE/fs_ne/EBSapps/log/adop/34/20180926_150103/apply/****/25828573/log/u25828573.log

for errors.

adop could not connect to custom schema to execute the script, thus patch is resulting into error. Perform the below to fix this issue. 


Solution :

Script location : $AD_TOP/patch/115/sql

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @adaddls.pls
Enter value for 1: *********** (System Password)
Connected.
Enter value for 2: XXCUST (Custom username)
old   1: grant create procedure to &&2
new   1: grant create procedure to XXCUST

Grant succeeded.

old   1: ALTER SESSION SET CURRENT_SCHEMA = &2
new   1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST

Session altered.

old   2:   execute immediate 'drop synonym &2..APPS_DDL';
new   2:   execute immediate 'drop synonym XXAHQ.APPS_DDL';

PL/SQL procedure successfully completed.


Package created.


Commit complete.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
bash-3.2$ sqlplus system

SQL*Plus: Release 10.1.0.5.0 - Production on Wed Sep 26 15:32:07 2018

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Enter password:

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @adaddlb.pls
Enter value for 1: ********* (System password)
Connected.
Enter value for 2: XXCUST
old   8:        where grantee='&2'
new   8:        where grantee='XXCUST'
Enter value for 2: XXCUST
old  14:     execute immediate 'grant execute on sys.dbms_sql to &&2';
new  14:     execute immediate 'grant execute on sys.dbms_sql to XXCUST';

PL/SQL procedure successfully completed.

old   1: ALTER SESSION SET CURRENT_SCHEMA = &2
new   1: ALTER SESSION SET CURRENT_SCHEMA = XXCUST

Session altered.


Package body created.


Commit complete.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Manually connect to the schema and confirm whether its working.

Retry the adop once again. you can use the below :

adop phase=apply patches=patch_number abandon=no restart=yes

If its failing you can perform the below.

As you can see the error above it was failing at the step below. So i ran the step below manually.


sqlplus -s XXCUST/XXCUST @/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adsqlwrapper.sql '/a01/appsclone/CLONE/fs2/EBSapps/appl/ad/12.0.0/patch/115/sql/adaddls.pls opensys_33 XXCUST XXCUST'


I was able to run adop without any issue with autoskip flag option.

adop phase=apply patches=25828573 abandon=no restart=yes flags=autoskip 

we can use the below to skip the failed adop session or if you manually performed the failed step. 

abandon=no restart=yes flags=autoskip 

This command will restart the patch once again from starting onwards and will skip all the failures if any comes. But make sure to review the log file at the end of the patch application that you have skipped the failures that you want to.

Thanks!
Sikky








Adop erros : APPS.AD_ZD_ADOP became invalid

Error :

This post is about one of the error i encountered while applying txk patch. This error is due to AD_ZD_ADOP package became invalid due to one of the opatch which applied this morning.

Due to invalid package i was unable to perform any operation in adop.

bash-3.2$ adop phase=apply patches=25828573 hotpatch=yes abandon=no restart=yes flags=autoskip

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials.

Initializing.
    Run Edition context  : /a01/appsclone/CLONE/fs2/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
    Patch edition context: /a01/appsclone/CLONE/fs1/inst/apps/CLONE_ahqtest/appl/admin/CLONE_ahqtest.xml
    Patch file system free space: 329.79 GB

Validating system setup.

 Statement Handler Error Code: 4063
 Statement Handler Error Message: ORA-04063: package body "APPS.AD_ZD_ADOP" has errors (DBD ERROR: OCIStmtExecute)
 Reference of statement-handler is valid, not attempting database reconnect.
 Failed to execute SQL statement:
select AD_ZD_ADOP.GET_INVALID_NODES() from dual
 Error Message:
ORA-04063: package body "APPS.AD_ZD_ADOP" has errors (DBD ERROR: OCIStmtExecute)    [UNEXPECTED]Error determining whether this is a multi-node instance

 Statement Handler Error Code: 4063
 Statement Handler Error Message: ORA-04063: package body "APPS.AD_ZD_ADOP" has errors (DBD ERROR: OCIStmtExecute)
 Reference of statement-handler is valid, not attempting database reconnect.
 Failed to execute SQL statement:
  select ad_zd_adop.validate_session_id('') from dual

 Error Message:
ORA-04063: package body "APPS.AD_ZD_ADOP" has errors (DBD ERROR: OCIStmtExecute)

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.


adop exiting with status = 2 (Fail)

i queried dba_objects and confirmed the below. 


select object_name,object_type,owner,status from dba_objects where status='INVALID';


OBJECT_NAME          OWNER                          STATUS  OBJECT_TYPE
-------------------- ------------------------------ ------- -------------------
AD_ZD_ADOP           APPS                           INVALID PACKAGE BODY
FND_DIAGNOSTICS      APPS                           INVALID PACKAGE BODY
XX_AR_MASTER_DATA_DE APPS                           INVALID PACKAGE BODY


I ran utlrp and compile apps schema option through adadmin but it dint fix the issue. 

But the below did.

SQL> grant execute on DBMS_METADATA_UTIL to apps;

Grant succeeded.

SQL> commit;

Commit complete.

SQL> alter package APPS.AD_ZD_ADOP compile body;

Package body altered.

Query once again dba_objects and confirm the package became valid. Then after i was able to run adop. 

Thanks!



Wednesday, August 8, 2018

Step by Step - How to install pre-install rpm in RHEL 7 for oracle ebs R12.2

Dear DBA's,

Installing prerequisite packages are one of the tedious tasks in any implementation or migration. Though this is one time task, its so mundane to check each rpm. Oracle has provided pre-install rpm which will save lot of our time on preparation tasks. All we need to do is configure yum repository and install the single package. Rest of the tasks will be taken care by yum and it will install all the needed pre-requisite packages for both apps and db tier.

Lets see how this can be done.

Go to the directory below. any file you see here with *.repo extension are repositories. YUM will refer this file and look for the packages to be installed. You can either provide any link to download the packages or we can provide the location  (if you have packages in local disk ).

I am going to install preinstall rpm on rhel 7.5 64 bit, So i would use the correspoding ol7 pre install rpm for this installation.

As root user :

# cd /etc/yum.repos.d




Enter the below command as root user and it will create the repository file for preinstall RPM. 

wget http://public-yum.oracle.com/public-yum-ol7.repo



AS you see the above pic public-yum-ol7.repo have been created. Keep only this repository and move other repositories temporarily. 

Open the repository in Vi file and updated enabled=0 to enabled=1 for the items below. You will see lot of items in the repository but only the below are recommended. Items which enabled=1 will be installed by YUM.

[ol6_latest]

name=Oracle Linux $releasever Latest ($basearch)

baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/

gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1

enabled=1


[ol6_addons]

name=Oracle Linux $releasever Add ons ($basearch)

baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/addons/$basearch/

gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1

enabled=1



[ol6_UEK_latest]

name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)

baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/

gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6

gpgcheck=1


enabled=1

# yum update


Type yes "Y"



Now we can install the packages with the below command and Yum will take care of the rest.

# yum install oracle-ebs-server-R12-preinstall








Thanks!
~Sikky


Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle error while installing Pre-install RPM

Hi,

OS : RHEL 7,5 64-bit
Preinstall RPM : OEL 7

I got this error while installing Pre-install RPM . I have shared the steps in this post to fix the same. This fix worked perfectly for me and i never publish a fix unless i tested it.

Error :

GPG key retrieval failed: [Errno 14] curl#37 - "Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle"

Reason :

GPG key is missing.

Solution :

Download the GPG key.


[root@***** ~]# wget http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol7 -O /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
--2018-08-07 10:58:53--  http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol7
Resolving public-yum.oracle.com (public-yum.oracle.com)... 23.34.86.200
Connecting to public-yum.oracle.com (public-yum.oracle.com)|23.34.86.200|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1011 [text/plain]
Saving to: ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle’

100%[====================================================================================================>] 1,011       --.-K/s   in 0s

2018-08-07 10:58:54 (138 MB/s) - ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle’ saved [1011/1011]

Now re-run the installation.

Thanks!
~Sikky

Step by Step R12.2 cloning (Application and DB)


My dearest DBA's,

** I will be happy if you leave a comment or share this post **

Hope this post will be helpful for freshers who does cloning for first time in EBS. 

1.                Pre-Clone

- You can take a backup of the files below (Conditional) :
- /u01/app/oracle/ebzd/R122/EBSapps.env (save actual copy, not symlink)
- $CONTEXT_FILE (both tiers)
- $TNS_ADMIN (both tiers)
- $ORACLE_HOME/dbs (exclude any logfiles)
- Create pfile from spfile
- Create controlfile from trace
- - $<Custom_TOP> (All the files under custom top)

Note :

I have commented few items as conditional since they are environment specific. Please double check whether it actually needed for your environment.

2.                Prepare  Source Instance

Check for in-progress online patching cycle:
On the Source system, there should not be any in-progress online patching cycle. Online
patching should be done till cleanup stage and also fs_clone should be run to synchronize with
the application file system RUN and PATCH.

You can check it easily by below command:

SQL> select ADOP_SESSION_ID, PREPARE_STATUS, APPLY_STATUS, FINALIZE_STATUS,
CUTOVER_STATUS, CLEANUP_STATUS, ABORT_STATUS, STATUS, ABANDON_FLAG,
NODE_NAME from AD_ADOP_SESSIONS order by ADOP_SESSION_ID;

 Or check with adop -status and make sure all the phases are completed properly. If any outstanding patch session, Either complete it or abort before cloning.

2.1 OS and Patch Level

                    Source and Target must be on the same Operating System (OS) and patch level

2.2 Check Disk Space on the Source system and Target

                    Ensure the Source System has enough free disk space. Oracle Fusion Middleware cloning tools require 6GB in /tmp and 6GB under $COMMON_TOP. On the target system file system space should match as that of source.

2.3       AD/TXK Patches

                    Apply the latest AD/TXK patches to the Source system.

                   You can check the lastet version of source instance by below SQL statement.

                SQL> SELECT abbreviation,codelevel FROM AD_TRACKABLE_ENTITIES WHERE abbreviation in (‘txk’,’ad’);

 Output :
                    ABBREVIA CODELEVEL

                    --------        -------------------------

                     ad              C.7

                     txk             C.7


Conditional note :

               If we are not on latest version of AD/TXK patches then we need to apply (Not mandatory step)

Note: Ensure all the services are up in the Source System before proceeding with the following two       steps

3.    Prepare Source Tier

3.1            DB Tier

- You can refresh the db through any of the method as per your convenient.
- If the db is running already in target server, you can simply drop the db and refresh database from source.

Methods can be followed for refresh :

- Cold backup
- Hot backup
- Rman backup

Please read these posts for RMAN methods :

RMAN active db duplication  Read
RMAN backup based duplication Read

3.1.1    Run adpreclone.pl script

cd $ORACLE_HOME/appsutil/scripts/${CONTEXT_NAME}

perl adpreclone.pl dbTier

Note :  $CONTEXT_NAME is nothing but <instance-name>_<hostname>

3.2         Apps Tier

                   Log on to the Application node of the Source System as the applmgr user.

                   Source the environment file of the Run Edition File system.
          
                   $. EBSapps.env run

Important note :

When you do cloning make to sure to note down the run file system in the source. If your source has fs1 has the run file system then we must refresh fs1 as run file system in the target. If source has fs2 in run file system then we must refresh fs2 as run file system in the target.



For example : If my run file system is in fs2 in source then i would do the below.

 - Make fs2 in target (Run file system first)

 - Make fs1 from fs2 (PAtch file system)

3.2.1        Run adpreclone.pl script

                             Check edition , should run file system

                             echo $FILE_EDITION

                             Execute adpreclone

                             $cd $ADMIN_SCRIPTS_HOME

                             $perl adpreclone.pl appsTier


3.2.2        Tar Application RUN File system

                              $. EBSapps.env run

                              Check edition , should return run file system

                              echo $FILE_EDITION

                             $cd $RUN_BASE

                              Ex: /u01/app/oracle/ebz2/R122/fs2

                             $nohup tar –czvf  ebz2_runfs.tar.gz  EBSapps  >  ebz2_runfs.log &

Note: Our run file system is  fs2, so we are compressing fs2 directory.  Its enough if we only copy EBSapps directory under run filesystem. Rest of the directories will be created in target through adcfgclone.


4      Prepare Target System

Backup Context & Config Files (please see Pre Clone steps; you should have saved off the necessary information then; if not, please do so now)


4.1        Backup  files in Target Db Tier/

Take the backup of inti<sid>.ora and $CONTEXT_FILE using  “cp” command.

4.2        Backup  file in Target APPS Tier CONTEXT_FILE and custom env file

Take the backup of CONTEXT_FILE and CUSTOM ENV file usins “cp” command.

 Note : Make sure both apps and DB services are down in target instance before proceeding with below steps

 5         Cleanup Target Application File System

Remove application directory structure from target application instance under $RUN_BASE  
And $PATCH_BASE in the target application tier system.

                   $. EBSapps.env run

bash-3.2$ cd /a01/apps/CLONE/

bash-3.2$ ls

EBSapps.env   L2866958.log  L2866963.log  fs1           fs2           fs_ne         scripts

$ pwd
/a01/apps/CLONE/
$ rm -rf *

Once everything is deleted make a empty directories for run and patch file system.

mkdir -p /a01/apps/CLONE/fs1
mkdir - /a01/apps/CLONE/fs2
Clean old inventory files from local inventory in application tier. Please check local inventory location in /etc/oraInst.loc (other wise you will get error saying oraInventory already exists)


[applmgr@xxxxxxxxxxx ~]$ cat /etc/oraInst.loc

inventory_loc=/u01/app/oracle/ebz2/oraInventory

 cd /u01/app/oracle/ebz2/
mv oraInventory oraInventory_old
mkdir oraInventory

 Cleanup Target Database File

Drop destination DB (If already DB exists)

                    $sqlplus / as sysdba

                    SQL> shutdown immediate;

                    SQL> startup mount exclusive restrict;

                    SQL> drop database;

 You can also go to the location where db files present and clear using rm -rf command.

 Cleanup DB files in ASM (conditional)

Note : If Target DB files are placed under ASM, we need to connect ASM and remove control  files, Data files and redo log files.

Go to server xxxxdbxt02
Sudo –iu grid
 [grid@xxxxdbxt02 ~]$ cat /etc/oratab
+ASM2:/u01/app/12.1.0.2/grid:N          # line added by Agent
Use the below to source the env,
+ASM2 – instance name
/u01/app/12.1.0.2/grid – Grid_Oracle_HOME

 [grid@xxxxdbxt02 ~]$ . oraenv

   ORACLE_SID = [grid] ? +ASM2

   The Oracle base has been set to /u01/app/grid

 [grid@xxxxdbxt02 ~]$ asmcmd

   ASMCMD> lsdg
It will list the available disk groups, go to releavant disk group and delete your DB files under Target sid.


ASMCMD> cd DATA/Target_sid

                  ASMCMD> ls

                  CONTROLFILE/

                  DATAFILE/

                  TEMPFILE/


Go to each directory and execute the below,

 ASMCMD> rm –rf *


Performe the following steps if you are not reusing the old OHOME (Conditional):

Manual DB drop

 Delete all the data files from target database instance. Also check control_file & log_file          

   Location and remove them too.
Use simple rm –rf command to delete these database files.


Deregister old OHOME (Conditional)

cd $ORACLE_HOME/oui/bin

./runInstaller -silent -detachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME="/u01/app/oracle/product/11.2.0.4/ebzd"

Copy oracle_home from the source to target.

 Verify Inventory & oratab entry


4.1         DB Tier Inventory


                    $cat /etc/oraInst.loc

                    Note: DB Inventory is always set to global inventory “/u01/app/oraInventory”


4.2         Oratab entry - - Only for new instances


                      $vi /etc/oratab

                      Add new instance oracle home entry



4.3         ADCFGCLONE

 Its always recommended to copy source oracle home to target and run adcfgclone.pl

Clone DB Tier DataBase

 Note : For building a new instance (Oracle_Home), Steps to clone DB oracle_home from source to    target given here


11.1     Run adcfgclone in DB Tier – Only for New Instances/ Oracle Home binaries copied


                   a) Log on to the Target Instance as the oracle user(DB binaries owner).

                   b) Source the Database tier environment file.

                   c) Execute the following commands:

                       $ORACLE_HOME/appsutil/clone/bin

                       $perl adcfgclone.pl dbTechStack



Disable RAC mode (Conditional):

cd $ORACLE_HOME/rdbms/lib

make -f ins_rdbms.mk rac_off

make -f ins_rdbms.mk ioracle





adcfgclone options for DB tier :



adcfgclone.pl dbTier - This option will be used specifically for cold backup. This option will create and configure oracle home, config files and database in the target.

adcfgclone.pl dbTechStack - This option will be used mainly if we are duplicating database thru rman or any other hot backup method. We must need to manually copy the source oracle home to target. dbTechStack option will create all the config files (ex : xml file) and configure target oracle home.


11.2     Create context file for DB – if previous context file is not available (Conditional)


                Go to $ORACLE_HOME/appsutil/bin

                [oracle@xxxxdbxt02 bin]$ perl adbldxml.pl


               Answer the questions according to your Target DB server and create context file for DB tier.



4.4         Pre Rman Dupicate setup:


Copy the backed up init<sid>.ora and CONTEXT FILE to auxiliary server.

Create a password file in target DB using “orapw” and copy the same in Auxiliary DB under       

                     $ORACLE_HOME/dbs location

Source the environment using <context_name>.env

Start instance in nomount

Choose any of below RMAN scenario to to restore

- Cold backup
- Hot backup
- Rman backup


6      Post cloning DB activity

6.1         Run EBS Technology Codelevel Checker (ETCC) In DB Tier

Download the latest version from MOS

                      sh checkDBpatch.sh

                      Enter the full path to the DB Context file

                       :/u01/app/oracle/product/11.2.0.4/ebzclone/appsutil/ebzclone_xxxxdbxt02.xml



6.2         Node table clean up

Connect as apps user

                     Sqlplus apps/<Source_apps_pwd>

Exec the following :

                    Select node_name from fnd_nodes;

                    It will display source apps and DB nodes.

Cleanup fnd_nodes table :

                    Sql>exec fnd_conc_clone.setup_clean;

                    Sql>commit;


Select node_name from fnd_nodes;

                 It will retrun no rows.


6.3         Edit template for listener (Conditional)


Edit file: /u01/app/oracle/product/11.2.0.4/ebzd/appsutil/template/ad8ilsnr.ora
Remove this line:
(ADDRESS = (PROTOCOL = TCP)(HOST = %s_virtual_hostname%.%s_domainname%)(PORT = %s_dbport%))


Add these lines:
(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = %s_virtual_hostname%.%s_domainname%)(PORT = %s_dbport%)(IP = FIRST)))

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = %s_dbhost%)(PORT = %s_dbport%)(IP = FIRST)))

6.4         Run autoconfig in db tier


                     Source target environment file

                     Execute adautocfg.sh

                    $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME/adautocfg.sh

                     Connect as apps user

                    Sqlplus apps/<Source_apps_pwd>


                   Exec the following :

                   Select node_name from fnd_nodes;

                   It will display only Target DB node.



Restore wallet information to sqlnet ifile (conditional)
Place Pending jobs on hold (Conditional)


update APPLSYS.FND_CONCURRENT_REQUESTS set HOLD_FLAG = 'Y' where PHASE_CODE  = 'P';



7      APPS Tier Cloning


7.1         Copy APPS Tier Run File System


                     Login to Target application server as applmgr user

                    Copy the apps filesystem binaries from source to destination.


Using scp command


Login to Target(ebzclone) application system using applmgr user

                    $scp –rp <ad_id>@<src_db_server>:/scratch/ebz2_runfs.tar.gz  /<stage_location>


 Note :

We need to copy this zip file under fs2 where we intially directoty.

Using sftp

Login to Target(ebzclone) application system using applmgr user

                cd <stage_location>

                ftp username@<source(ebz2) instance name>

               cd /scratch/

              mget ebz2_runfs.tar.gz

After finishing copy of backup,comeout from ftp session by entering “quit” at command prompt

Create apps filesystem directories – Only for New Instance

              $mkdir –p /u01/app/oracle/ebzclone/R122/fs1 /u01/app/oracle/ebzclone/R122/fs2

Untar apps file system

Note: In destination server Set $RUN_BASE and $PATCH_BASE based on source run and patch file system.

If run filesystem is fs2 in source instance, set same fs2 as run in destination instance
and untar.

              $export $RUN_BASE=/u01/app/oracle/ebzclone/R122/fs2

           $cd /u01/app/oracle/ebzclone/R122/fs2

           $nohup tar –xvzf  /<stage_location>/ebz2_runfs.tar.gz &

           $export PATCH_BASE= /u01/app/oracle/ebzclone/R122/fs1

                                                                               

Configure Target Apps Tier


Check the oraInst.loc file entry ,it must contain the entry for target instance


        App Tier Inventory
$cat /etc/oraInst.loc
inventory_loc=/u01/app/oracle/ebzclone/oraInventory
inst_group=oinstall


8.1         Run adcfgclone in Apps Tier

Make sure you are running adcfgclone from the same file system as your source

For example : If my run file system is in fs2 in source then i would do the below.

 - Make fs2 in target (Run file system first)

 - Make fs1 from fs2 (PAtch file system)


$ cd /u01/app/oracle/ebzclone/R122/fs2/EBSapp/comn/clone/bin
$ perl adcfgclone.pl appsTier </path/to/XML/file>

If you do not have the XML file, use the following method:

[applmgr@xxxxvebsxd03 bin]$ perl adcfgclone.pl appsTier

Enter the APPS password :

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

Target System File Edition type [run] :


Provide the values required for creation of the new APPL_TOP Context file.

Target System Hostname (virtual or normal) [xxxxVEBSXD03] :

Target System Database SID : ebzclone

Target System Database Server Node [xxxxxxx] : xxxxxx

Target System Database Domain Name [xxxxx.com] : -- Hit Enter

Target System Base Directory : /u01/app/oracle/ebzclone/R122

Target System Base Directory set to /u01/app/oracle/ebzclone/R122

Target System Current File System Base set to /u01/app/oracle/ebzclone/R122/fs2



Target System Other File System Base set to /u01/app/oracle/ebzclone/R122/fs1

Target System Fusion Middleware Home set to /u01/app/oracle/ebzclone/R122/fs2/FMW_Home

Target System Web Oracle Home set to /u01/app/oracle/ebzclone/R122/fs2/FMW_Home/webtier

Target System Appl TOP set to /u01/app/oracle/ebzclone/R122/fs2/EBSapps/appl

Target System COMMON TOP set to /u01/app/oracle/ebzcnv1/R122/fs2/EBSapps/comn

Target System Instance Home Directory [/u01/app/oracle/ebzclone/R122] :  --Hit Enter

Target System Instance Top set to /u01/app/oracle/ebzcnv1/R122/fs2/inst/apps/ebzclone_xxxxvebsxd03

Do you want to preserve the Display [xxxxvebsxd03:0.0] (y/n)  : n

Target System Display [xxxxvebsxd03:0.0] :

 Target System Root Service [enabled] :

Target System Web Administration [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] :

Enter port pool value[0] : 37 (standard port value for ebzclone instance)

-

-

UTL_FILE_DIR on database tier consists of the following directories.



1. /usr/tmp

2. /archive/ebz/inbound

3. /archive/ebz/outbound

4. /apps9/oracle_cifs_mount/operations/shipping_label

Choose a value which will be set as APPLPTMP value on the target node [2] :


 File system clean-up


                     After finishing adcfgclone in run file system,

                     Run the correct ENV file

                     cd /u01/app/oracle/ebzclone/R122/

                    . EBSapps.env  run



                    Make sure you have sourced the run file system


                    echo $FILE_EDITION

                    It should be RUN



                   Delete .env files belong to source(ebz2) instance

                   cd $APPL_TOP

                  rm –rf *ebz2*.env


Copy the Target Run file system to Patch file system:


Do the below in Target server :

fs2 - run file system
fs1- patch file system

                       cd /u01/app/oracle/ebzclone/R122/fs2/

                       cp –r EBSapp /u01/app/oracle/ebzclone/R122/fs1/

 Note :only do copy of “EBSapps” directory,No need to copy FMW_Home and inst directories.
Adcfglone will create those directories

        Run adpreclone on target run file system

 Check edition , should run file system

                             echo $FILE_EDITION

                             Execute adpreclone

                             $cd $ADMIN_SCRIPTS_HOME

                             $perl adpreclone.pl appsTier

  
         Copy run fs to patch fs
         Run adcfgclone on Patch file System(Target):


                      cd /u01/app/oracle/ebzclone/R122/fs1/EBSapp/comn/clone/bin

$echo $CONTEXT_FILE (copy the run file system context file)

perl adcfgclone.pl appsTier


  Target System File Edition type [run] : patch

  Note : It will prompt you for a context file,make sure you will give the fullpath of Run file system 
Context file  (DO NOT use the one you saved off, use the one from the RUN file system)

Location of Run System Context File: <Full patch to run fs context file>

                       -

                       -

      Target System Port Pool [0-99] : 37 if patch is fs1, 38 if patch is fs2

  After finshing adcfgclone start all the services on run file system

 cd /u01/app/oracle/ebzcnv1/R122/fs1/EBSapp/

                       .EBSapps.env run

                           echo $FILE_EDITION

                           it should be RUN


cd $ADMIN_SCRIPTS_HOME

                          ./adstrtal.sh <apps_username>/<apps_password>

  Validate the front end
  
Login into the front end using sysadmin user and perform the validate steps and validate
The application to ensure everything is fine.


Post cloning activities in R12.2 :

Stop application services


                     Go to $ADMIN_SCRIPTS_HOME

                     $ ./adstpall.sh apps/<apps_pwd>



 Reset apps & other passwords:


                      Reset sys & system password:

  $sqlplus / as sysdba

       SQL>alter profile APPS_PROFILE limit PASSWORD_VERIFY_FUNCTION null ;

                       SQL>altyer user sys identified by <newpassword>;

                       SQL>alter user system identified by <newpassword>;

   ALLORACLE

  FNDCPASS apps/<old_password> 0 Y system/system123 ALLORACLE
 <newpassword>

 SYSADMIN --> FNDCPASS apps/not2share123 0 Y system/<password> USER sysadmin

                                                 <new_password>

APPS--> FNDCPASS apps/<old_password> 0 Y system/mock2system SYSTEM APPLSYS

                                     <new password>

 Note: Oracle recommends to use AFPASSWD utility to change the passwords over 
FNDCPASS.

 SQL>alter profile APPS_PROFILE limit PASSWORD_VERIFY_FUNCTION VERIFYPASSWORD14 ;

  Change Apps password in R12.2.4 (Weblogic Console)

                      Start AdminServer using the adadminsrvctl.sh script from your RUN filesystem

                      Do not start any other application tier services.

                      Update the “apps” password in WLS Datasource as follows:

                      Log in to WLS Administration Console.

                      Click Lock & Edit in Change Center.

                      In the Domain Structure tree, expand Services, then select Data Sources.

                      On the “Summary of JDBC Data Sources” page, select EBSDataSource.

                      On the “Settings for EBSDataSource” page, select the Connection Pool tab.

                        Enter the new password in the “Password” field.

                       Enter the new  password in the “Confirm Password” field.

                       Click Save.

                       Click Activate Changes in Change Center.

                       Start all the application tier services using the adstrtal.sh script.

 Validate the changed passwords

                        Try to login with changed passwords and validate the functioning



9      FS_CLONE (Conditional)


Run the fs_clone in application instance and make sure it should be completed without errors.



cd /u01/app/oracle/ebzclone/R122/

.EBSapps.env run

echo $FILE_EDITION

it should be RUN



]$ adop phase=fs_clone



Check the log files for errors if comes and resolve them after that again run fs_clone














You cannot complete this task because one of the following events caused a loss of page data: A system failure has occurred "Front end is locked after 12.2 upgrade"

  If you have upgraded to Oracle E-Business Suite 12.2.10 Release Update Pack from Oracle E-Business Suite 12.2.6 Release Update Pack (or ea...