Friday, March 11, 2016

Oracle E-Business Suite on Oracle Cloud


Run Oracle E-Business Suite on the Oracle Cloud today!

By running Oracle E-Business Suite on Oracle Cloud, you can reduce time and cost for new projects, increase business agility, better manage growth, and increase the productivity of your global IT workforce.

LEARN HOW TO USE ORACLE E-BUSINESS SUITE ON ORACLE CLOUD

Get hands-on, step-by-step instructions in Oracle by Example (OBE) tutorials.

Tuesday, March 8, 2016

SSL Setup on EBS 12.2 Environments



1. stop the services
2. go to $INST_TOP/certs
3. If directory Apache exists, take backup of that dir
5. cp -r Apache Apache_bak
6. cd Apache
7. rm *

If Apache dir does not exist, create it under $INST_TOP/certs.

8. Create wallet under Apache dir using :

orapki wallet create -wallet . -auto_login -pwd  Welcome123
9. Update wallet by replacing  ebs.oracle.com  in the following example with  your VM host

 orapki wallet add -wallet . -dn "CN= ebs.oracle.com,OU=Unit,O=Org,L=Redwood Shores,ST=California,C=US" -keysize 1024 -self_signed -validity 3650 -pwd  Welcome123

10. Replace     with your  env context name in following command:

cp   $INST_TOP/certs/Apache/cwallet.sso $IAS_ORACLE_HOME/instances/EBS_web_/config/OHS/EBS_web_component/keystores/default            

      
cd  $INST_TOP/certs/Apache
 Please  replace   the  ebs.oracle.com  with  your  VM host .

orapki wallet export -wallet  $PWD  -dn "CN= ebs.oracle.com,OU=Unit,O=Org,L=Redwood Shores,ST=California,C=US"  -cert server.crt -pwd Welcome123

11. cd  $OA_JRE_TOP/lib/security
12. cp  cacerts cacerts_org

13. $ keytool -import -alias ApacheServer -file $INST_TOP/certs/Apache/server.crt -trustcacerts -v -keystore ./cacerts -storepass  Welcome123


Trust this certificate? [no]:  Yes
Certificate was added to keystore
14  Update the $CONTEXT_FILE with SSL values given in table below:
 Variable 
Non-SSL Value 
SSL Value 
s_url_protocol
http
https
s_local_url_protocol
http
https
s_webentryurlprotocol
http
https
s_active_webport
same as s_webport
same as s_webssl_port
s_webssl_port
not applicable
Make sure base= 4443
s_https_listen_parameter
not applicable
same as s_webssl_port
s_enable_sslterminator
#
remove the '#' to use ssl_terminator.conf
s_login_page
url constructed with http protocol and s_webport
url constructed with https protocol and s_webssl_port.
Eg. https://ebs.oracle.com:4452/OA_HTML/AppsLogin
s_external_url
url constructed with http protocol and s_webport
url constructed with https protocol and s_webssl_port
Eg. https://ebs.oracle.com:4452/OA_HTML/AppsLogin




15. Run Autoconfig on middle tier.

On DB tier :-
  1. First create  ca.crt using   server.crt file .
    cd  $ORACLE_HOME/appsutil    (   RDBMS home )
  2. mkdir  wallet
  3. cd wallet ;   and  ftp the ca.crt file  created in step 1  to this location.
  4. Run the following commands
  5. orapki wallet create -wallet $ORACLE_HOME/appsutil/wallet -auto_login -pwd Welcome123
  6. import trusted certificate using:
orapki wallet add -wallet . -trusted_cert -cert ca.crt -pwd Welcome123
Test using new URL

Create a Clean oraInventory in Release 12.2

1. Clean the current oraInventory location:

Check the oraInventory location from the /etc/oraInst.loc file
Backup and clean that directory
Customer can write down the name of all entries from the old inventory from /ContentsXML/inventory.xml to use during the creation of the new OHs

2. Add the RDBMS Oracle Home first to the new oraInventory:

Go to $ORACLE_HOME
source the environment file .env
cd $ORACLE_HOME/oui/bin
Run the following command to add the RDBMS OH to oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/11.2.0 ORACLE_HOME_NAME='12_2_DB'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.


3. Add the 10.1.2 OH from RUN filesystem to the new oraInventory:

Source the Run FS environment file
cd $ORACLE_HOME/oui/bin
Run the following command to add the 10.1.2 OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs1/EBSapps/10.1.2 ORACLE_HOME_NAME='10_1_2_fs1_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.

4. Add the FMW OHs from RUN filesystem to the new oraInventory:

