Steps to Create Disk partition of RAW disks in ASM with 64Bit

Login as root user and perform.

To create disk partition with 64 bit to improve performance –

[root@l-ebdb-01 ~]# fdisk -u /dev/sdd

The number of cylinders for this disk is set to 16970.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (63-272629759, default 63): 128
Last sector or +size or +sizeM or +sizeK (128-272629759, default 272629759):
Using default value 272629759

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

[root@l-ebdb-01 ~]# partprobe

[root@l-ebdb-01 ~]# fdisk -lu /dev/sdd

Disk /dev/sdd: 139.5 GB, 139586437120 bytes
255 heads, 63 sectors/track, 16970 cylinders, total 272629760 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 128 272629759 136314816 83 Linux

Advertisements

Oracle Access Manager Integration With Oracle E-Business Suite R12

Installation and Integration Instructions for oracle Access manager

(OAM) with Oracle E-business Suite R12.1.3

Oracle Single Sign-On Server (OSSO) and Oracle Access Manager (OAM) are two Single Sign On Solutions from Oracle. Oracle Access Manager is the preferred solution going forward, and forms the basis of Oracle Fusion Middleware 11g. OSSO is no longer being developed, is not ported to Oracle WebLogic Server.

Environment Name:  OAM, R12TEST Machine:  fusionapps.xxxxx.com, r12test.xxxxx.com

OAM Pre-Installation High Level Steps

1. Install 11gR2 database.

2. Install Oracle Weblogic server 11g on OAM residing server.

3. Install RCU, OID 11g

4. Integrate OID with E-Business Suite R12 instance.

OAM High Level Installation & Integration Steps

1. Install OAM, Integrate with OID & define Policies.

2. Install Oracle Weblogic server 11g on E-Business suite server.

3. Install Oracle Webgate 11g.

4. Install Oracle Accessgate 11g; deploy it on E-Business suite Weblogic server.

5. Integrate OID with MS Active Directory

Pre-reqs for 11g Oracle Home, Weblogic, OID & OAM installation:

Hardware Requirements

                     Parameter                                               Recommended Value

Memory                                                                  4GB

Disk Space                                                             40GB

Space in /tmp directory                                        >150MB

Swap Space                                                           >4GB

Software Requirements

                         Type                                                   Required Packages

                       

                            OS Packages binutils-2.15.92.0.2
compat-libstdc++-33-3.2.3 for x86_64
compat-libstdc++-33-3.2.3 for i386
elfutils-libelf-0.97
elfutils-libelf-devel-0.97
gcc-3.4.5
gcc-c++-3.4.5
glibc-2.3.4-2.19 for x86_64
glibc-2.3.4-2.19 for i686
glibc-common-2.3.4
glic-devel-2.3.4 for x86_64
glic-devel-2.3.4 for i386
libaio-0.3.105 for x86_64
libaio-0.3.105 for i386
libaio-devel-0.3.105
libgcc-3.4.5 for x86_64
libgcc-3.4.5 for i386
libstdc++-3.4.5 for x86_64
libstdc++-3.4.5 for i386
libstdc++-devel-3.4.5 for x86_64
libstdc++-devel-3.4.5 for i386
make-3.80
openmotif-2.2.3
openmotif21-2.1.30-11.RHEL4.4
sysstat-5.0.5

Kernel Parameters                                              soft  nofile  4096

hard  nofile  4096

Checking the Software Requirements

To ensure that the system meets these requirements, follow these steps:

[oraapps@fusionapps ~]$ uname -a

Linux fusionapps.xxxxx.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux

[oraapps@fusionapps ~]$ rpm -qa binutil*

binutils-2.17.50.0.6-9.el5

binutils220-2.20.51.0.2-5.29.el5

[oraapps@fusionapps ~]$ rpm -qa compat-lib*

compat-libgcc-296-2.96-138

compat-libcom_err-1.0-7

compat-libstdc++-33-3.2.3-61

compat-libstdc++-33-3.2.3-61

compat-libf2c-34-3.4.6-4

compat-libstdc++-296-2.96-138

compat-libcom_err-1.0-7

[oraapps@fusionapps ~]$ rpm -qa elf*

elfutils-libs-0.137-3.el5

elfutils-libelf-devel-0.137-3.el5

elfutils-libelf-devel-static-0.137-3.el5

elfutils-libelf-0.137-3.el5

elfutils-libelf-0.137-3.el5

elfutils-0.137-3.el5

elfutils-libelf-devel-static-0.137-3.el5

elfutils-libelf-devel-0.137-3.el5

[oraapps@fusionapps ~]$ rpm -qa gcc*

gcc44-gfortran-4.4.6-3.el5.1

gcc-objc-4.1.2-52.el5_8.1

gcc-objc++-4.1.2-52.el5_8.1

gcc-java-4.1.2-52.el5_8.1

gcc44-4.4.6-3.el5.1

gcc-c++-4.1.2-52.el5_8.1

gcc-gnat-4.1.2-52.el5_8.1

gcc44-c++-4.4.6-3.el5.1

gcc-gfortran-4.1.2-52.el5_8.1

gcc-4.1.2-52.el5_8.1

[oraapps@fusionapps ~]$ rpm -qa glibc*

glibc-2.5-81.el5_8.4

glibc-common-2.5-81.el5_8.4

glibc-devel-2.5-81.el5_8.4

glibc-headers-2.5-81.el5_8.4

glibc-devel-2.5-81.el5_8.4

glibc-2.5-81.el5_8.4

[oraapps@fusionapps ~]$ rpm -qa libai*

libaio-devel-0.3.106-5

libaio-0.3.106-5

libaio-0.3.106-5

libaio-devel-0.3.106-5

[oraapps@fusionapps ~]$ rpm -qa libgcc*

libgcc-4.1.2-52.el5_8.1

libgcc-4.1.2-52.el5_8.1

[oraapps@fusionapps ~]$ rpm -qa libstdc*

libstdc++-4.1.2-52.el5_8.1

libstdc++44-devel-4.4.6-3.el5.1

libstdc++-devel-4.1.2-52.el5_8.1

libstdc++-4.1.2-52.el5_8.1

libstdc++-devel-4.1.2-52.el5_8.1

[oraapps@fusionapps ~]$ rpm -qa make*

make-3.81-3.el5

[oraapps@fusionapps ~]$ rpm -qa openmotif*

openmotif-2.3.1-2.el5

openmotif22-2.2.3-18

[oraapps@fusionapps ~]$ rpm -qa sysstat*

sysstat-7.0.2-11.el5

Configuring Kernel Parameters

[oraapps@fusionapps ~]$ cat /etc/sysctl.conf

# Kernel sysctl configuration file for Red Hat Linux

#

# For binary values, 0 is disabled, 1 is enabled.  See sysctl(8) and

# sysctl.conf(5) for more details.

# Controls IP packet forwarding

net.ipv4.ip_forward = 0

# Controls source route verification

net.ipv4.conf.default.rp_filter = 1

# Do not accept source routing

net.ipv4.conf.default.accept_source_route = 0

# Controls the System Request debugging functionality of the kernel

kernel.sysrq = 0

# Controls whether core dumps will append the PID to the core filename

# Useful for debugging multi-threaded applications

kernel.core_uses_pid = 1

# Controls the use of TCP syncookies

net.ipv4.tcp_syncookies = 1

# Controls the maximum size of a message, in bytes

kernel.msgmnb = 65536

# Controls the default maxmimum size of a mesage queue

kernel.msgmax = 65536

# Controls the maximum shared segment size, in bytes

kernel.shmmax = 4294967295

# Controls the maximum number of shared memory segments, in pages

kernel.shmall = 4294967296

#Added newly

kernel.sem  = 256 32000 100 142

kernel.shmmni = 4096

fs.file-max = 6815744

net.ipv4.ip_local_port_range = 9000 65500

net.core.rmem_default           = 524288

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 16777216

net.ipv4.ipfrag_high_thresh     = 524288

net.ipv4.ipfrag_low_thresh      = 393216

net.ipv4.tcp_rmem               = 4096 524288 16777216

net.ipv4.tcp_wmem               = 4096 524288 16777216

net.ipv4.tcp_timestamps         = 0

net.ipv4.tcp_sack               = 0

net.ipv4.tcp_window_scaling     = 1

net.core.optmem_max             = 524287

net.core.netdev_max_backlog     = 2500

sunrpc.tcp_slot_table_entries   = 128

sunrpc.udp_slot_table_entries   = 128

fs.aio-max-nr = 1048576

[oraapps@fusionapps security]$ cat limits.conf

# /etc/security/limits.conf

#

#Each line describes a limit for a user in the form:

#

#<domain>        <type>  <item>  <value>

#

#Where:

#<domain> can be:

#        – an user name

#        – a group name, with @group syntax

#        – the wildcard *, for default entry

#        – the wildcard %, can be also used with %group syntax,

#                 for maxlogin limit

#

#<type> can have the two values:

#        – “soft” for enforcing the soft limits

#        – “hard” for enforcing hard limits

#

#<item> can be one of the following:

#        – core – limits the core file size (KB)

#        – data – max data size (KB)

#        – fsize – maximum filesize (KB)

#        – memlock – max locked-in-memory address space (KB)

#        – nofile – max number of open files

#        – rss – max resident set size (KB)

#        – stack – max stack size (KB)

#        – cpu – max CPU time (MIN)

#        – nproc – max number of processes

#        – as – address space limit

#        – maxlogins – max number of logins for this user

#        – maxsyslogins – max number of logins on the system

#        – priority – the priority to run user process with

#        – locks – max number of file locks the user can hold

#        – sigpending – max number of pending signals

#        – msgqueue – max memory used by POSIX message queues (bytes)

#        – nice – max nice priority allowed to raise to

#        – rtprio – max realtime priority

#

#<domain>      <type>  <item>         <value>

#

#*               soft    core            0

#*               hard    rss             10000

#@student        hard    nproc           20

#@faculty        soft    nproc           20

#@faculty        hard    nproc           50

#ftp             hard    nproc           0

#@student        –       maxlogins       4

*  hard nofile 65536

*  soft nofile 65536

# End of file

RDBMS Installation Steps

Download the 11gR2 software, extract the files and run command runInstaller.

[oraapps@fusionapps database]$ ls

doc  install  response  rpm  runInstaller  sshsetup  stage  welcome.html

[oraapps@fusionapps database]$ ./runInstaller

De-select the security updates via My Oracle Support “Check Box” and click next.

Click “Yes”…

Check “Create and configure a database” radio button and click “next”…

Select “Server Class” radio button and click “Next”…

Select “Single instance database installation” radio button and click “Next”…

Select “Advanced Install” and Click “Next”…

Select “English” and Click “Next”…

Select “Enterprise Edition” & Click “Next”…

Enter path for “Oracle Base” & location for Oracle Home or Software installation and Click Next…

Select “General Purpose” button & Click Next…

Enter “Global Database name” & Click Next…

Check Memory Allocation under “Memory” tab & make necessary changes as per your requirement and click on “Character Set” tab

Select “Use Unicode (AL32UTF8)” character set radio button as required for Fusion Middleware installation & Click next.

Click next.

Click next.

Select “DO not enable automated backups” radio button & click next.

Select “Use same password for all accounts”, enter the password & click next.

Check Groups & click next.

Verification process is in progress.

Click “Finish”.

Installation process is in progress.

Click “Retry”.

DBCA process is in progress.

Click “OK”.

Click “OK”.

Login to server from backend with root user and run “root.sh” script in oracle home location.

Enter “n” for 3 options.

Installation process is in progress.

RDBMS Installation was successful. Now configure Listener using “NETCA”.

 

Weblogic 11g Server Installation Steps on OAM server

Install JDK 1.7 and export the java path.

[oraapps@fusionapps ~]$ export PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/home/oraapps/bin:/bin:/usr/java/jdk1.7.0_21/jre/bin

Extract Weblogic 11g (10.3.6) software and run the jar file.

[oraapps@fusionapps ~]$ java -jar wls1036_generic.jar

Click “Next”.

Click “Next”.

Enter full path for Middleware home installation & Click “Next”.

Uncheck the “Oracle Security Updates” option & Click Next. Click “Yes” in “Are You Sure” pop window.

Click “Yes” in Pop-up window.

Select “Typical” Install type & Click next.

The entire required configurations are fine, click next.

Check “JDK” installed in the server & click next.

Verify path and location of installation are as defined & click next.

Click Next.

Installation is in-progress.

Installation completed successfully.

Creating Domain in Weblogic, run “config.sh” in $MW_HOME/bin:

$/apps/topps/oracle/Middleware/wlserver_10.3/common/bin/config.sh

Select “Create a new Weblogic domain” option & click next.

Select “Generate a domain configured automatically to support” option & click next.

Enter Domain name and verify the location. Click next.

Enter the user name & password. Click next.

Select “Production Mode” and “Available JDK” options & click next.

Select “Administration Server” and “Managed Servers, Clusters and Machines” options & click next.

Enter Administration server name, port number & click next.

Click Next.

Click Next.

In Configure Machines window click on Unix Machine tab and enter Admin server name & click next.

Click Next.

Verify configuration & click “Create”.

Domain creation completed successfully, save the details & click “Done”.

Config.sh will not start the services automatically. Start the Admin Server manually.

$/apps/topps/oracle/middleware/user_projects/domains/IDMDomain/bin/startWebLogic.sh

 

RCU Installation Steps

Extract and launch the RCU utility from <RCU_HOME>/bin/rcu

[oraapps@fusionapps bin]$ pwd

/apps/topps/stage/naveen/rcu/rcuHome/bin

[oraapps@fusionapps bin]$ ./rcu

Click next.

Enter database type, hostname, service name, port number & “sys” user password. Click ok on RCU pre-requisites pop-window.

Enter new prefix to be used and select DEV_MDS, DEV_IAU, DEV_OPSS under “AS Common Schemas” and ODS, DEV_OAM under “Identity Management” options & click next.

Click “Ok”.

Select “Use same password for all schemas” option, enter password & click next.

Click next.

Click “Ok” for creation any tablespaces required while creating schemas.

Click “Ok” on RCU creating tablespaces pop-window.

Click “Create”.

RCU create process is in-progress.

RCU successfully completed. Click “Close”.

OID Installation Steps

Extract OID 11.1.1.6.0 software and run “runInstaller”.

Click next.

Select “Install Software – Do Not Configure” option (configuration is done separately) & click next.

Check all Pre-requisites status is 100% & click next.

Check the installation path, enter “Home Directory” name & click next.

Uncheck oracle security updates option & click “Yes” in pop-up window.

Click “Install”.

Installation completed. Click next.

Login to server from back-end with “root” user & run the script mentioned in pop-up window.

Installation completed successfully, Click “Finish”.

 Run the configuration wizard.

[oraapps@fusionapps bin]$ pwd

/apps/topps/oracle/Middleware/OID/bin

[oraapps@fusionapps bin]$ sh config.sh

Click next.

Select “Create New Domain” option, enter “User Name”, “User Password”, “Domain Name” & Click next.

Enter the “Instance Location” and “Instance Name” & click next.

Uncheck the Oracle Security update option & click “Yes” on pop-up window.

Select “Oracle Directory Services Components” & click next.

Check “Auto Port Configuration” option & click next.

Enter “LDAP v3 Name Space”, Oracle Virtual Directory Administrator User name, password & click next.

Username: cn=orcladmin

Password: xxxxx123

LDAP v3 Name Space: dc=xxxxx, dc=com

Select “Use Existing Schema”, provide the “Connect String”, Schema password & click next.

Enter “Realm”, Administrator password & click next.

Realm: dc=xxxxx, dc=com

Username: cn=orcladmin

Password: xxxxx123

Click “Configure”.

Configuration process is in-progress.

Configuration completed successfully, Click “Finish”.

OID Integration with E-Business Suite Steps

We will now integrate our OID installed on “fusionapps.xxxxx.com” server with Oracle E-Business Suite R12.1.3 running on “r12test.xxxxx.com” server.

Login to r12test.xxxxx.com server and perform below steps –

[applmgr@r12test ~]$ $FND_TOP/bin/txkrun.pl -script=SetSSOReg -registerinstance=yes

You are registering ORACLE HOME only.

Enter the host name where Oracle iAS Infrastructure database is installed ? fusionapps.xxxxx.com

Enter the LDAP Port on Oracle Internet Directory server ? 3060

Enter SSL LDAP Port on Oracle Internet Directory server ? 3131

Enter the Oracle Internet Directory Administrator (orcladmin) Bind password ?

Enter Oracle E-Business apps database user password ?

*** Log File = /u01/oracle/r12vis/inst/apps/r12test_r12test/logs/appl/rgf/TXK/txkSetSSOReg_Wed_May_29_12_43_21_2013.xml

Beginning input parameter validation for Oracle Home Instance registration.

Input parameter validation for Oracle Home Instance registration completed.

BEGIN ORACLE HOME INSTANCE REGISTRATION:

Oracle Home Instance preferences stored successfully.

Oracle Home Instance registered successfully.

End of /u01/oracle/r12vis/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkSetSSOReg.pl : No Errors encountered

Oracle Access Manager 11g Installation Steps

Unzip the OAM 11g software and execute “runInstaller” script.

Click “Next”.

Select “Skip Software Updates” option & click next.

Check all Prerequisites status is 100% & click next.

Verify the installation path, give oracle home directory name & click next.

Click “Install”.

Installation is in-progress.

Installation completed, click “Finish”.

Run Configuration Wizard for creating domain in weblogic for OAM

Execute $MW_HOME/oracle_common/common/bin/config.sh, for example:

[oraapps@fusionapps ~]$ /oracle/middleware/oracle_common/common/bin/config.sh

Click “Next”.

Select “Generate a domain configured automatically to support the following products” option:

Check 1. Oracle Access Management – 11.1.2.0.0 [OAM]

2. Oracle Enterprise Manager – 11.1.2.0 [oracle_common]

3. Oracle Platform Security Service – 11.1.2.0 [OAM]

4. Oracle JRF – 11.1.1.0 [oracle_common]

Click Next.

Enter Domain name, verify locations & click next.

Enter Administrator username and password & click next.

Domain Name: OAMDomain

Username: weblogic

Password: xxxxx123

Select “Production Mode” and “Available JDKs” & click next.

Provide service name, schema name, passwords for OAM Infrastructure, OPSS Schema & click next.

Check Component schemas status is “Passed” & click next.

Select “Administration Server”, “Managed Servers, Clusters and Machines”, “Deployments and Services” & Click next.

Enter Administration server name, port number & click next.

Enter Managed Server name, port number & click next.

Click next.

Click next.

Check the deployments listed for both AdminServer and Managed Server & click next.

Click next.

Check configuration details & click “Create”.

Domain creation completed successfully, click “Done”.

Configure the Database Security Store for OAM by performing below steps –

[oraapps@fusionapps ~]$ /apps/topps/oracle/middleware/oracle_common/common/bin/wlst.sh /apps/topps/oracle/middleware/oam_home/common/tools/configureSecurityStore.py -d /apps/topps/oracle/middleware/user_projects/domains/oam_domain -m create -c IAM -p xxxxx123

Check “Create operation has completed successfully” is the final output.

Configuring OAM with OID & Policy Creation Steps

Create a dedicated Oracle Internet Directory identity store for Oracle E-Business Suite

 

You are not required to change Oracle Access Managers primary identity store for Oracle E-Business Suite integration. If you do not wish to change Oracle Access Manager’s primary identity store to Oracle Internet Directory, follow the steps below to define a dedicated identity store for Oracle Internet Directory and an Oracle E-Business Suite Authentication Scheme.

The Authentication Scheme and LDAP Authentication Module that we define in this section are identical to the default Authentication Scheme and LDAP Authentication Module with the exception that we point to OID as identity store.

Logon to the OAM Console

http://fusionapps.xxxxx.com:7003/oamconsole

Enter username “weblogic” & “xxxxx123” password.

Click on “System Configuration” tab, go to “Data Sources”, and select “User Identity Stores” & click on “+” symbol on top to create a new store.