4.1. /oracle_common
cd /oracle_common
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs1/FMW_Home/oracle_common ORACLE_HOME_NAME='FMW_oracle_common_fs1_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.

4.2. /webtier
cd /webtier
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs1/FMW_Home/webtier ORACLE_HOME_NAME='FMW_webtier_fs1_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.


4.3. /Oracle_EBS-app1
cd /Oracle_EBS-app1
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs1/FMW_Home/Oracle_EBS-app1 ORACLE_HOME_NAME='FMW_Oracle_EBS_app1_fs1_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.


5. Add the 10.1.2 OH from PATCH filesystem to the new oraInventory

Source the PATCH FS environment file
cd $ORACLE_HOME/oui/bin
Run the following command to add the 10.1.2 OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs1/EBSapps/10.1.2 ORACLE_HOME_NAME='10_1_2_fs1_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.



6. Add the FMW OHs from PATCH filesystem to the new oraInventory:

6.1. /oracle_common
cd /oracle_common
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs2/FMW_Home/oracle_common ORACLE_HOME_NAME='FMW_oracle_common_fs2_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.

6.2. /webtier
cd /webtier
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs2/FMW_Home/webtier ORACLE_HOME_NAME='FMW_webtier_fs2_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.


6.3. /Oracle_EBS-app1

cd /Oracle_EBS-app1
export ORACLE_HOME=PWD
cd $ORACLE_HOME/oui/bin
Run the following command to add the OH to the oraInventory:
./runInstaller -attachhome ORACLE_HOME= ORACLE_HOME_NAME=''
Example:
./runInstaller.sh -attachhome ORACLE_HOME=/u01/app/fs2/FMW_Home/Oracle_EBS-app1 ORACLE_HOME_NAME='FMW_Oracle_EBS_app1_fs2_OH'
Check the inventory.xml under /ContextXML directory and ensure the new entry is added.

5. The new oraInventory is complete.

Friday, May 29, 2015

EBS Workflow Service Components Status



Good piece of script to identify the status of the workflow components from sql prompt.
This is alternate option to see workflow service components status from OAM GUI.


Run the below SQL as apps user

col component_id format 999999
col startup_mode format a10
col component_status format a10
col component_name format a50
set linesize 125
set pagesize 25
select component_id, startup_mode,component_status,component_type,component_name from fnd_svc_components

order by component_id;

Search and Replace String across multiple files in Linux

  perl -pi -e 's/old_string/new_string/g' file_pattern

  perl -pi -e 's/temp/tmp/g' *.html
  /happy/
To correctly replace it, you would have to escape the forward slashes with the escape character (the backslash) so that the forward slashes aren't interpreted as commands. Your replacement string would need to be:
  \/happy\/

Monday, December 22, 2014

HowTo Restore The Weblogic User Password On EBS 12.2 if Lost Or Forgotten

The steps are mentioned on the EBS Setup Guide for 12.2 which can be downloaded from the link : https://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T589913.htm (12.2 Setup Guide) under the topic  "If the Admin Password of an EBS WebLogic Domain is lost or forgotten"

Also refer for more details :-
Procedure To Restore The Weblogic User Password On EBS 12.2 In Case Of Lost Or Forgotten Password (Doc ID 1949675.1)

Monday, March 10, 2014

Fusion Applications P4FA Patches

 

High levels to apply P4FA:

  1. Shutdown FMW, IDM and DB (Transaction, OID and OIM database) services
  2. Backup Environment
  3. * Apply patches to FMW Oracle Homes (excluding ATGPF/Generic and ATGPF/Database patches)
  4. * Apply patches to IDM Oracle Homes
  5. * Apply RDBMS patches to Transaction, OID and OIM ** Oracle Homes
  6. Start DB (Transaction, OID and OIM database) services
  7. Apply RDBMS patches post steps (if any) on Transaction, OID and OIM databases
  8. Start IDM Middle-tier services
  9. Apply post steps on IDM Oracle Homes (if any)
  10. Bounce IDM Middle-tier services (ONLY if any post step on IDM Oracle Homes requires OID/OIM/AUTHOHS bounce)
  11. Apply ATG/Generic patches to ATGPF Oracle Home
  12. Apply ATGPF/Database patches to ATGPF Oracle Home
  13. Start FMW services (FA, BI, and other techstack components)
  14. Apply post steps on FMW Oracle Homes (if any)
  15. Bounce FA Domains (ONLY if any post steps on FMW Oracle Homes requires domain bounce)

* can be done in parallel
** If Transaction, OID, OIM databases share same Oracle Home, then apply RDBMS patches once and perform patch post steps (if any) on all databases.

 