Enter all the details & click “Test Connection”.

Click “Ok” on Connection to the User Identity Store Successful Pop-up window.

Click “Apply”.

Create Authentication Module

Select “System Configuration” tab, go to “Authentication Modules” sub-menu & select “LDAP Authentication Module”.

Click on “+” button on top to create Authentication module.

Enter Name & Identity store details and click “Apply”.

Create Authentication Scheme

 

Go to “Policy Configuration” tab, select “Authentication Schemes” menu & click on “+” button on top to add authentication scheme.

Enter all the details & click “Apply”.

Set Authentication Scheme

Select “Policy Configuration” tab, go to “Application Domains” sub-menu & Click “Search”.

Go to “Authentication Policies” tab & click on “Protected Resource Policy”.

On “Protected Resource Policy” tab, select the newly created “Authentication Scheme” created in earlier step & click “Apply”.

Configure Response Headers

Oracle E-Business Suite integration with Oracle Access Manager uses two specific response headers. Configure Oracle Access Manager to set these response headers as follows.

Add Response Headers to the Authentication Policies –

In “Policy Configuration” tab go to “Application Domains” sub-menu & select “Authentication Policy”.

Select “Protected Resource Policy”, click “Responses” tab.

Click on “+” symbol to add new Response headers. Enter “Type”, “Name” & “Value” details, click on “Add”.

Click “Apply”.

Add Response Headers to the Authorization Policies –

Repeat the same steps performed for adding Response Headers in “Authentication Policy” & click “Apply”.

Configure OAM to support long URLs

Long URLs may exceed a cookie limit on your Internet browser. Configure Oracle Access Manager to support long URLs by changing the serverRequestCacheType from COOKIE to FORM in Oracle Access Manager Configuration file $DOMAIN_HOME/config/fmwconfig/oam-config.xml:

<Setting Name=”serverRequestCacheType” Type=”xsd:string”>FORM</Setting>

Weblogic 11g Server Installation Steps on E-Business Suite server

Extract Weblogic 11g (10.3.6) 32-bit software and run the jar file.

[applmgr@r12test ~]$ java -jar wls1036_generic.jar

Click “Next”.

Click “Next”.

Uncheck “Security updates”, click “Next” & Click “Yes” on pop-up window.

Select “Typical” & click “Next”.

Provide the Middleware home path & click “Next”.

Click “Next”.

Click “Done”.

Create a New Domain

Select “new Weblogic domain” option & click “Next”.

Select “Generate” option & click “Next”.

Enter name, path details & click “Next”.

Enter username, password “xxxxx123” & click “Next”.

Select “Production Mode”, JDK’s & click “Next”.

Select “Administration Server”, “Managed Servers, Clusters and Machines” options & click “next”.

Enter Name, port number & click “Next”.

Click “Next”.

Select “Unix Machine” tab, enter name and other details, & click “Next”.

Assign “AdminServer” & click “Next”.

Click “Create”.

Domain creation completed successfully.

Install Oracle Webtier Utilities 11g, Webgate 11g & Access Gate Steps

Install Webtier Utilities 11g (11.1.1.7.0)

Unzip webtier utilities zip file and run “runInstaller”

Click “Next”

Select “Skip Software Updates” option & click “Next”.

Select “Install Software – Do Not Configure” option & click “Next” (we will configure in later part).

Check all “Prerequisite Checks” status is successful.

Enter path, name & click “Next”.

Uncheck “security updates” option, click “Yes” in pop-up window & click “Next”

Click “Install”

Installation is in-progress

Webtier installation completed successfully.

Configure Webtier utilities by running config.sh script in Webtier home

Click “Next”

Select “Oracle HTTP Server” option & click “Next”

Enter location, instance name & click “Next”

Select option – 2, create a configuration file for port & click “Save”

Click “Next”

Uncheck “Security Updates” option, click “Yes” on pop-up window & click “Next”

Click “Configure”

Login to server from backend using “root” user and execute “oracleRoot.sh” script & click “Ok”

Webtier utilities configuration is completed successfully, click “Next”

Click “Finish”.

Install OHS Webgate 11g (11.1.2)

Unzip OHS Webgate software zip file and run “runInstaller”

Click “Next”

Check all “Prerequisite Checks” status is successful & click “Next”

Enter path, name & click “Next”

Click “Install”

Installation completed successfully, click “Next”

Click “Finish”

Configure & Register Oracle Webgate 11g

Configure Webgate on the Webtier

cd /u01/oracle/topps/middleware/webgate_home/webgate/ohs/tools/deployWebGate

./deployWebGateInstance.sh \

-w /u01/oracle/topps/middleware/webtier_home/instances/instance1/config/OHS/ohs1 \

-oh /u01/oracle/topps/middleware/webgate_home

cd /u01/oracle/topps/middleware/webgate_home/webgate/ohs/tools/setup/InstallTools

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/u01/oracle/topps/middleware/webtier_home/lib:/u01/oracle/topps/middleware/webgate_home/ohs/lib

./EditHttpConf \

-w /u01/oracle/topps/middleware/webtier_home/instances/instance1/config/OHS/ohs1 \

-oh /u01/oracle/topps/middleware/webgate_home

Create Webgate agent in OAM

Login to OAM console, navigation “System Configuration” à “Access Manager” à SSO Agents à OAM Agents à Click “+” symbol to create new OAM 11g Webgate Agent

Enter all the details, click “Apply”

Name: WebgateOHS11g

Access Client Password: xxxxx123

Register the Webgate Agent with Oracle Access Manager

  1. Change directories to /apps/topps/oracle/middleware/OAM/oam/server/rreg/client/rreg/input.
  2. Create a new file named EBS_OAM11gRequest_short.xml to serve as a parameter file to the   oamreg tool. Use the example file below.

<?xml version=”1.0″ encoding=”UTF-8″?> <!– Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved.

NAME: OAM11GRequest_short.xml – Template for OAM 11G Agent Registration Request file (Shorter version – Only mandatory values – Default values will be used for all other fields)

DESCRIPTION: Modify with specific values and pass file as input to the tool.

–>

<OAM11GRegRequest>

<serverAddress>http://fusionapps.xxxxx.com:7003</serverAddress&gt;

<hostIdentifier>WebgateOHS11g</hostIdentifier>

<agentName>WebgateOHS11g</agentName>

<agentBaseUrl>http://r12test.xxxxx.com:8001</agentBaseUrl&gt;

<logOutUrls><url>/logout</url></logOutUrls>

</OAM11GRegRequest>

Replace {oam_admin_server_host} with the fully qualified name for your OAM host.

Replace {oam_admin_server_port} with the weblogic administration server port.

Replace {Identifier for your WebGate} within both the <hostIdentifier> and <agentName> elements to a string that identifies your webgate, for example use the hostname for your WebGate. Note that if you are installing multiple WebGates on a single machine, this name needs to be unique for each WebGate.

Replace {webgatehost} and {port} with the fully qualified hostname and port for the WebTier that you’ve associated with WebGate in the previous step.

Use the element <logOutUrls> as is in the example above.

  1. Create a new file named ebs.oam.conf to serve as URIs file to the oamreg tool. Use the example file below.

##################################################################

# Copyright (c) 2009, 2011, Oracle and/or its affiliates. All rights reserved.

#

# This is a configuration file, to be used with the OAM Config Tool, for

# configuring policies in OAM in order to facilitate Single Sign On.

#

# Protected URIs:-

# A Protected URI (resource) implies that an user must be authenticated

# before he could access that resource. Upon accessing a protected uri, the

# user would be redirected to the OAM login page for authentication.

# Subsequently, upon successful authentication, he would be redirected to the

# original requested resource.

#

# Public URIs:-

# A Public URI (resource), on the contrary, implies that a user be allowed

# access to that resource without authentication.

#

# This file essentially contains a list of protected and public URIs belonging

# to an Application.

#

# Please refer to the documentation of OAM Config Tool for anything related to

# the OAM Config tool’s usage and the documentation of OAM for anything

# related to OAM in general.

#

##########################

# File format description

##########################

# 1. Any line beginning with ‘#’ is considered a comment and would be ignored

# 2. Likewise any empty line or any line beginning with ‘ ‘ (space) would be

# ignored

# 3. All the Protected URIs must be listed followed by the key-word:

# “protected_uris”.

# 4. All the Public URIs must be listed followed by the key-word: “public_uris”

#

# Note that Public URIs are optional. But you need to have at least one

# Protected URI listed

#

#

########################

#Product Name: E-Business Suite

########################

###########################

protected_uris

###########################

/ebsauth_r12test

/index.html

###########################

public_uris

###########################

/ebsauth_r12test/style/

/ebsauth_r12test/ssologin

/ebsauth_r12test/ssologout.do

/ebsauth_r12test/ssologout_callback

/public/oacleanup.html

/public/index.html

Note, you will be using the same string “ebsauth_r12test” later in this document as context root for installation of Oracle E-Business Suite AccessGate.

  1. Set the following environment variables in the /apps/topps/oracle/middleware/OAM/oam/server/rreg/client/rreg/bin/oamreg.sh script

OAM_REG_HOME – Set this variable to point to the absolute path to your <RREG_Home>.

JAVA_HOME – Set this variable to the absolute path where Java/JDK is installed on your machine.

  1. Change directories to /apps/topps/oracle/middleware/OAM/oam/server/rreg/client/rreg
  1. Run the following command:

[oraapps@fusionapps rreg]$ ./bin/oamreg.sh inband input/IDMOracle_OAM11GRequest_short.xml

  1. Copy the generated registration artifacts to your WebTier

After successfully executing the registration tool oamreg, you will find registration artifacts named ObAccessClient.xml, and optionally a file named cwallet.sso, depending on the mode you chose to register with, generated in directory:

/apps/topps/oracle/middleware/OAM/oam/server/rreg/client/rreg/output/WebgateOHS11g

Copy these files to your WebGate instance configuration directory on your WebTier:

$MW_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1/webgate/config/

  1. Re-start the Webtier services

Configure Oracle E-Business Suite