CLASSIFICATION OF PATCHES:

FMW_HOME=${HOME}/APPTOP/fusionapps

P4FA Directory
ORACLE_HOME to be applied
Generic ORACLE_HOME Name

ecm_bucket2
FMW_HOME/ecm

biappsshiphome
FMW_HOME/bi

wc
FMW_HOME/webcenter

odi
FMW_HOME/odi

ses
FMW_HOME/ses

fusionapps/generic
FMW_HOME/applications

pfcore
FMW_HOME/applications

osn
FMW_HOME/osn

soa
FMW_HOME/soa
OIM - IDMTOP/products/app/soa
OIM - IDMTOP/products/app/soa

suwrapper
FMW_HOME/wlserver_10.3
OID - IDMTOP/products/dir/wlserver_10.3
OIM - IDMTOP/products/app/wlserver_10.3

weblogic
FMW_HOME/wlserver_10.3
OID - IDMTOP/products/dir/wlserver_10.3
OIM - IDMTOP/products/app/wlserver_10.3

webgate
FMW_HOME/../webtier_mwhome/webgate
AUTHOHS - IDMTOP/products/ohs/webgate
WEBGATE_ORACLE_HOME

webtier
ADMIN Host - FMW_HOME/../webtier_mwhome/webtier
APPOHS - FMW_HOME/../webtier_mwhome/webtier
AUTHOHS - IDMTOP/products/ohs/ohs
OHS_ORACLE_HOME

oracle_common
FMW_HOME/oracle_common
ADMIN Host - FMW_HOME/../webtier_mwhome/oracle_common
APPOHS - FMW_HOME/../webtier_mwhome/oracle_common
OID - IDMTOP/products/dir/oracle_common
OIM - IDMTOP/products/app/oracle_common
AUTHOHS - IDMTOP/products/ohs/oracle_common
OID_COMMON_HOME
OIM - IDMTOP/products/app/oracle_common
OHS_COMMON_HOME

pltsec
OID - IDMTOP/products/dir/oid
OID_ORACLE_HOME

idm
OIM - IDMTOP/products/app/iam
OIM - IDMTOP/products/app/iam

idmlcm/generic
OID - $HOME/Middleware/Oracle_IDMLCM1 (Only for Provisioned IDM and not for tarball based IDM)

oif
OIM - IDMTOP/products/app/idm
OIM - IDMTOP/products/app/idm

atgpf/generic
FMW_HOME/atgpf

atgpf/database
adpatch FMW_HOME/atgpf

rdbms_11.2.0.3.0
Transaction DB
IDM DBs

Thursday, September 26, 2013

EBS12.2 How does Online Patching work on the application tier?

 

During Release 12.2 installation, Rapid Install will lay down two copies of the application tier file system. One of the copies will be labeled as the run file system, and the other as the patch file system. Subsequently, when a patch is applied, adop will:

    1. Synchronize the contents of the run file system to the patch file system. This happens during the prepare phase.
    2. Perform patching actions on the patch file system. This happens during the apply phase.
    3. Finally, during the cutover phase, the adop utility restarts the application tier services. The patch file system is then promoted to be the new run file system, and the old run file system becomes the patch file system for the next patching cycle.

Note that a third file system, the non-editioned file system (fs_ne), is created to store files containing data that is needed across all file systems, such as log files.

What are the phases that make up the Online Patching cycle?
The Online Patching cycle consists of the following phases:

  1. Prepare a virtual copy (patch edition) of the running application (run edition).
  2. Apply patches to the patch edition of the application.
  3. Finalize the system in readiness for the cutover phase.
  4. Cutover to the patch edition and make it the new run edition.
  5. Cleanup obsolete definitions or data to recover space.

What are the space requirements for Online Patching?
Space required on the application tier file system is approximately double that of Release 12.1.3, to support the dual file system architecture. In the database there must be sufficient space to hold a duplicate copy of any code, seed data or table columns that are patched. Refer to Oracle E-Business Suite Installation Guide: Using Rapid Install for additional guidance.

Reference :-

Oracle E-Business Suite Release 12.2: Online Patching FAQ (Doc ID 1583902.1)

Stage R12 - 12.2 Software for Installation

 

As EBS R12 - 12.2 is released officially, for installing , Download all the software 12.2  from edelivery.oracle.com.


Here are the steps to stage 12.2. software

First unzip start CD parts in the staging directory “Stage” as in this example.

cd /u01/oracle/122/Stage
unzip ../V35215-01_1of3.zip
unzip ../V35215-01_2of3.zip
unzip ../V35215-01_3of3.zip