Follow the steps in this section to configure Oracle E-Business Suite for single sign-on integration with Oracle Access Manager, using Oracle E-Business Suite AccessGate.

Oracle E-Business Suite AccessGate is deployed as a standalone J2EE application on a WebLogic server and is protected by Oracle Access Manager. Oracle E-Business Suite AccessGate creates an E-Business Suite session based on a valid Oracle Access Manager session.

Create WebLogic Domain for Oracle E-Business Suite AccessGate

Use the Configuration Wizard to create a WebLogic Domain and managed server for Oracle E-Business Suite AccessGate.

cd $WLHOME/common/bin
./config.sh

In the Configuration Wizard, specify the following

Create a new WebLogic Domain, click “Next”

Generate a domain configured automatically to support the following products & Click “Next”:

Oracle JRF – 11.1.1.0 [oracle_common]

Enter Domain name: eag_domain & Click “Next”

Enter username, password & click next. Ex. Weblogic, xxxxx123

Select Startup mode, JDK & click next

Select Administration Server, Managed Server, Deployments options & click next.

Enter Admin server name, port number & click next.

Add managed server & click next – Name: eag_server, Port: 7003

Click next.

Click next

Verify all deployments for Admin server, managed server & click next.

Click Create.

Creating domain is completed successfully, click done.

Deploy Oracle E-Business Suite AccessGate

a.    Create Installation Directory

In the Fusion Middleware Home of your WebLogic Server installation, create following subdirectory structure for E-Business AccessGate.

$MW_HOME/appsutil/accessgate/r12test

b.    Download and extract Oracle E-Business Suite AccessGate

Download Oracle E-Business Suite AccessGate available from Patch 13704814 and unzip it to $MW_HOME/appsutil/accessgate/r12test. For example:

mkdir -p $MW_HOME/appsutil/accessgate/r12test
cd $MW_HOME/appsutil/accessgate/r12test
unzip p13704814_R12_GENERIC.zip

The patch contains the following files, all of which are installed independently from Oracle E-Business Suite:

  • fndauth.war – the Oracle E-Business Suite AccessGate Java application
  • fndext.jar – the Oracle E-Business Suite Software Development Kit for Java library, which enables communication between external application servers and the Oracle E-Business Suite database
  • files to automate the process of creating a data source and deploying the Oracle E-Business Suite AccessGate web application:
    • txkEBSAuth.xml – an ant script
    • fndauth_deployment_plan.tmp – a deployment plan template file
  • LogConfig.properties – a sample file, which may be used to set external logging levels (refer to My Oracle Support Knowledge Document 1077460.1, Troubleshooting Oracle Access Manager and Oracle E-Business Suite AccessGate, for more information)
  • samplecleanup.html – a sample HTML file, which may be used for cleaning up Oracle E-Business Suite sessions and other application resources when implementing centralized logout
  • A README file (which points back to this document).
c.    Copy oacleanup.html to WebTier

Copy the samplecleanup.html from $MW_HOME/appsutil/accessgate/r12test/sample to the /public directory that you created on your WebTier in section. Verify your WebTier, and rename the file to oacleanup.html.

$ORACLE_INSTANCE/config/OHS/ohs1/htdocs/public/oacleanup.html

Access the page from your browser:

http://r12test.xxxxx.com:80/public/oacleanup.html

You should be able to access this test page without authentication, because we specified this page in the URIs file during WebGate registration with Oracle Access Manager as public resource. At this point you will only see an empty page. We will use this URL when deploying E-Business Suite AccessGate in the next step. We will edit this file later, in section, Configuring Centralized Logout.

d.    Copy library

Copy the file $MW_HOME/appsutil/accessgate/r12test/fndext.jar to your $DOMAIN_HOME/lib directory. For example:

cd $MW_HOME/appsutil/accessgate/r12test
cp fndext.jar $MW_HOME/user_projects/domains/eag_domain/lib

Restart the Oracle WebLogic Server processes. This allows the Oracle WebLogic Server to include fndext.jar on the classpath during startup.

e.    Generate DBC file

Use the AdminDesktop utility to generate a DBC file that will be used for creating a connection pool and data source for Oracle E-Business Suite AccessGate.

For example:

java oracle.apps.fnd.security.AdminDesktop apps/apps CREATE \
NODE_NAME=r12test.xxxxx.com \
[IP_ADDRESS=<IP address of external application server>] \
DBC=$FND_SECURE/r12test.dbc

The utility will generate a dbc file, for example r12test_R12TEST.xxxxx.COM.dbc. Copy this file to the directory where you installed Oracle E-Business Suite AccessGate in the previous step. For example:

cp r12test_R12TEST.xxxxx.COM.dbc $MW_HOME/appsutil/accessgate/r12test

f.      Deploy Accessgate on Weblogic Managed Server (eag_server) Using “ant” Script

ant -f txkEBSAuth.xml \

-DuseDefaults=true \

-Dwlshosturl=r12test.xxxxx.com:7001 \

-Dwlsuser=weblogic \

-DdataSourceName=r12test \

-DasadminPassword=xxxxx123 \

-DdbcFile=/u01/oracle/topps/middleware/appsutil/accessgate/r12test/r12test_R12TEST.xxxxx.COM.dbc \

-DserverName=eag_server \

-DdeploymentName=ebsauth_r12test \

-DfndauthWarFile=/u01/oracle/topps/middleware/appsutil/accessgate/r12test/fndauth.war \

-DplanPath=/u01/oracle/topps/middleware/appsutil/accessgate/r12test/plan/Plan.xml

Check & Confirm that end output of ant script is “BUILD SUCCESSFUL”.

g.    Verify Oracle E-Business Suite AccessGate deployment

Logon to WebLogic Administration Console:

http://r12test.xxxxx.com:7001/console

In the WebLogic Administration Console, navigate to eag_domain > Environment > Servers, and verify that the Oracle E-Business Suite AccessGate managed server “eag_server” is running on the specified port, for example port 7002.

Navigate to eag_domain > Deployments, and verify that the Oracle E-Business Suite AccessGate application named “ebsauth_r12test” is deployed, with State: Active and Health: OK.

Navigate to Services > DataSources, and verify that the DataSource that you created during deployment, for example “r12test” exists, and is targeted to your managed server, for example eag_server. Click on the data source to review its settings.

  • In the Connection Pool tab, observe it has the correct values for Properties user and dbcFile that you specified during deployment in parameters -DasadminUser and -DdbcFile respectively.
  • In the Monitoring tab, observe that the data source is enabled and running.

Verify that you can access following Oracle E-Business Suite AccessGate URL from your browser, for example:

http:// r12test.xxxxx.com:7002/ebsauth_r12test/ssologout_callback

You should see an empty page at this point.

Redirect HTTP Server to WebLogic Server for Oracle E-Business Suite AccessGate

Configure the HTTP server on which Webgate is running to act as a proxy for authentication requests for Oracle E-Business Suite resources. After a request for authentication is successfully handled by Webgate, the request will be processed by the Oracle E-Business Suite AccessGate application that is deployed on your WebLogic Server instance.

On your Oracle HTTP Server, locate the file mod_wl_ohs.conf file in your $ORACLE_INSTANCE/config/OHS/ohs1 directory.

Modify the file and include the configuration to redirect HTTP server requests to your WebLogic Server. For example:

<IfModule mod_weblogic.c>
WebLogicHost r12test.xxxxx.com
WebLogicPort 7002
</IfModule>

<Location /ebsauth_r12test>
SetHandler weblogic-handler
</Location>

Restart your HTTP Server

Verify that you can access following Oracle E-Business Suite AccessGate resource via your HTTP server and WebGate from your browser, for example:

http://webgatehost.example.com:7778/ebsauth_myEBS/ssologout_callback

You should be able to access this test page without authentication, because we specified the ssologout_callback resource in the URIs file during WebGate registration with Oracle Access Manager as public resource.

Your HTTP server will now act as a proxy and your Oracle E-Business Suite AccessGate application will process the request.

You should see an empty page at this point.

 

Configure Centralized Logout

When logging out of an application protected by Oracle Access Manager, the host and domain cookies created by Oracle Access Manager are removed, which forces a user to re-authenticate the next time he accesses a protected resource. However, this process does not clean up sessions or remove cookies specific to partner applications, such as Oracle E-Business Suite. The process of logging out must invalidate all sessions for Oracle Access Manager, Webgate, and Oracle E-Business Suite. To ensure that these cookies are cleared when a single sign-on session is terminated, you must configure Oracle Access Manager and Oracle E-Business Suite AccessGate to initiate a callback that will clean up these sessions. Without this, a user who terminates his single sign-on session may still be able to access Oracle E-Business Suite or even create a new Oracle E-Business Suite session.

Follow the steps in this section to configure centralized logout and clean up any active Oracle E-Business Suite sessions upon logout.

Configure Cleanup for Logout from Oracle E-Business Suite

On your Webtier, locate the file oacleanup.html that you copied during Oracle E-Business Suite AccessGate installation to the /public subdirectory on your htdocs root directory.

$ORACLE_INSTANCE/config/OHS/ohs1/htdocs/public/oacleanup.html

Set your Context Root

Set your context as follows.

Find the following line:

<script type=”text/javascript” src=’/CONTEXT_ROOT/ssologout_callback?mode=cleanup’></script>

Replace CONTEXT_ROOT with the value of the context root for any deployment of Oracle E-Business Suite AccessGate protected by this Webgate. For example:

<script type=”text/javascript” src=’/ebsauth_r12test/ssologout_callback?mode=cleanup’></script>

Update Oracle E-Business Suite

Download and apply the Oracle E-Business Suite FND patches listed in the table below:

Release

Patch Number
12.1.3 Patch 12387976, Patch 14196434

3.9.6              Set Oracle E-Business Suite profile options

 

Profile

Level

Value

FND: Desktop Nodes allowed (FND_SERVER_ DESKTOP_USER) User <comma separated list of external nodes for which IP restriction is required>For example: R12TEST, r12test.xxxxx.com column NODE_NAME in the fnd_nodes table for the desktop nodes.Set this option at the user level for the user with the Apps Schema Connect role.
Application Authenticate Agent (APPS_AUTH_AGENT) Site  http://r12test.xxxxx.com:80/ebsauth_r12test/
Applications SSO Type
(APPS_SSO)
Site SSWA w/SSO
Applications Single Sign On Hint Cookie
(APPS_SSO_HINT_COOKIE_NAME)
Site <blank> (null)There should be no value here, if there is a value such as ‘ORASSO_AUTH_HINT’ remove it and save the new empty value.

 

Test Single Sign-On with Oracle E-Business Suite

You have completed integrating Oracle E-Business Suite with Oracle Access Manager 11.1.2 using Oracle E-Business Suite AccessGate.

Test single sign-on integration now.

Logon to Oracle E-Business Suite

http://r12test.xxxxx.com:8001/OA_HTML/AppsLogin

You will be re-directed to your OAM single sign-on page. Login using valid OID user credentials. After successful authentication, you will be re-directed to your Oracle E-Business Suite home page.

OID INTEGRATION WITH MICORSOFT ACTIVE DIRECTORY

Parameters for OID server

set proper environments variables as given below –

export WLS_HOME=/apps/topps/oracle/middleware/user_projects/domains/oid_domain

export ORACLE_SID=oam

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_HOME/opmn/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/oraapps/bin

alias cdo=”cd $ORACLE_HOME”

echo “Use the command cdo to change directory to the $ORACLE_HOME”

alias cdi=”cd $ORACLE_INSTANCE”

echo “Use the command cdi to change directory to the $ORACLE_INSTANCE”

alias cdw=”cd $WLS_HOME/bin”

echo “Use the command cdw to change directory to the $WLS_HOME”

set -o vi

Verify that your account will let you communicate with the Active Directory Server

[oraapps@fusionapps ~]$ ldapbind -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=administrator,cn=users,dc=inablr,dc=com” -w “xxxxx@1234”

bind successful

[oraapps@fusionapps ~]$ ldapbind -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=oambind,ou=OAM_USERS,dc=inablr,dc=com” -w “xxxxx@1234”

bind successful

  

Verify that you can read the ‘container’ of directory entries you wish to sync:

ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D administrator@inablr.com -w xxxxx@1234 -b “” -s base “objectclass=*” highestCommittedUSN

[oraapps@fusionapps ~]$ ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D administrator@inablr.com -w xxxxx@1234 -b “” -s base “objectclass=*” highestCommittedUSN

highestCommittedUSN=231484

[oraapps@fusionapps ~]$ ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D oambind@inablr.com -w xxxxx@1234 -b “” -s base “objectclass=*” highestCommittedUSN

highestCommittedUSN=229759

Verify that you can read an entry within the ‘container’ of directory entries you wish to synch:

ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=administrator,cn=users,dc=inablr,dc=com” -w “xxxxx@1234” -b “CN=Users,DC=inablr,DC=com” -s base “objectclass=*”

ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=administrator,cn=users,dc=inablr,dc=com” -w “xxxxx@1234” -b “CN=oamtestuser,CN=Users,DC=inablr,DC=com” -s base “objectclass=*”

ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=oambind,ou=OAM_USERS,dc=inablr,dc=com” -w “xxxxx@1234” -b “CN=Users,DC=inablr,DC=com” -s base “objectclass=*”

ldapsearch -h WIN-988S0O12DPI.inablr.com -p 389 -D “cn=oambind,ou=OAM_USERS,dc=inablr,dc=com” -w “xxxxx@1234” -b “CN=oamtestuser,CN=Users,DC=inablr,DC=com” -s base “objectclass=*”

Configuration Setup on OID Node

 Login to Oracle Diresctory Services Manager, URL http://fusionapps.xxxxx.com:7005/odsm

Enter Username: cn=orcladmin

Password: xxxxx123

Click on “Connect to a Directory” à go to “OID – OID – OID Connection”

Enter Username: cn=orcladmin

Password: xxxxx123

Click “Connect”.

Create the AD-OID integration profile and setup the synchronization

a.            Launch the FMW Enterprise Manager Console and login with weblogic user.

http://fusionapps.xxxxx.com:7002/em

Enter username: weblogic

Password: xxxxx123

b.            Expand your domain and Navigate to Identity and Access and select DIP

 

c.         From the DIP Server drop down list select Administration, then Synchronization Profiles

d.         Using the navigation path, create a new DIP Sync profile with a name.
For Example we used AdminProfile as the integration profile name.
in this window you’ll be asked to enter the AD details: WIN-988S0O12DPI.inablr.com

e.            For the attribute Use DIP-OID as Source or Destination , you need to select the option Destination if you are using import (AD to OID) sync or select Source option if you are using Export (OID to AD) sync

f.             Source type select Active Directory (MS) from the drop down next type.

g.            After Providing the above mentioned details in the general tab click on Test Connection Tab, If the provided values are correct you’ll see the Information dialogue saying that
“Test Passed.Connection Successful”
If the values provided for AD are wrong in the General tab , when you click on the Test Connection, you will get an Error dialogue saying Authentication Failure ,Make sure that you
provide the correct values and get connection Successful to move Further.

h.            Then Click on “OK” to save the profile.

i.              select the “AdminProfil”e profile from the list of available
profiles and click on “Edit”.

j.             Select the “Mapping” tab and configure mapping

k.            Configure Domain Rules

l.              Click on Create option, You’ll get a Add Mapping Rule Window ,
in that Select the Source Container DN and OID container DN from the lookup windows provided and click on OK.

Click “Ok”.

Click “Cancel”.

Enter into “Test Mode”.

Click “Next”.

Click “Test”.

Check “Test Passed” is the output.

m.           Then Click on “OK” to save the profile.

n.            Select the “OAM_USERS” profile from the list of available
profiles and click on Edit.

o.            Select the Mapping tab and configure mapping

p.            Configure Domain Rules

q.            Click on Create option, You’ll get a Add Mapping Rule Window ,
in that Select the Source Container DN and OID container DN from the lookup windows provided and click on OK.

r.             Validate / re-Validate mapping until you have no errors, warnings are OK.

s.             Skip Exclusion Rules

t.          Configure Attribute Rules. Be sure to click OK after editing mapping rules to save the
changes so that it is in sync for command line validation.

Perform Ldapsearch for DIP profile created

 ldapsearch -h fusionapps.xxxxx.com -p 3060 -D cn=orcladmin -w xxxxx123 -b “cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory” -s sub “objectclass=*”

Check DIP Status

dipStatus -h fusionapps.xxxxx.com -p 7005 -D weblogic

Bootstrap the users using the command line tool

syncProfileBootstrap -h fusionapps.xxxxx.com -port 7005 -D weblogic -profile AdminProfile -lp 5

Check Bootstrap status using DIP Tester from the Enterprise Manager User Interface

Check Bootstrap status from command line

 

Verify Synchronization

 

Enable Profile

Add a user in Active Directory & verify that user is created in OID.

Check using ldap search command from backend.

ID Issue Resolution
1 Oracle Net Configuration Assistant Failed Configure listener using “netca” manually
2 RCU -6107 Init Param pre-requisite failure Increase “open_cursors” parameter value from 300 to 500.
3 OAMSSA-06252: The Policy Store Is Not Available Apply Solution provided in note id: 1491920.1
4 Error: Failed to initialize security store. Apply Solution provided in note id: 1491920.1
5 SEVERE: Exception encountered: RemoteAgentRegistrationException. Install and Configure Webgate & Accessgate on same server where e-business is running or the same domain in which e-business suite is running.

FND_LOBS_CTX index rebuilding on FND_LOBS..!

Issue:
FND_LOBS_CTX is an index on FND_LOBS table.
As per the Metalink Doc ID 396803.1 and ID 397757.1 we performed below work around:
1. Take a snapshot of the original state of the fnd_lobs entries for comfort sake:

select
FILE_FORMAT,
count(*)
from
fnd_lobs
group by FILE_FORMAT;

2. Set the file_format column of all rows other than FND_HELP so that they won’t get indexed:

update fnd_lobs
set FILE_FORMAT = ‘IGNORE’
where NVL(PROGRAM_NAME,’NULL’) != ‘FND_HELP’ ;

commit;

3. Most versions of aflobbld.sql, as written, will only rebuild the FND_LOBS_CTX index if the status of the index is invalid or missing. To force the rebuilding of the index we may first have to drop it.

Check the status of the fnd_lobs_ctx index. If it is valid, then drop it.

select status
from all_indexes
where owner=’APPLSYS’
and index_name=’FND_LOBS_CTX’
and table_name=’FND_LOBS’;

If this returns a status of “valid”, then “drop index applsys.fnd_lobs_ctx force”

4. Run aflobbld.sql. This takes two parameters; the name of the applsys schema and the name of the apps schema.
Typically “@aflobbld.sql applsys apps”.

5. The reasonably recent versions of fnd_gfm contain the function “set_file_format” which you can use to reset the values of the FILE_FORMAT column, based on the FND_MIME_TYPES table using the following update:

update fnd_lobs
set file_format = fnd_gfm.set_file_format(file_content_type);

commit;

You can verify the success of the above update by comparing the following reiteration to the previous result of step 1:

select
FILE_FORMAT,
count(*)
from
fnd_lobs
group by FILE_FORMAT;

But the aflobbld.sql script mentioned above in the 4th step was hanging over for more than 24 hours (it is supposed to complete in half an hour or less than that) ….

Below is the workaround you can apply to resolve the fnd_lobs_ctx index rebuild issues:

Fix:

First I followed,
My FND_LOBS size was 15 GB. I took the following solution to finally fix this issue:
a.
Take backup by using following script, this backup will be faster than whole FND_LOBS table backup Create table applsys.fnd_lobs_ddmmyyyy as select file_id, rowid “custom_rowid”, file_format from applsys.fnd_lobs;

b.
Make sure records before changing BINARY/binary => IGNORE
SQL> select FILE_FORMAT, count(*) from fnd_lobs group by FILE_FORMAT;

c.
update fnd_lobs set file_format = ‘IGNORE’ where FILE_FORMAT = ‘binary’ or FILE_FORMAT = ‘BINARY’;
commit;