Go to startCD/Disk1/rapidwiz/bin

cd /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin

Launch buildStage.sh script which will stage the software. It prompts for
the downloaded the zips locations , All the zip files need to be downloaded to
the same location.

./buildStage.sh
                Build Stage Menu
------------------------------------------------------
1.     Create new stage area
2.     Copy new patches to current stage area.
3.     Display existing files in stage TechPatches.
4.     Exit menu
Enter your choice [4]: 1


         Rapid Install Platform Menu
------------------------------------------------------
1.    Oracle Solaris SPARC (64-bit)
2.    Linux x86-64
3.    IBM AIX on Power Systems (64-bit)
4.    HP-UX Itanium
5.    Exit Menu
Enter your choice [5]: 2


/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jre/Linux_x64/1.6.0/bin/java
-classpath /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/emocmutl.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/ewt-3_4_22.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/share-1_1_18.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/jnls.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/ACC.JAR:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/netcfg.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/ojdbc14.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/OraInstaller.jar:/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../jlib/java
oracle.apps.ad.rapidwiz.util.StageBuilder /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin


Please enter the directory containing the zipped installation media:
/u01/oracle/122/


Unzipping V35805-01_1of2.zip
Unzipping V35803-01_2of3.zip
Unzipping V35231-01_3of5.zip
Unzipping V35806-01_3of3.zip
Unzipping V35812-01.zip
Unzipping V35215-01_3of3.zip
Unzipping V35215-01_1of3.zip
Unzipping V35231-01_5of5.zip
Unzipping V35810-01.zip
Unzipping V35809-01.zip
Unzipping V35803-01_3of3.zip
Unzipping V35813-01.zip
Unzipping V35811-01.zip
Unzipping V35806-01_2of3.zip
Unzipping V35231-01_4of5.zip
Unzipping V35802-01.zip
Unzipping V35806-01_1of3.zip
Unzipping V35231-01_1of5.zip
Unzipping V37515-01_3of6.zip
Unzipping V37515-01_6of6.zip
Unzipping V37515-01_1of6.zip
Unzipping V35805-01_2of2.zip
Unzipping V35804-01_2of2.zip
Unzipping V35230-01_1of2.zip
Unzipping V35231-01_2of5.zip
Unzipping V37515-01_5of6.zip
Unzipping V37515-01_4of6.zip
Unzipping V35803-01_1of3.zip
Unzipping V35804-01_1of2.zip
Unzipping V35230-01_2of2.zip
Unzipping V35807-01.zip
Unzipping V35215-01_2of3.zip
Unzipping V37515-01_2of6.zip
Unzipping V35808-01.zip
Applying one-off patches
All files have been unzipped.
Done Unzipping shiphome ...
StageBuilder will now stage the tech patches for Linux_x64...
Copying one-off patches to shiphome
/u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../unzip/Linux_x64/unzip -o /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../Xpatches/Linux_x64.zip
-d /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches
Archive:  /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../Xpatches/Linux_x64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16303726/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16303726/p16303726_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14123213/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14123213/p14123213_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/13923995/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/13923995/p13923995_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14751895/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14751895/p14751895_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16163946/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16163946/p16163946_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14207902/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14207902/p14207902_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/15967134/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/15967134/p15967134_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16438289/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16438289/p16438289_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/13931044/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/13931044/p13931044_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16342486/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16342486/p16342486_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14398795/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14398795/p14398795_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/12951696/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/12951696/p12951696_112030_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/12942119/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/12942119/p12942119_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14698700/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/14698700/p14698700_112030_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16587934/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16587934/p16587934_112030_Linux-x86-64.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16105745/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16105745/p16105745_112030_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16040940/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/DB/16040940/p16040940_112030_Linux-x86-64.zip
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/13583235/p13583235_1036_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14825718/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14825718/p14825718_10123_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14353879/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14353879/p14353879_10123_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14614795/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14614795/p14614795_101231_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16209520/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16209520/p16209520_10123_GENERIC.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16275529/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16275529/p16275529_10105_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14597598/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14597598/p14597598_1036_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14577216/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14577216/p14577216_101231_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16784403/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16784403/p16784403_101232_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14386347/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14386347/p14386347_111160_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16199894/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/16199894/p16199894_111160_Generic.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14374587/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/14374587/p14374587_10123_GENERIC.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/10152652/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/10152652/p10152652_10123_LINUX.zip
   creating: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/11669923/