The main point is to set the FILE_FORMAT to IGNORE for any file that should not be included in the FND_LOBS_CTX index.

d.
Drop the INPROGRESS index ‘FND_LOBS_CTX’ forcefully if it exists
Drop index applsys.fnd_lobs_ctx force;

e.
Stop the apps services and bounce the database to free up all the client sessions
Make sure no one connects to the database.

f.
Execute aflobbld.sql from OS terminal with session level sql trace enabled:
sqlplus apps/
SQL> @$FND_TOP/sql/aflobbld.sql applsys apps

g.
After the script is exit which may take 30 mins to 2 hours, please start the services
and make sure iHelp and corresponding search is working fine

h.
If that is working fine, restore the records from backup table to FND_LOBS whichwe changed to speed up index creation.

update (select fl.file_format ffo,flb.file_format ffb
from applsys.fnd_lobs fl , applsys.FND_LOBS_[ddmmyyyy] flb
where fl.file_id = flb.file_id)
set ffo=ffb;

upon confirmation and comparison of previous data, issue

commit;

Export/import process for R12 with 10g

Section 1: Prepare the source system

This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database.

Apply prerequisite patches
Ensure that you have applied steps 1 and 2 in Section 1 of the Oracle E-Business Suite Release 12 with Oracle Database 11g Release 1 (11.1.0) Interoperability Notes if you are importing an E-Business Suite Release 12.0 into 11.1.0, Oracle E-Business Suite Release 12.1 with Oracle Database 11g Release 1 (11.1.0) Interoperability Notes if you are importing an E-Business Suite Release 12.1 into 11.1.0, or Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2.0) Interoperability Notes if you are importing an E-Business Suite Release 12.x into 11.2.

When performing the AutoConfig prerequisite instructions, ensure that steps 3.1 and 3.2.1 of the Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 document are completed. The other steps in 3.2 are not necessary as they will be done at the target side.

Apply the Applications consolidated export/import utility patch
Apply patch 13023290 to the source administration server node. This patch provides several SQL scripts that facilitate exporting and importing an Applications database instance.

Create a working directory
Create a working directory named expimp in the source system that will contain all generated files and scripts required to complete this section. As an example,

$ mkdir /u01/expimp
Generate target database instance creation script aucrdb.sql
The target database instance must be created with the same tablespace structure as the source database instance. The export/import patch provides the auclondb.sql script which generates the aucrdb.sql script, which you use to create the target database instance with the appropriate tablespace and file structure. The script converts all tablespaces except for SYSTEM to locally managed tablespaces with auto segment space management, if they are not already so.

On the source administration server node, use SQL*Plus to connect to the database as SYSTEM and run the $AU_TOP/patch/115/sql/auclondb.sql script. It creates aucrdb.sql in the current directory.

$ sqlplus system/[system password] \
@$AU_TOP/patch/115/sql/auclondb.sql 11
Record Advanced Queue settings
Advanced Queue settings are not propagated in the target database instance during the export/import process. Therefore, you must record them beforehand and enable them in the target database instance afterwards. The export/import patch contains auque1.sql, which generates a script called auque2.sql. You can use auque2.sql to enable the settings in the target database instance.

Copy the auque1.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the working directory in the source database server node. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the auque1.sql script. It generates auque2.sql.

$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> @auque1.sql
Create parameter file for tables with long columns (conditional)
If the source database is Oracle Database 10g Release 2, tables with long columns may not propagate properly in datapump. Therefore, they have to be migrated separately using the traditional export/import utilities.

Copy the aulong.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the working directory in the source database server node. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the aulong.sql script. It generates aulongexp.dat.

$ sqlplus /nolog
SQL> connect system/[system password];
SQL> @aulong.sql
Remove rebuild index parameter in spatial indexes
Ensure that you do not have the rebuild index parameter in the spatial indexes. To see if you have any rebuild index parameters, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the following command:

SQL> select * from dba_indexes where index_type=’DOMAIN’ and
upper(parameters) like ‘%REBUILD%’;
To remove the rebuild index parameter, use SQL*Plus to connect to the source database as the owner of the index and run the following command:
SQL> alter index [index name] rebuild parameters [parameters]
where [parameters] is the original parameter set without the rebuild_index parameter.
Section 2: Prepare a target Release 12 database instance

This section describes how to create the empty target database and populate it with all of the required system objects prior to running import.

The Oracle home of the target database instance can be the same Oracle home that the source database instance uses, or it can be different (on another machine running a different operating system, for example), as long as it uses Oracle Database 11g Release 1 Enterprise Edition.

Create target Oracle 11g Oracle home (conditional)
If you want the target Oracle 11g Oracle home to be separate from the source Oracle home, you must create it now. Perform the steps in the “Database Installation” subsection of Section 1 of the Oracle E-Business Suite Release 12 with Oracle Database 11g Release 1 (11.1.0) Interoperability Notes, Oracle E-Business Suite Release 12.1 with Oracle Database 11g Release 1 (11.1.0) Interoperability Notes, or Oracle E-Business Suite Release 12 with Oracle Database 11g Release 2 (11.2.0) Interoperability Notes.

Modify sqlnet.ora file (Windows only)
If the target database server node is running Windows, add the following line to the sqlnet.ora file in the %ORACLE_HOME%\network\admin\[SID] directory, if it does not already exist:

SQLNET.AUTHENTICATION_SERVICES=(NTS)
Create the target initialization parameter file and CBO parameter file
The initialization parameter file (init[SID].ora) and cost-based optimizer (CBO) parameter file (ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server node. Copy both files to the Oracle 11g $ORACLE_HOME/dbs directory on the target database server node.

Refer to Database Initialization Parameters for Oracle Applications Release 12 and update both the init.ora and ifilecbo.ora files with any necessary changes. You may also need to update initialization parameters involving the db_name, control_files, and directory structures.

Ensure that the undo_tablespace parameter in the initialization parameter file of the target database instance matches with the default undo tablespace set in the aucrdb.sql script.

Ignore the initialization parameters that pertain to the native compilation of PL/SQL code. You will be instructed to add them later, if necessary.

Create a working directory
Create a working directory named expimp in the target system that will contain all generated files and scripts required to complete this section. As an example,

$ mkdir /u01/expimp
Create the target database instance
Copy the aucrdb.sql script, generated in Section 1, from the source administration server node to the working directory in the target database server node. Then update the script on the target database server node with any necessary changes to the directory structures for the log file(s), data file(s), or tablespaces, reflecting the layout of the target database server node. You may enlarge the file sizes to ensure that tablespaces do not run out. If the target database server node is running Windows, update the directory structure from UNIX/Linux format to Windows format or vice versa.

Make sure that the environment of your session on the target database server node is set up properly for the target database instance, especially the ORACLE_HOME, ORACLE_SID, and ORA_NLS10 environment settings. (ORACLE_SID must be set to the same value as the db_name parameter in the init[SID].ora file.) Then, use the following commands to run aucrdb.sql and create the target database instance:

$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> spool aucrdb.log;
For UNIX or Linux:

SQL> startup nomount;
SQL> @aucrdb.sql
SQL> exit;
For Windows:

SQL> startup nomount pfile=%ORACLE_HOME%\dbs\init%ORACLE_SID%.ora
SQL> @aucrdb.sql
SQL> exit;
If PL/SQL of the source database was natively compiled, see the “Compiling PL/SQL Code for Native Execution” section of Chapter 12 of Oracle Database PL/SQL Language Reference 11g Release 1 (11.1) or Oracle Database PL/SQL Language Reference 11g Release 2 (11.2) for instructions on how to natively compile PL/SQL in the target database. Add the parameters that pertain to the native compilation where specified. Do not use the natively compiled code generated by the source database. Oracle does not support switching the PL/SQL compilation mode from interpreted to native (and vice-versa) for an export/import. Exporting/importing using native mode takes significantly more time than interpreted mode.

When the target database instance has been created, restart the database instance.

Note: You may modify the sizes of the database files in aucrdb.sql to ensure enough tablespace. Querying the dba_free_space and dba_data_files tables in the source database can give you an idea of how much tablespace is required. However, this is no guarantee as the space requirements may change depending on the extent sizes used by each object. Not having enough tablespace will cause failures as well as a major performance degradation in the import run.

Copy database preparation scripts to target Oracle home
The export/import patch that you applied to the source administration server node in Section 1 contain four scripts that are needed on the target database server node. Copy the following files from the $AU_TOP/patch/115/sql directory of the source administration server node to the working directory in the target database server node: audb1110.sql/audb1120.sql, ausy1110.sql/ausy1120.sql, aujv1110.sql/aujv1120.sql, and aumsc1110.sql/aumsc1120.sql (UNIX or Linux) or audb1110_nt.sql/audb1120_nt.sql, ausy1110_nt.sql/ausy1120_nt.sql, aujv1110_nt.sql/aujv1120_nt.sql, and aumsc1110_nt.sql/aumsc1120_nt.sql (Windows).

As you run each of the next four steps, note the following:

The remarks section at the beginning of each script contains additional information.

Each script creates a log file in the current directory.

Set up the SYS schema
The audb1110.sql, audb1120.sql, audb1110_nt.sql, or audb1120_nt.sql script sets up the SYS schema for use with the Applications. On the target database server node, use SQL*Plus to connect to the target database instance as SYSDBA and run audb1110.sql/audb1120.sql (UNIX/Linux) or audb1110_nt.sql/audb1120_nt.sql (Windows).

Here is an example on UNIX or Linux for 11.2.0:

$ sqlplus “/ as sysdba” @audb1120.sql
Set up the SYSTEM schema
The ausy1110.sql, ausy1120.sql, ausy1110_nt.sql, or ausy1120_nt.sql script sets up the SYSTEM schema for use with the Applications. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run ausy1110.sql/ausy1120.sql (UNIX/Linux) or ausy1110_nt.sql/ausy1120_nt.sql (Windows).

Here is an example on UNIX or Linux for 11.2.0:

$ sqlplus system/[system password] @ausy1120.sql
Install Java Virtual Machine
The aujv1110.sql, aujv1120.sql, aujv1110_nt.sql, or aujv1120_nt.sql script installs the Java Virtual Machine (JVM) in the database. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run aujv1110.sql/aujv1120.sql (UNIX/Linux) or aujv1110_nt.sql/aujv1120_nt.sql (Windows).

Here is an example on UNIX or Linux for 11.2.0:

$ sqlplus system/[system password] @aujv1120.sql
Attention: This script can be run only once in a given database instance, because the scripts that it calls are not rerunnable.

Install other required components
The aumsc1110.sql, aumsc1120.sql, aumsc1110_nt.sql, or aumsc1120_nt.sql script installs the following required components in the database: ORD, Spatial, XDB, OLAP, Data Mining, interMedia, and ConText. On the target database server node, use SQL*Plus to connect to the target database instance as SYSTEM and run aumsc1110.sql/aumsc1120.sql (UNIX/Linux) or aumsc1110_nt.sql/aumsc1120_nt.sql (Windows). You must pass the following arguments to the script, in the order specified:

Argument Value
remove context? FALSE
SYSAUX tablespace SYSAUX
temporary tablespace TEMP
Here is an example on UNIX or Linux for 11.2.0:

$ sqlplus system/[system password] \
@aumsc1120.sql FALSE SYSAUX TEMP
Attention: All of the components are created in the SYSAUX tablespace regardless of where it was installed in the source database.

Set CTXSYS parameter (conditional)
If your target database is 11g Release 2 (11.2.0), use SQL*Plus to connect to the database as SYSDBA and run the following command:

$ sqlplus “/ as sysdba”
SQL> exec ctxsys.ctx_adm.set_parameter(‘file_access_role’, ‘public’);
Disable automatic gathering of statistics
Copy $APPL_TOP/admin/adstats.sql from the administration server node to the target database server node. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode and run adstats.sql:

$ sqlplus “/ as sysdba”
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus “/ as sysdba”
SQL> alter system disable restricted session;
SQL> exit;
Back up the target database instance
The target database instance is now prepared for an import of the Applications data. You should perform a backup before starting the import.

Section 3: Export the source Release 12 database instance

This section describes how to ensure that you have the required patches, create your export file, and capture important information that is required to import your database.

Create the export parameter file
A template for the export parameter file has been included as part of the the export/import patch. Copy $AU_TOP/patch/115/import/auexpdp.dat from the source administration server node to the working directory in the source database server node. Use a text editor to modify the file to reflect the source environment and other customized parameters.

The customizable parameters are:

Parameter Description Template Value
directory directory where the export dump files will be created dmpdir
dumpfile export dump file name(s) aexp%U.dmp
filesize export dump file size 1GB
log log file name expdpapps.log
interMedia, OLAP, and Data Mining schemas are not exported. The aumsc1110.sql script creates these schemas in the target database. Ensure that the schema names in the exclude parameters reflect those in your database.

If your source database is Oracle Database 11g (11.x), add the following line to the parameter file:

QUERY=applsys.wf_item_attribute_values:”where item_type!=’WFERROR’ and
name != ‘EVENT_MESSAGE'”
Create a directory in the system schema that corresponds to the directory specified in the template. Here is an example of how to create a directory named dmpdir:

$ sqlplus system/[system password]
SQL> create directory dmpdir as ‘/u01/expimp’;
Do not change the other parameters.

The export process uses as many of the listed file names as necessary to hold the exported data. You must ensure that the number of dump files specified, as well as the size of each dump file, is sufficient to contain all the data in your source database instance.

Shut down Applications server processes
Shut down all Applications server processes except the database and the Net8 listener for the database. Users cannot use the Applications until the import is completed.

Grant privilege to source system schema
Grant the exempt access policy privilege to system by using SQL*Plus to connect to the database as SYSDBA and run the following command:

SQL> grant EXEMPT ACCESS POLICY to system;
Export OLAP analytical workspaces (optional)
The export/import of OLAP analytical workspaces may take up a lot of resources. It may cause memory issues such as bug 10331951. Customers who use OLAP may export/import OLAP through the DBMS_AW package directly as an alternative.

Perform the detailed steps 1-3 as documented in My Oracle Support Note 352306.1, Upgrading OLAP from 32 to 64 bits, to export OLAP analytical workspaces on the source machine. Copy the export files to the target machine.

Drop XLA packages (optional)
The export/import of large Sub-ledger Accounting (XLA) packages may take up a long time. The XLA packages can be dropped before the export and re-created after the import to optimize the export/import process.

On the source database server node, use SQL*Plus to connect to the source database as APPS and run the following to determine the XLA packages:

$ sqlplus apps/[APPS password]
SQL> select distinct(‘drop package ‘||db.owner||’.’|| db.object_name || ‘;’)
from dba_objects db, xla_subledgers xl
where db.object_type=’PACKAGE BODY’ and db.object_name like ‘XLA%AAD%PKG’
and substr(db.object_name,1,9) = ‘XLA_’||
LPAD(SUBSTR(TO_CHAR(ABS(xl.application_id)), 1, 5), 5, ‘0’)
and db.object_name NOT IN (‘XLA_AAD_HDR_ACCT_ATTRS_F_PKG’,’XLA_AMB_AAD_PKG’)
order by 1;
Copy the output to SQL*Plus to drop the packages.

Export the Applications database instance
Start an export session on the source database server node using the customized export parameter file.

If the source database is 10.2.0 or 11.1.0, use the following command:

$ expdp system/[system password] parfile=[export parameter file name]
If the source database is 11.2.0, use the following command:

$ expdp “‘/ as sysdba'” parfile=[export parameter file name]
Typically, the export runs for several hours.

Export tables with long columns (conditional)
If the source database is Oracle Database 10g Release 2 (10.2.0), start an export session on the source database server node using the customized aulongexp.dat file generated in Section 1. Use the following command:

$ exp parfile=aulongexp.dat
Export tables with XML type columns (conditional)
If the source database is Oracle Database 10g Release 2 (10.2.0), copy $AU_TOP/patch/115/import/auxmlexp.dat from the source administration server to the working directory in the source database server node. Start an export session on the source database server node using the following command:

$ exp parfile=auxmlexp.dat
Revoke privilege from source system schema
Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command:

SQL> revoke EXEMPT ACCESS POLICY from system;
Section 4: Import the Release 12 database instance

This section describes how to use the import utility to load the Oracle Applications data into the target database.

Create the import parameter files
Copy auimpdp.dat, aufullimp.dat, and auimpusr.dat from the $AU_TOP/patch/115/import directory in the source administration server node to the working directory in the target database server node. Make sure that the directory, dumpfile, and logfile parameters in auimpdp.dat and auimpusr.dat are set properly.

Create a directory in the system schema with the name set to the directory specified in the template and the path set to where the export dump files will reside. Here is an example of how to create a directory named dmpdir:

$ sqlplus system/[system password]
SQL> create directory dmpdir as ‘/u01/expimp’;
Save the changed file.

Copy the export dump files
Copy the export dump files from the source database server node to the working directory in the target database server node.

Import the users into the target database (conditional)
If the source database is Oracle Database 10g Release 2 (10.2.0), start an import session on the target database server node using the customized import parameter file. Use the following command:

$ impdp system/[system password] parfile=auimpusr.dat
Import tables with long columns into the target database (conditional)
If the source database is Oracle Database 10g Release 2 (10.2.0), modify the aufullimp.dat file with the following:

Set userid to “sys/[sys password] as sysdba”.

Set file to the dump file containing the long tables (longexp by default).

Set the log file appropriately.

Leave the ignore parameter commented out.

Import the tables using the following command:

$ imp parfile=aufullimp.dat
Attention: You will get failures for the triggers as the dependent tables have not yet been imported.

Import the Applications database instance
If your source database is Oracle Database 11g (11.x), remove or comment out all the exclude parameters in the auimpdp.dat parameter file. If your source database is Oracle Database 10g Release 2 (10.2.0), leave the parameter file as is. Start an import session on the target database server node using the auimpdp.dat parameter file.

If the target database is 11.1.0, use the following command:

$ impdp system/[system password] parfile=auimpdp.dat
If the target database is 11.2.0, use the following command:

$ impdp “‘/ as sysdba'” parfile=auimpdp.dat
Typically, import runs for several hours.

Import triggers into the target database (conditional)
If the source database is Oracle Database 10g Release 2 (10.2.0), modify the aufullimp.dat file with the following:

Set userid to “sys/[sys password] as sysdba”.

Set file to the dump file containing the long tables (longexp by default).

Change the log file name.

Uncomment the ignore parameter.

Add a line with the parameter “rows=n”.

Start an import session on the target database server node using the customized import parameter file. Use the following command:

$ imp parfile=aufullimp.dat
Import OLAP analytical workspaces (conditional)
If you exported OLAP analytical workspaces, perform the detailed step 7 as documented in My Oracle Support Note 352306.1 to import the OLAP analytical workspaces that were previously exported from the source machine.

Revoke privilege from target system schema
Revoke the exempt access policy privilege from system by using SQL*Plus to connect to the database as SYSDBA and run the following command:

SQL> revoke EXEMPT ACCESS POLICY from system;
Section 5: Update the imported Release 12 database instance

This section describes how to recreate the database objects and relationships that are not handled by the export and import utilities.

Reset Advanced Queues
Copy the auque2.sql script that was generated in Section 1 from the working directory in the source database server node to the working directory in the target database server node. Then, on the target database server node, as the owner of the Oracle 11g file system and database instance, use SQL*Plus to connect to the target database as SYSDBA and run the auque2.sql script to enable the Advanced Queue settings that were lost during the export/import process. The script creates a log file in the current directory.

$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> @auque2.sql
Start the new database listener (conditional)
If the Oracle Net listener for the database instance in the new Oracle home has not been started, you must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable (UNIX/Linux) or Services (Windows). See the Oracle Database Net Services Administrator’s Guide, 11g Release 1 (11.1) or Oracle Database Net Services Administrator’s Guide, 11g Release 2 (11.2) for more information.

Attention: Set the TNS_ADMIN environment variable to the directory where you created your listener.ora and tnsnames.ora files.

Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration server node to the working directory in the database server node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:

$ sqlplus “/ as sysdba” @adgrants.sql (or adgrants_nt.sql) \
[APPS schema name]
Note: Verify the usage of adgrants.sql in the adgrants.sql script. Older versions of adgrants.sql require the APPLSYS schema name parameter to be passed instead of APPS.
Grant create procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node. Use SQL*Plus to connect to the database as APPS and run the script using the following command:

$ sqlplus apps/[APPS password] @adctxprv.sql \
[SYSTEM password] CTXSYS
Apply patch 6494466 (conditional)
If the target database is Windows and the source is not, apply patch 6494466 on the target database tier. Create the appsutil directory if needed.

Deregister the current database server (conditional)
If you plan to change the database port, host, SID, or database name parameter on the database server, you must also update AutoConfig on the database tier and deregister the current database server node.

Use SQL*Plus to connect to the database as APPS and run the following command:

$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;
Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener.

See Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12 on My Oracle Support, especially section 3.2, for instructions on how to implement and run AutoConfig.

Shut down all processes, including the database and the listener, and restart them to load the new environment settings.

Gather statistics for SYS schema
Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:

$ sqlplus “/ as sysdba”
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus “/ as sysdba”
SQL> alter system disable restricted session;
SQL> exit;
Attention: Make sure that you have at least 1.5 GB of free default temporary tablespace.

Re-create custom database links (conditional)
If the Oracle Net listener in the 11g Oracle home is defined differently than the one used by the old Oracle home, you must re-create any custom self-referential database links that exist in the Applications database instance. To check for the existence of database links, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following query:

$ sqlplus apps/[apps password]
SQL> select db_link from dba_db_links;
The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should have been updated with the new port number by AutoConfig in the previous step.

If you have custom self-referential database links in the database instance, use the following commands to drop and re-create them:

$ sqlplus apps/[apps password]
SQL> drop database link [custom database link];
SQL> create database link [custom database link] connect to
[user] identified by [password] using
‘(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname])
(PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))’;
where [custom database link], [user], [password], [hostname], [port number], and [ORACLE_SID] reflect the new Oracle Net listener for the database instance.