extracting: /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin/../../../../TechPatches/MiddleTier/11669923/p11669923_10123_GENERIC.zip
Done Copying additional patches
Verifying stage area...
Directory /u01/oracle/122/Stage/TechInstallMedia is valid
Directory /u01/oracle/122/Stage/TechPatches/DB
is valid
Directory /u01/oracle/122/Stage/TechPatches/MiddleTier
is valid
Directory /u01/oracle/122/Stage/EBSInstallMedia/AppDB
is valid
Directory /u01/oracle/122/Stage/EBSInstallMedia/Apps
is valid
Directory /u01/oracle/122/Stage/EBSInstallMedia/AS10.1.2
is valid
Directory /u01/oracle/122/Stage/TechInstallMedia/database
is valid
Directory /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin
is valid
Directory /u01/oracle/122/Stage/startCD/Disk1/rapidwiz/bin
is valid
Stage area verified.
Press enter to continue...


When staging get completed, the directory structure looks like below.


EBSInstallMedia  startCD  TechInstallMedia  TechPatches

Monday, June 10, 2013

What's new in EBS 12.2?

New or changed technology-related features in EBS 12.2 include:

  • Streamlined installation:
    • Use of native installation tools for Oracle Fusion Middleware and Oracle Database technology stack components.
    • Option for installing EBS 12.2 on to existing database servers.
    • Capability of installation into existing Real Application Clusters environments.
    • Database deployment on Automatic Storage Management (ASM) and other file systems.
  • Support for online patching.
  • Use of Oracle WebLogic Server instead of AutoConfig for many (but not all) of AutoConfig's previous functions.
  • Use of Oracle WebLogic Server instead of Oracle Containers for Java (OC4J).
  • Integration between Oracle Enterprise Manager 11g Fusion Middleware Control and Oracle Applications Manager to monitor EBS environments with Oracle WebLogic Server technology.
  • Enhanced internationalization features, including new languages and calendars, and improved diagnostics.
  • Enhanced user interface features for Navigator menu, progress indicators, and table sorting.
  • Integration with AutoVue Document Print Services to print file attachments.
  • Undo and copy OA Framework personalizations.
  • Support for Mobile Safari on Apple iPads.
  • Enhanced Integrated SOA Gateway functionality for use with Oracle SOA Suite 11g and Oracle EBS Adapter.
  • Enhanced Workflow Worklist notification and management features.

For complete details for individual EBS products, see:

Concurrent Processing - CP Analyzer for E-Business Suite

The Concurrent Processing Analyzer is a Self-Service Health-Check script which reviews the overall Concurrent Processing Footprint, analyzes the current configurations and settings for the environment providing feedback and recommendations on Best Practices.

  • This is a non-invasive script which provides recommended actions to be performed on the instance it was run on and can be run at any time.  For production instances, always apply any changes to a recent clone to ensure an expected outcome.
Benefits
  • Immediate Analysis and Output of Concurrent Environment
    • E-Business Applications Concurrent Processing Analyzer Overview
      • Total Purge Eligible Records in FND_CONCURRENT_REQUESTS
      • E-Business Suite Version
      • Concurrent Processing Database Parameter Settings
      • Applied ATG Patches
      • Known 1-Off Patches on top of Rollups
    • E-Business Applications Concurrent Request Analysis
      • Long Running Reports During Business Hours
      • Elapsed Time History of Concurrent Requests
      • Requests Currently Running on a System
      • FND_CONCURRENT_REQUESTS Totals
      • Running Requests
      • Total Pending Requests by Status Code
      • Count Pending Regularly Scheduled/Non Regularly-Scheduled Requests
      • Count of Pending Requests on Hold/Not on Hold
      • Listing of Scheduled Requests
      • Listing of Pending Requests on Hold
      • Listing of Pending Requests Not on Hold
      • Volume of Daily Concurrent Requests for Last Month
      • Identify/Resolve the Pending/Standby Issue, if Caused by Run Alone Flag
      • Tablespace Statistics for the fnd_concurrent tables
    • E-Business Applications Concurrent Manager Analysis
      • Concurrent Managers Active and Enabled
      • Concurrent Manager Processes by Workshift
      • Active Manager for Applications that are not Installed/Used
      • Total Target Processes for Request Managers (Excluding Off-Hours)
      • Request Managers with Incorrect Cache Size
      • Concurrent Manager Request Summary by Manager
      • Check Manager Queues for Pending Requests
      • Check the Configuration of OPP
  • Identifies Concurrent System Setup and configurations
  • Identifies and recommends Concurrent Best Practices
  • Easy to add Tool for regular Concurrent Maintenance
  • Execute Analysis anytime to compare trending from past outputs
Audience
  • DBA's / System Administrator's should run the script and review the output
  • Pending the output, one may interact with the the following End-User types to resolve the identified Opportunity Improvement areas:
    • Apps Access (Toad or SQL Developer)
    • Filesystem access (apps logfiles) $APPLCSF/$APPLLOG
    • SYSADMIN access permissions
  • Output usually will be reviewed by a group of people pending the problems
  • This script was designed for Concurrent Processing in 11.5.x and later.

Where to Run Script & How to fix Items Identified in Script:
You may run the script on a Production environment as it's non-invasive.  We recommend fixing items identified from the output first in a clone of production to test/verify the expected outcome.

For script and more information, Concurrent Processing - CP Analyzer for E-Business Suite [ID 1411723.1]

Tuesday, March 8, 2011

Cloning SSO-Enabled Environments in E-Business Suite


This is already discussed in Steven Chan's Blog article http://blogs.oracle.com/stevenChan/2006/05/11/ and much of this note is a straight copy from this article.  Please review this blog article in it's entirety before proceeding.

If you're willing to experiment a bit, the following are general guidelines to point you in the right direction.  Some customers and Oracle Consultants have used the following approaches to get the job done but have reported that there was some trial-and-error involved.

These are neither detailed nor comprehensive instructions.  The following should be attempted only by system administrators who have a solid understanding of the principles outlined in Metalink Note 261914.1.

If you're going to experiment with these approaches, I strongly recommend that you take all sensible precautions, including backing up your environments at multiple stages, taking careful notes, and doing things in small, incremental steps to control your risk.

There is no single stop, supported or documented method to create a clone of your eBiz instance when integrated with SSO.   Please use this note with caution and make sure you thoroughly test any procedure you decide to use to ensure it fits with all aspects of your specific setup.

1- Use Rapid Clone to create a clone of your E-Business Suite, including the application-tier and database-tier.
   For 11i, please use:
     Note 230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
  
   For R12 ,please use:
     Note 406982.1   Cloning Oracle Applications Release 12 with Rapid Clone

2- In the  newly-cloned E-Business Suite instance, set the APPS_SSO_LDAP_SYNC profile option to "Disabled" at the site level (since there's no new Oracle Internet Directory instance to synchronize with yet).

3 -  In your newly-cloned E-Business Suite instance, unlink all E-Business Suite users that were linked to the original Oracle Internet Directory 10g users (i.e. where FND_USER.USER_GUID is populated), since the those old links are no longer valid. Those E-Business Suite users will need to be linked to their corresponding accounts in the as-yet non-existent new Oracle Internet Directory instance.

To Unlink EBS users, you should execute the following Command for each individual user (For both 11i and R12):

$FND_TOP/patch/115/sql/fndssouu.sql

See Note 429375.1 for more information on this utility

4 -  In your newly-cloned E-Business Suite instance, remove all reference to the original OID/SSO instance

Use the “removereferences” to cleanup the previous registration information of SSO & OID

For R12 this is described in Note 376811.1 "Section 3: Remove References"

For 11i :  Note 233436.1  "Appendix D:  Advanced Configuration - Manual SSO/OID Registration" - Option 6

5 -  Create a fresh install of Single Sign-On and Oracle Internet Directory 10g on your new server.

6 - Assuming that you enabled bidirectional provisioning between the E-Business Suite and Oracle Internet Directory, do one of the following (but not all three):

a) Redo your bulkload from the E-Business Suite into Oracle Internet Directory.
   On Release 12, please refer to "System Administrator's Guide - Security" on Section 6 (Oracle Single Sign-On Integration )

Then  Reregister your E-Business Suite environment using the Bidirectional Provisioning Profile, and enable the APPS_SSO_AUTO_LINK_USER profile option, and set the profile option APPS_SSO_LDAP_SYNC back to Enabled at site level.

b) Export your LDAP namespace from your original Oracle Internet Directory instance into an LDIF file, and then import the LDIF file into the new Oracle Internet Directory instance. Reregister your E-Business Suite environment using the Bidirectional Provisioning Profile, and (assuming that the Oracle Internet Directory accounts are identical to the E-Business Suite accounts) enable the APPS_SSO_AUTO_LINK_USER profile option, and set the profile option APPS_SSO_LDAP_SYNC back to Enabled at site level.

c) Connect the original Oracle Internet Directory instance to your new Oracle Internet Directory instance via a connector, synchronizing the namespaces. Reregister your E-Business Suite environment using the Bidirectional Provisioning Profile, and (assuming that the Oracle Internet Directory accounts are identical to the E-Business Suite accounts) enable the APPS_SSO_AUTO_LINK_USER profile option, and set the profile option APPS_SSO_LDAP_SYNC back to Enabled at site level.