Create ConText and AZ objects
Certain ConText objects and the AZ objects dependent on the tables with XML type columns 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:

$ perl $AU_TOP/patch/115/bin/dpost_imp.pl [driver file]\

Set

to 10 if the source database is 10.2 or to 11 if the source database is 11g.

Once the driver file has been generated, use AutoPatch to apply it on the target administration server node.

Import tables with XML type columns into the target database (conditional)
If the source database is Oracle Database 10g Release 2, modify the aufullimp.dat file with the following:

Set userid to “az/[az password]”

Set file to the dump file containing the tables with XML types (xmlexp by default).

Change the log file name.

Comment out the ignore parameter.

Start an import session on the target database server node using the customized import parameter file. Use the following command:

$ imp parfile=aufullimp.dat
Once the import is complete, you can delete the export dump files, as well as the export and import parameter files, from the source and target database server nodes.

Populate CTXSYS.DR$SQE table
To populate the CTXSYS.DR$SQE table, use SQL*Plus on the database server node to connect to the Applications database instance as APPS and run the following command:

$ sqlplus apps/[apps password]
SQL> exec icx_cat_sqe_pvt.sync_sqes_for_all_zones;
Compile invalid objects
On the target database server node, as the owner of the Oracle 11g file system and database instance, use SQL*Plus to connect to the target database as SYS and run the $ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.

$ sqlplus “/ as sysdba” @$ORACLE_HOME/rdbms/admin/utlrp.sql
Re-create XLA packages (conditional)
If you dropped the XLA packages in the source environment, copy $XLA_TOP/patch/115/sql/xla6128278.sql from the administration server node to the target working directory, use SQL*Plus to connect to the database as APPS, and run the following script to re-create the XLA packages:

$ sqlplus apps/[APPS password]
SQL> @xla6128278.sql [spool log file]
Maintain Applications database objects
Run AD Administration on the target administration server node. From the Maintain Applications Database Objects menu, perform the following tasks:

Compile flexfield data in AOL tables

Recreate grants and synonyms for APPS schema

Start Applications server processes
Start all the server processes on the target Applications system. You can allow users to access the system at this time.

Create DQM indexes
Create DQM indexes by following these steps:

Log on to Oracle Applications with the “Trading Community Manager” responsibility

Click Control > Request > Run

Select “Single Request” option

Enter “DQM Staging Program” name

Enter the following parameters:

Number of Parallel Staging Workers: 4

Staging Command: CREATE_INDEXES

Continue Previous Execution: NO

Index Creation: SERIAL

Click “Submit”

Oracle E-Business Suite 12.0.6 to 12.1.3 Upgradation Issues & Fixes

1. Issue: OC4J~home~default_group~1

WARNING: Application: default is in failed state as initialization failedjava.lang.InstantiationException: Shared library
“adf.oracle.domain” could not be found. Error initializing server: Shared library “adf.oracle.domain” could not be found.

Fix: Add adf.oracle.domain share library to your oc4j’s server.xml file, if those libs are not required for your app.. Then you can
remove “adf.oracle.domain” share libs from your app’s orion-application.xml.

2. Issue: ERROR: OPatch failed during prerequisite check

Fix: Please follow below steps from Error [Code=1] Running Adjopy.class [ID 339072.1]
a. Change the ownership of the directories to the APPS User and DBA group (to which APPS User should belong to) — this action
has to be done as Root User.
b. Retest the issue and re-apply patch.
Follow step C and D only, if step a and b didn’t solve the issue!
c. Rename class CloneContext$1.class to CloneContext$1.class.bak
d. Retest the issue and re-apply patch.

3. Issue: Patch 7303030 (12.1.1 Patchset) & 9839090 (12.1.3 Patchset) Fails on Egosildu.sql with ORA-02149 error

Fix: Please follow steps from ORA-02149 Specified Partition Does Not Exist [ID 847687.1]

Note: Prior to failing out the worker was hanging on this script for more than 2 Hours, when checked in alert log file APPS, SYSTEM
tablespaces were full.

4. Issue: Oracle Application E-Business suite Login Page is blank after upgrading 12.0.6 to 12.1.1

Fix: It is a Bug 10287187: LOGIN PAGE IS A BLANK AFTER R12.1.3 UPGRADE FROM 12.0.6 – HTML: CHAIN FAILED. Please
perform the following:

perl ojspCompile.pl –compile -s ‘AppsLocalLogin.jsp’ –flush

Note: To perform jsp compilation by default change the “main_mode” parameter in XML file from “just run” to “recompile”.

5. Issue: ORA-600/ORA-7445 errors

Fix: Error Look-up Tool [ID 153788.1]

6. Issue: Oracle E-Business Suite Release 12.1.3 Patch 9239090 was running for more than 10 Hours, when checked db
pfile was not having updated values as required by 11gR2 database.

Fix: Please follow Database Initialization Parameters for Oracle E-Business Suite Release 12 [ID 396009.1]

7. Issue: Patch 9239090 Fails on Egosildu.sql with ORA-02149 error

Fix: Please follow the step 3.

8. Issue: Patch 9239090 Fails on mth_pre_upgrade.sql with ORA-00955: name is already used by an existing object

Fix: The usual cause of your issue is that the pre upgrade script mth_pre_upgrade.sql already ran successfully in the past. This
script should be run only once and the solution is to skip the failed job.

9. Issue: Patch 9239090 Fails on MSDODPCODE.sql with ORA-33272: Analytic workspace APPS.ODPCODE cannot be
opened & ORA-33288: Another user has incompatible access to analytic workspace.

Fix: Restart the patch using adpatch options= “noparallel”

10. Issue: Autoconfig exited with status 1 & during jtfictx.sh script execution ORA-29874, DRG-10595 errors

Fix: Please check the below note id’s and perform appropriate action plan:
1. “Jtfictx.sh” Failed During Autoconfig on Application Tier, ORA-29874, and DRG-10595 [ID 1271186.1]
2. Error DRG-10758 When Creating Text Index Using File Data store [ID 1081227.1]
3. DRG-11446: supplied knowledge base file /u01/app/oracle/product/11.2.0/dbhome_1/ctx/data/enlx/droldUS.dat not installed

Please perform the below steps to resolve above issue:
a. Download the Oracle Examples Installation (formally Companion CD)
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-linx8664soft-100572.html
b. Unzip the Oracle Examples Installation
$ unzip linux.x64_11gR2_examples.zip
c. Go to the location in the installation media for the CTX File groups
$ cd examples/stage/Components/oracle.ctx.companion/11.2.0.1.0/1/DataFiles
d. Unzip the CTX Knowledge base files
$ unzip filegroup1.jar
Archive: filegroup1.jar
inflating: ctx/data/enlx/drofdUS.dat
inflating: ctx/data/enlx/drofiUS.dat
inflating: ctx/data/enlx/droldUS.dat
inflating: ctx/data/enlx/droliUS.dat
inflating: ctx/data/enlx/drolkUS.dat
inflating: ctx/data/enlx/drolsUS.dat
e. Go to the location of the knowledge base files we just extracted and copy them to the Oracle Database Home location
$ cd ctx/data/enlx/
$ cp * $ORACLE_HOME/ctx/data/enlx

11. Issue: FRM-92101: There was a failure in the Form Server during startup.
Details…
Java Exception:
Oracle.forms.net.ConnectionException: Forms session <1> failed during
at Oracle.forms.net.ConnectionException:………………..

Fix: Issue is because missing rpm “openmotif21-2.1.30-11.EL5.i386.rpm”
Download this rpm from http://oss.oracle.com/projects/compat- oracle/files/Enterprise_Linux/ and apply.

12. Issue: After 12.1.1 to 12.1.3 upgradation if below mentioned objects are invalid then apply the respective patches to fix
them.

Fix:

Object Name

Patch Number

PA_PWP_SUMM_PKG

9813360

FV_*

9000001:R12.FV.B

ITG_SYNCSUPPLIERINBOUND_PVT

13598894:R12.ITG.B

IGW_BUDGET_CATEGORY_V & IGW_REPORT_PROCESSING

6629280