Is it Possible to Clone an SSL Enabled E-Business Suite Middle Tier?

The Rapidclone utility does not support like for like cloning of an SSL enabled E-business suite middle tier.
Note 230672.1 Cloning Oracle Applications Release 11i with Rapid Clone
Note 406982.1 Cloning Oracle Applications Release 12 with Rapid Clone

The problem can be broken down into 3 issues

1:- File system changes.

The location of the SSL files on the clone is different to that from the source. From the bug we can see the following were not the same between source and target.

s_frmWalletDir
s_web_ssl_directory
s_web_ssl_keyfile
s_web_ssl_certfile
s_web_ssl_certchainfile

2:- SSL Port is wrong in the clone.

s_webssl_port - Gets Defaulted to 443, ideally it should take Apache Port given during adcfgclone run.

3:- SSL certificates are the same on the clone as they are on source.

This might be a security issue depending on your security requirements.

However Rapidclone will create a clone of an SSL enabled middle tier, but the target will require additional configuration to allow it to function correctly. To progress the issue further you must decide if

A:- You want the middle tier clone to be SSL enabled.

Re-implement SSL on the clone following the note below.

Note 123718.1 11i: A Guide to Understanding and Implementing SSL for Oracle Applications

B:- You want the middle tier clone to be HTTP only.

Remove the SSL configuration added in

Note 123718.1 11i: A Guide to Understanding and Implementing SSL for Oracle Applications

Should I Implement a Shared Appl Top? And if so How?

1:- Is it recommended to implement a shared APPL_TOP?

Both single APPL_TOP and shared APPL_TOP are supported. Full details of the requirement can be found in

Note.233428.1 Sharing the Application Tier File System in Oracle Applications Release 11i
Note.384248.1 Sharing The Application Tier File System in Oracle E-Business Suite Release 12

There is no official Oracle support document that would recommend a shared APPL_TOP over a normal APPL_TOP. The DBA and the business need to decide if the costs and factors involved in implementing a shared file system, outweigh the benefits (reduced patching time etc)

However there is a very good blog article by the Oracle E-Business suite integrations team that explains the choices and benefits of using a shared APPL_TOP.

Choosing a Shared File System for Oracle E-Business Suite
http://blogs.oracle.com/stevenChan/2009/07/choosing_an_ebs_shared_file_system.html

There is also some good information in

Reducing Patching Downtimes via Shared Apps File Systems
http://blogs.oracle.com/stevenChan/2007/05/reducing_patching_downtimes_vi.html

2:- What are the requirements from the Backend?

This is an area that Oracle support is unable to help you with, other than tell you that you need to have a storage system that can mount drives to multiple servers. Full detail of Oracle's position on this can be found in

Choosing a Shared File System for Oracle E-Business Suite
http://blogs.oracle.com/stevenChan/2009/07/choosing_an_ebs_shared_file_system.html

The issue generally come down to how much money you have for the storage system. NFS for example is very cheap but the NFS mount can be classed as a single point of failure (e.g. NFS mount goes down, all E-business suite middle tiers go down).

How to Gather Statistics on Custom Schemas for Ebusiness Suite 11i and R12?



To gather statistics for Oracle Applications Ebusiness Suite 11i or R12 modules you should use the concurrent programs 'Gather Schema Statistics', 'Gather Table Statistics', or run 'FND_STATS'.

In order to run the programs 'Gather Schema Statistics', 'Gather Table Statistics', or run 'FND_STATS'  for a custom schema, the schema must be registered with the Application.

To register an schema with Oracle Applications, follow the steps listed in
Note 176852.1 - Integrating Custom Applications with Oracle Applications

If the custom schema is not registered, it will not show up in the LOV for schema selection for the mentioned concurrent programs.

You can run the following statement to see which schemas are currently registered with the Ebusiness Suite:


select   distinct(upper(oracle_username)) sname
from     fnd_oracle_userid a, fnd_product_installations b
where    a.oracle_id = b.oracle_id
order by sname;

Friday, June 18, 2010

Compile forms in Release 12

Follow the instructions below to compile your forms in Release 12
1:- Log into the forms tier.
2:- Set the applications environment
3:- Ensure that the $FORMS_PATH includes $AU_TOP/resource and $AU_TOP/resource/stub, for example

echo $FORMS_PATH

/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/resource:
/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/resource/stub

4:- Compile the form
a:- If you are using forms customizations (CUSTOM.pll) then run the command below to compile the form.

frmcmp_batch.sh module=<path to fmb file> userid=APPS/APPS output_file=<full path to fmx output file> module_type=form compile_all=special

For eg:-

frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/XXX.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/12.0.0/forms/US/XXX.fmx module_type=form compile_all=special

b:- If you are NOT using forms customizations, then run the command below to compile the form.

frmcmp_batch.sh module=<path to fmb file> userid=APPS/APPS output_file=<full path to fmx output file> module_type=form

For example..

frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/XXX.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/12.0.0/forms/US/XXX.fmx module_type=form

Shared Application File System in R12 and 11i

E-Business suites (EBS) 11i and R12 both support the sharing of the Applications Tier File System. Sharing a file system in EBS involves sharing a volume between 2 or more physical servers. In a shared Application Tier File System (ATFS) implementation, the application services can be configured to run (utilize CPU and memory) on any server sharing the ATFS simply by changing some context file variables via OAM, running Autoconfig and restarting the services. This process is detailed in the following notes:

R12: Note.384248.1: Sharing the Application Tier File System in Oracle E-Business Suite Release 12
11i:   Note.233428.1: Sharing the Application Tier File System in Oracle Applications 11i

Some key concepts of sharing ATFS:

  • Each server sharing the ATFS will have its own context file
  • Certain context file variables dictate which application services start and run on which server(s)
  • Certain context file variables dictate how AD Utilities will behave on each server
The Unified Applications Tier File System (UATFS)
The term "Unified Applications Tier File System" (UATFS) came along with R12 as a new feature. Oracle Development decided it would be beneficial to always install all the files needed on every server in a given R12 installation, even if the server was only to host some of the Application services. Even though this term was coined for an R12 feature, it still applies to some 11i file systems. A Unified Applications File System essentially means that the file system contains all the files required to support all 4 base service groups in E-Business Suite:
  • Web
  • Forms
  • Admin (Not a true process or service as the other 3 are. The "admin" component dictates which server administers the application database objects and therefore has the needed files for that task.)
  • Concurrent Processing (Reports)
Again, all versions of R12 are always installed with UATFS as delivered by Rapid Install. However in 11i only single node-installations are unified at install time. In 11i in order to achieve a unified file system from a multi-node installation, a merge of the file systems must be performed. This is the only supported manner in which to achieve a unified file system from an installation which was originally multi-node. APPL_TOP Merging in 11i is accomplished by Note 233428.1, Section 4, "Merging existing APPL_TOPs into a single APPL_TOP". Because R12 is always unified there is not an APPL_TOP merge process in R12.
Some Non-Typical Scenarios for Shared File Systems in 11i
In 11i it is also possible to share an ATFS even if the file system is not unified or complete; i.e., it only supports 1, 2 or 3 of the 4 core services. For example 11i can have an ATFS which only has the files for Forms and Web. That ATFS can then be shared with another server for Forms / Web services only. The other core services, Admin and Concurrent would then have its own ATFS on another server or servers. This would be done for some advanced topology configurations like load-balancing or perhaps a standby Web / Forms server and would minimize the footprint of the ATFS. Because the ATFS in this example is not unified, the ATFS of the Forms/Web servers could never host the Concurrent Processing or Admin services without first being merged with an ATFS which has the necessary Concurrent Processing and Admin files. So while in 11i it is possible to share a non-unified ATFS, it would not be a typical configuration. A typical configuration is sharing 1 unified ATFS for amongst multiple servers. The advantages of this non-typical example would be:
  • Smaller Footprint for the ATFS on each volume/disk (however the overall combined footprint would be larger)
  • Better performance from the shared volume/disk, as there are 2 instead of 1

The disadvantages would be:
  • Must maintain multiple ATFS's
  • Patches have to be applied multiple times 
  • Cloning is more difficult as 2 ATFS's must be cloned
For disk performance reasons, you could implement a similar strategy in R12, for example sharing 2 volumes (VOL1, VOL2) amongst 4 servers: 2 web/forms servers accessing only VOL1 and the 2 CCM/Admin servers accessing only VOL2. Those 2 disks would each have a unified ATFS in R12, where the same configuration in 11i the file systems could be partial or unified.

For more information please refer :

Explanation of Context Variables for Shared Application File System in R12 and 11i [ID 1070152.1]



References
NOTE:233428.1 - Sharing the Application Tier File System in Oracle Applications Release 11i
NOTE:384248.1 - Sharing The Application Tier File System in Oracle E-Business Suite Release 12
NOTE:406558.1 - Configuring Applications Node Services in Oracle E-Business Suite Release 12
NOTE:415385.1 - On a R12 Multi-Node Install -- Why do all Middle Tiers run all Services?