How can we control a concurrent program to Run In Specific RAC/PCP node?

How can we control a concurrent program to Run In Specific RAC/PCP node?


There is an interesting feature in R12 for this to achieve.


In concurrent program define window , we can define which node and instance a concurrent program should connect and run, That is through concurrent program session control.

Navigation: System Administrator Responsibility > Concurrent > Program > Define > Click 'Session Control' 

You can define in this screen Target Node and Target Instance for that particler concurrent program. 

Irrespective of the managers running on the node and connected to which ever RAC instance, This definition makes sure the program is run in the specified RAC/PCP node.

What is Target Node 
------------------------

If you specify the target node on which requests for this program will run. When requests for this program are submitted, They run on this node if that is node is available, 

If no specification is made for the target node of a concurrent program, a request for it will be picked up by any manager available to run it. 

If a node specification is made for a concurrent program and the node is up, only available managers running on the specified node will pick up the request. 

What is Target Instance 
----------------------------

When requests for this program are submitted, they run on this database instance node If it is available.

If no specification is made for the target instance of a concurrent program, a request for it will be picked up by the first manager available to run it and will be run in the instance where the manager is already connected.

If an instance specification is made for a concurrent program and the instance is up, it will be picked up by the first manager available to run it and the manager will run the request in the specified instance. 

However, if the target RAC instance is down, the manager will run the request in the instance where it is already connected and log an appropriate message.

Oracle Business Intellegence Analytics Installation on Linux Steps

Oracle Business Intellegence Analytics Installation on Linux Steps

OBIA works with in combination of the OBIEE,Informatica and DAC.

The below versions of the components were used to complete the OBIA 7.9.6.3 Installation and Setup.

----------------------
OBIEE 11g - 11.1.1.5
OBIA - 7.9.6.3
Informatica - 9.0.1
DAC - 7.9.6.3
Oracle DW Database - 11GR2
Oracle Database Client - 11GR2
----------------------

Installation of the Server components has been done on Linux server and the Client components was done on Windows server.

Please find the below high level steps of the installation.

THIS IS ONLY HIGH LEVEL PLAN

Server Installation on Linux
==================

1)Install the Database 11GR2 (In multinode architecture this should be done on Database node)

2)Create the schemas & objects required for OBIEE using RCU (Repository creation utility

3)Install OBIEE 11G and which will also install weblogic

4)Install Informatica server 9.0.1 on Linux

5)Install DAC server on Linux

6)Install Oracle database 11GR2 Client software (in case of DB is in different node)

Client  Installation on Windows
============================

1)Install OBIEE 11G on Client windows machine (use OBIEE windows software

2)Install OBIA on top of the OBIEE installation

3)Install DAC & Informatica client on the windows machine

4)Install OBIEE client tool.


Server Setup & Configuration:
==============================

1) Copy the rdp and catalog presentation layer components fron biapps directory to server OBIEE

2) Copy DAC metadata related files to DAC client to DAC server

3) Setup DAC server using setupserver.sh script

4) Create DAC connection and create the DAC DataWare house tables

6) Copy information source and config files from windows to linux server

How does workflow Notification Mailer IMAP (Inbound Processing) Works

How does workflow Notification Mailer IMAP (Inbound Processing) Works:

This is the inbound flow:

1. Approver sends email response which is directed to the value defined in Replyto address.
a. This address has been setup by the customer's mail administrator to route incoming mail to the IMAP Inbox folder.
2. The Workflow Inbound Agent Listener picks up the message. Only messages which are in ‘unread’ state are evaluated; the rest of the messages in the inbox are ignored.

3. The message is scanned to see if it matches entries in the TAG file . Mail tags are defined in the OAM mailer configuration pages and these list strings of text and actions to take if those strings are encountered. An example of this are 'Out of Office' replies. If the string of the message matches a mail tag and the action is 'Ignore' then nothing else will happen.

4. The message is then scanned for the presence of a Notification Id (NID). This NID is matched against valid NID for the mailer node.

5. If valid NID is not detected, (and there is no matching TAG file entry) then the message is placed into the DISCARD folder.

6. If a valid NID is detected the listener raises a subscription to the WF_NOTIFICATION_IN queue and places the mail message in the Processed folder.

7. From this point on the message is handled by the product workflow (like PO APPROVAL) . An event created by that group will monitor the WF_NOTIFICATION_IN queue and will trigger the rest of the approval workflow.

What is REVIVER In Oracle Applications:

What is REVIVER In Oracle Applications:

Reviver is used for momentary disconnects in the system where the concurrent managers and/or forms go down, and forms is later reconnected while the concurrent managers are not. FNDREVIVER revives the Internal Concurrent Manager (ICM) when it fails.
When ICM can no longer get a database connection, it kills itself and spawns the reviver. Reviver loops every 30 seconds, attempting to login to the database as apps user. Once login is successful, it starts up the ICM again.

If the failure is due to a brief network outage, or database issue, the managers are restarted, so the client does not have to restart the managers manually.

Reviver is recovery mechanism delivered with ATG RUP4 (patch 4676589), and runs in the background. In a Real Applications Cluster (RAC) environment, when the primary node goes down and ICM is set to migrate to the secondary node, the reviver parameter will be passed to the secondary node.

The easiest way to determine if reviver.sh exists is by checking the $FND_TOP/bin directory.

The variable resides in the context file under 's_cp_reviver' and can be set to "enabled" or "disabled". Based on the value of s_cp_reviver in the context file, AFCPDNR is started with a value of either "enabled" or "disabled" .

The reviver is started when starting the ICM, by passing a parameter reviver="enabled". You do this on the node you start the manager, and if the ICM is set to migrate to the second node, this parameter will be passes to the second node.
A common misconception is that users must start the reviver.sh manually, however this is not the intended use. It is automatically enabled when the parameter REVIVER_PROCESS="enabled" is passed via the adcmctl.sh concurrent manager startup script.

On a single node concurrent processing system, FNDREVIVER is the only way to recover from a database connection loss.

On a two node system (PCP), there is another factor, the Internal Monitor (FNDIMON).The FNDIMON will race to restart the internal manager in a multi node setup, and by the time the reviver starts it will likely see that the ICM is already running and exit accordingly.
FNDIMON checks whether it can connect to the database in order to determine if the ICM is running, and if the database connection is not available it fails to run and exits accordingly. The reviver is a shell script which loops until a connection is obtained, and then starts the manager accordingly. The reviver's job is the last line of defense after a database connection failure, as FNDIMON only works when the database connection is available.

In the event the ICM goes down due to a network outage, then the reviver would be needed to bring the ICM back up.

How to check and Enable reviver in Oracle Applications (Its by default enabled in R12):

The following parameters can be set in the context file, and then autoconfig should be re-run to enable reviver:

Example:
 $grep -i s_cp_reviver $CONTEXT_FILE
<cp_reviver oa_var="s_cp_reviver">enabled</cp_reviver>

Reviver Process PID Directory Location (s_fndreviverpiddir)

This variable specifies the path where ICM reviver process pid file will be created. Oracle recommends using a local disk as the PID file location because
the reviver process may run when the network is down.

Example:
<fndreviverpiddir oa_var="s_fndreviverpiddir">/u02/oracle/visappl/fnd/11.5.0/log</fndreviverpiddir>

Oracle Applications Database Documentation Resources

Oracle Applications Database Documentation Resources, Release 12
================================================================
 
 Note 396009.1 Database Initialization Parameters for Oracle Applications Release 12
 Note 802875.1 Interoperability Notes E-Business Suite Release 12.1 with Oracle Database 11gR1 (11.1.0)
 Note 1058763.1 Interoperability Notes EBS R12 with Database 11gR2
 Note 735276.1 Interoperability Notes E-Business Suite R12 with Oracle Database 11gR1 (11.1.0)
 Note 782224.1 Interoperability Notes Oracle E-Business Suite Release 12 with 11gR1 (11.1.0.6)
 Note 454750.1 Oracle Apps Release 12 with Oracle Database 10.2.0 interoperability notes
 Note 761570.1 Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade
 Note 728244.1 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 738556.1 Oracle 11gR1 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 784374.1 Oracle 11gR1 (11.1.0.6) Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 403339.1 Oracle 10gR2 Database Preparation Guidelines for an E-Business Suite Release 12.0.4 Upgrade
 Note 552973.1 Oracle 10gR2 (10.2.0.3) Database Preparation Guidelines for an E-Business Suite Release 12.0 Upgrade
 Note 467778.1 Oracle 10gR2 (10.2.0.2) Database Preparation Guidelines for an E-Business Suite Release 12.0 Upgrade
 Note 756050.1 Troubleshooting Autoconfig issues with Oracle Applications RAC Databases
 Note 745759.1 Oracle E-Business Suite and Oracle Real Application Clusters Documentation Roadmap
 Note 823587.1 Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12
 Note 466649.1 Using Oracle 11g Release 1 (11.1.0.7) Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
 Note 783044.1 Using Oracle 11g Release 1 (11.1.0.6) Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
 Note 388577.1 Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12
 Note 762669.1 Using Oracle EBS R12 with a Database Tier Only Platform on Oracle 11gR1
 Note 456197.1 Using Oracle E-Business Suite Release 12 with a Database Tier Only Platform on Oracle 10g Release 2
 Note 741818.1 Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 11g Release 1
 Note 454616.1 Export/Import Process for Oracle E-Business Suite Release 12 Database Instances Using Oracle Database 10g Release 2
 Note 452056.1 Business Continuity for Oracle Applications Release 12 on Database Release 10gR2 - Single Instance and RAC
 Note 859397.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 11.1.0.7
 Note 566841.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.4
 Note 744363.1 Integrating Oracle E-Business Suite Release 12 with Oracle Database Vault 10.2.0.3
 Note 732764.1 Using TDE Column Encryption with Oracle E-Business Suite Release 12
 Note  828229.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
 Note 734763.1 Using Transportable Database to migrate Oracle E-Business Suite R12 using Oracle Database 10g Release 2
 
Oracle Applications Database Documentation Resources, Release 11i
================================================================
 Note 216205.1 Database Initialization Parameters for Oracle Applications Release 11i
 Note 881505.1 Oracle Applications Release 11i with Oracle 11g Release 2
 Note 452783.1 Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 1 (11.1.0)
 Note 757593.1 Oracle Applications Release 11i with Oracle 11g Release 1 (11.1.0.6)
 Note 362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)
 Note 726982.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0.3)
 Note 423056.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0.2)
 Note 282038.1 Oracle Applications Release 11i with Oracle Database 10g Release 1 (10.1.0)
 Note 362202.1 Oracle Applications Release 11i with Oracle 10g (10.1.0.4)
 Note 216550.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
 Note 399078.1 Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0.7)
 Note 162091.1 Interoperability Notes Oracle Applications R11i with Oracle9i Release 9.0.1
 Note 148903.1 Interoperability Notes Oracle Applications Release 11i with Release 8.1.7
 Note 359483.1 Upgrading 9.2.0.6 to 10.1.0.4.2 with 11.5.10.2 Applications
 Note 148902.1 Interoperability Notes Oracle Applications Release 11.0 with Release 8.1.7
 Note 148901.1 Interoperability Notes Oracle Applications Release 10.7 with Release 8.1.7
 Note 455398.1 Using Oracle Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i and Oracle Database 11g
 Note 757980.1 Using Oracle 11g Release 1 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 11i (11.1.0.6)
 Note 362135.1 Configuring Oracle Applications Release 11i with Oracle10g Release 2 Real Application Clusters and Automatic Storage Management
 Note 312731.1 Configuring Oracle Applications Release 11i with 10g RAC and 10g ASM
 Note 279956.1 Oracle E-Business Suite Release 11i with 9i RAC Installation and Configuration using AutoConfig
 Note 261924.1 Oracle Applications 11.5.8 with 9i RAC Installation and Configuration
 Note 760637.1 Manually Cloning Oracle Applications Release 11i with 10g or 11g RAC
 Note 946413.1 Using Oracle EBS with a Split Configuration Database Tier on 11gR2
 Note 562983.1 Using Oracle E-Business Suite with a Split Configuration Database Tier on Oracle 11g Release 1
 Note 369693.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 2
 Note 356839.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g Release 1
 Note 304489.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 9i Release 2
 Note 332977.1 Using Oracle Applications with an HP OpenVMS Alpha Database Server
 Note 204015.1 Export/Import Process for Oracle Applications Release 11i Database Instances
 Note 557738.1 Export/Import Process for Oracle E-Business Suite Release 11i Database 11g
 Note 362205.1 10g Release 2 Export/Import Process for Oracle Applications Release 11i
 Note 331221.1 10g Export/Import Process for Oracle Applications Release 11i
 Note 230627.1 9i Export/Import Process for Oracle Applications Release 11i
 Note 204015.1Export/Import Process for Release 11i Database Instances Using Oracle8i Enterprise Edition
 Note 341437.1 Business Continuity for Oracle Applications Release 11i Using Oracle Real Application Clusters and Physical Standby Database
 Note 859399.1 Integrating Oracle E-Business Suite Release 11i with Oracle Database Vault 11.1.0.7
 Note 403294.1 Using TDE Column Encryption with Oracle E-Business Suite Release 11i
 Note 828223.1 Using TDE Tablespace Encryption with Oracle E-Business Suite Release 11i
 Note 729309.1 Using Transportable Database to migrate Oracle E-Business Suite Release 11i Using Oracle Database 10g Release 2 Enterprise Edition
 Note 285267.1 Oracle E-Business Suite 11i and Database FAQ


Miscellaneous - Oracle Applications Database Documentation Resources
================================================================
Note 216211.1 Nologging in the E-Business Suite
Note 312421.1 PL/SQL Native Compilation of Applications 11i on Oracle Database 10g Release 1 (10.1.0)
Note 554539.1 Using Database Partitioning with Oracle E-Business Suite
 

Configure Parallel Concurrent Processing For Oracle Applications

Configure Parallel Concurrent Processing (Note ID:362135.1)
NOTE: This section is for UNIX platforms only. Windows users should follow the instructions in Appendix F for configuration of Parallel Concurrent Processing and transaction managers.

a) PCP Prerequisites:
---------------------
It is assumed that you have more than one Concurrent processing tiers in your environment to setup PCP.
If you do not have this refer to Oracle MetaLink Note: 230672.1 for cloning of Applications tier.

b) Set Up PCP:
-------------
   1. Execute AutoConfig by using $COMMON_TOP/admin/scripts/<context_name>/adautocfg.sh on all concurrent nodes.
   2. Source the application environment by using $APPL_TOP/APPSORA.env
   3. Check the configuration files tnsnames.ora and listener.ora located under 8.0.6 ORACLE_HOME at $ORACLE_HOME /network/admin/<context>. Ensure that you         have information of all the other concurrent nodes for FNDSM and FNDFS entries.
   4. Restart the application listener processes on each application node.
   5. Logon to Oracle E-Business Suite Applications using SYSADMIN in login and System Administrator Responsibility. Navigate to Install > Nodes screen             and ensure that each node in the cluster is registered.
 
   6. Verify whether the Internal Monitor for each node is defined properly with correct primary and secondary node specification and work shift details.           Also make sure the Internal Monitor manager is activated by going into Concurrent -> Manager -> Administrator and activate the manager.
      (e.g. Internal Monitor: Host2 must have primary node as host2 and secondary node as host3)
   7. Set the $APPLCSF environment variable on all the CP nodes pointing to a log directory on a shared file system.
   8. Set the $APPLPTMP environment variable on all the CP nodes to the value of the UTL_FILE_DIR entry in init.ora on the database nodes. This value should        be pointing to a directory on a shared file system.
   9. Set profile option ' Concurrent: PCP Instance Check' to OFF if DB instance sensitive failover is not required. By setting it to 'ON' Concurrent               Managers will failover to a secondary middle-tier node when database instance it is connected goes down.

Purging and performence related Concurrent Requests for 11i and R12

The below seeded purging requests will help you to reduce the unwanted data and increase the performence of the oracle Applications.
These requests are applicable to both 11i and R12.

Note :Please note the purging request will delete the data permanently, So if you have any other business requierements please be cautious.

1)The "WORKFLOW CONTROL QUEUE CLEANUP" concurrent program should be scheduled to run at least every 12 HOURS.
 
2)Request Set with the following parameters:
For instances using Oracle Applications Release 11.5.8 or later, a concurrent request set consisting of the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" and "COMPLETE DEFUNCT HR WORKFLOW PROCESSES" concurrent programs should be scheduled to run daily with the following parameters:
    "Purge Obsolete Workflow Runtime Data":
      Item Type: NULL
      Item Key: NULL
      Age: 7
      Persistence Type: select meaning
                        from fnd_lookups
                        where lookup_type = 'FND_WF_PERSISTENCE_TYPE'
                        and lookup_code = 'TEMP';
    "Complete Defunct HR Workflow Processes":
      Item Type: HR
      Age: 7
      Transaction Status: ALL
In addition, the stages of the request set should be linked such that the "Complete Defunct HR Workflow Processes" concurrent program only runs if the "Purge Obsolete Workflow Runtime Data" concurrent program returns Success or Warning.
 

3)The "GATHER SCHEMA STATISTICS" concurrent program should be scheduled to run at least every 7 DAYS.
 
4) For instances using Oracle Applications Release 11.5.8 or later, if PO is licensed, then the "PURGE OBSOLETE WORKFLOW RUNTIME DATA" concurrent program should be scheduled to run every week with the following parameters:
    Item Type: PO Approval
   
5)The program "PURGE CONCURRENT REQUEST AND/OR MANAGER DATA" should be scheduled to run within the next 24 hours with the following parameter(s): Entity=ALL, Mode=Age, Mode Value=30
  
6)The "PURGE OBSOLETE GENERIC FILE MANAGER DATA" concurrent program should be scheduled to run at least once a month with the following parameters:
     Expired=Yes
     Program Name=NULL
     Program Tag=NULL
    
7)The program "PURGE SIGNON AUDIT DATA" should be scheduled to run within  the next 30 days with the following parameter value:
      Audit date: <30 days prior to the scheduled run date>
In addition, the "Increment date parameters each run" scheduling option should be selected for the scheduled run of the program.
    

The Best practices to reduce the patching downtime (Execution point view)

1)Use Hotpatch option:
---------------------
where ever Possible apply the patches in the hotpatch mode (ihelp patches, One off patches (small patches) can be applied in hotpatch mode), In hotpatch mode there is no downtime required, Patch can be applied when the services are running.


Note : hotpatch mode is not suggested/supported for patching, It must be used in extreame situations.




2)Use adpatch options:
---------------------
adpatch provides multiple options which can be used reduce the downtime, Eg: No compile DB, No Compile jsp...etc


These activies can be done later when the services are running.


3)Merge Patches:
----------------
Merging of the patches is very good option and it reduces the downtime significantly in case where we have Multiple patches to apply.


4)Increase the batch size during the patching:
----------------------------------------------
Increasing the batch size to higher value (10000) will reduce the patch time by 10%.


5)Distributed AD can be used in Multi Node systems:
---------------------------------------------------
In case of multinode systems we can Distributed AD feature, In this method patch workers will spread and run in all the Applications nodes effectively utilizing the OS resources of others nodes as well.


6)Increase the OS resources (as possible) which help in increasing the the no.of parallel workers of the patch:
---------------------------------------------------------------------------------------------------------------
Having well sized OS resources such as CPU,Memory..etc will increase the patch runtime there by reduces the downtime.




7)Staged APPL_TOP:
-----------------
A staged Applications system represents an exact copy of your Production system, including all APPL_TOPs as well as a copy of the Production database. Patches are applied to this staged system, while your Production system remains up. When all patches have been successfully applied to the test system, the reduced downtime for the Production system can begin.


Please Note:
------------


i) Staged APPL_TOP only reduces the the time required to Apply the patch on Application Node only.(The database part of the patch requires downtime anyway)


ii)Usually Database portion of the patch takes 60-70% of the patching time, So by this method we can only reduce the 30-40% of the patch time,


iii) But staged APPL_TOP is only usefull in case of bulk patching or Upgrades,This approach is not a soultion to the small and day to day patching as this involves lot of preparation (cloning of the Production system to target) and synching back the APPL_TOP to Prod and it is a complex process.

Multi Node to Single Node Cloning - Oracle Apps 11i

Multi Node to Single Node Cloning – Oracle Apps 11i

With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.

Source System here refers to the multi node system to be cloned

Target System refers to the newly to be created single node system

Applications Version 11.5.10

The following Steps are required to be performed on the source system

1. Apply application tier patches using adpatch

Apply patch 4038964
Apply patch 4175764

Both the above patches are include in the consolidated update 2 or CU2 so in case you are on 11.5.10.2 or later you can ignore this step.

2. Maintain snapshot information

Log in as the applications user on each application tier node and run 'Maintain Snapshot Information' by using adadmin.

3. Merge existing APPL_TOPs

Log in to the primary node of your application tier as the application user user and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appsTier merge

This will prompt you with option to merge secondary nodes

Now log in as the applications user to each of the secondary application tier nodes being merged and run:

$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl appltop merge

4. Prepare the source system database tier.

Log on to the database tier of the source system as the oracle user and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier

With this all the pre clone tasks on the source system have been completed.

The next set of tasks is required to be carried out on the target system that is the system on which you wish to place the merged single node instance.

5. Copy the following application tier directories

Copy the following application tier directories from the primary node of your source system to the target application tier node, retaining the original directory structure:

– [APPL_TOP]
– [OA_HTML]
– [OA_JAVA]
– [COMMON_TOP/util]
– [COMMON_TOP/clone>
– [806 ORACLE_HOME]
– [iAS ORACLE_HOME]

6. Copy the required files for merging

Log in as the applications user to each of the secondary source nodes and recursively copy:

directory [COMMON_TOP]/clone/appl
- to -
directory [COMMMON_TOP]/clone/appl on the target system node

Before proceeding with the next steps you must shutdown your oracle applications services and the database on the source system

  7. Copy the database tier file system

Log on to the source system as the database user

Copy the database (DBF) files from the source to the target system
Copy the source database ORACLE_HOME to the target system

After this you can now startup the database and applications services on your source system and release it for use.

8. Configure the target system database server

Log on to the target system as the database user and type the following commands to configure and start the database:

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

This will prompt for new ORACLE_SID,ORACLE_HOME,Port Pool,JAVA_TOP and DATA_TOP give the appropriate values matching your target system

Once successful this should start your database and listener

9. Configure the application tier server nodes

The database and its listener should remain up before executing the next set of commands.
Log in to the merged APPL_TOP node as the applications user and execute the following commands:

$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier

This will prompt you new port pool for application tier services as well as new APPLTOP,COMMON_TOP,ORACLE_HOME and IAS_TOP

Successful completion of this task will bring up your application tier services on the target or the cloned node.

10. Post Clone Tasks

Log in to the target system application tier node as the APPLMGR user.

1.      Run the following tasks in adadmin for all products:o generate JAR files
o generate message files
o relink executables
o copy files to destination

2.      Change Apps,system,sysadmin passwords using FNDCPASS

3.      Update the following tables to clean up the source entries:

   - update wf_notification_attributes

- update wf_item_attribute_values

- update wf_systems

- update fnd_concurrent_requests log & our directories

- update fnd_concurrent_queues target_node names

4. update the profile options:  

   -Site Name & any custom profile options

FNDCPASS – Oracle Applications 11i & R12

What is FNDCPASS?

To change the password in Oracle Applications 11i & R12, The FND binary which will help us is doing these things is FNDCPASS. This is present in $FND_TOP/bin directory.

FNDCPASS is a utility change password in Oracle Applications 11i and R12.

Using FNDCPASS

Below is the usage for FNDCPASS

You can just type FNDCPASS and press enter , it will give you these details.

Gather Schema Statistics Using FND_STATS.

Gather Schema Statistics Using FND_STATS.

1. Gathers specified schema level statistics

2. Backs up existing statistics

3. Creates the histogram for the specified columns in the FND_HISTOGRAM_COLS tables
4. Populates default statistics for all the interface tables as defined in the FND_EXCLUDE_TABLE_STATS table.

What is oraInventory

What is oraInventory

The Orainventory is the location for the OUI's Book keeping

The inventory stores information about.

• All the Oracle software products installed on all ORACLE_HOMES on a machine
  
• Other non-oracle products such as Java Runtime env's (JRE)
  

Socket to Servlet conversion - Oracle Apps 11i

A)How to identify the Forms connect mode:

grep -i connectMode $COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg

If the above command returns connect mode as http/https -> The forms are running in Servlet Mode:

If the above command returns connect mode as socket -> The forms are running in Socket Mode:

Socket to Servlet conversion (vice - versa) - Oracle Apps 11i

A)In Servlet mode the context file values looks like the following:

<server_url oa_var="s_forms_servlet_serverurl">/forms/formservlet</server_url>

<servlet_comment oa_var="s_forms_servlet_comment"/>

<forms_connect oa_var="s_frmConnectMode">https</forms_connect>

B)In Socket mode the context file values looks like the following:

$APPL_TOP/admin/SID_hostname.xml

<server_url oa_var="s_forms_servlet_serverurl"/>

<servlet_comment oa_var="s_forms_servlet_comment">#</servlet_comment>

<forms_connect oa_var="s_frmConnectMode">socket</forms_connect>

C)Edit the context file as required (servlet or socket) and run the autoconfig to reflect the change

D)Verify the Forms connect mode and start the services

grep -i connectMode $COMMON_TOP/html/bin/appsweb_$CONTEXT_NAME.cfg

check the connectMode socket or http(s)

For more information on socket or servlet mode please go to http://www.dbatutor.com/2010/12/forms-servlet-or-socket-mode-which-is.html

Forms Servlet or Socket Mode - Which is better ?

Forms Servlet or Socket Mode - Which is better ?
A good article from Steve Chan Blog (http://blogs.oracle.com/stevenChan)

Many products within the Oracle E-Business Suite have screens that are built with Oracle Forms. Oracle Forms can be run in either servlet mode or socket mode. Apps 11i is based on Forms 6i and is configured to run in socket mode by default. Apps 12 is based on Forms 10g and is configured to run in servlet mode by default. What are these modes, and which is better?

What is Forms Servlet Mode?
The Forms Listener Servlet is a Java servlet that delivers the ability to run Oracle Forms applications over HTTP and HTTPS connections. It manages the creation of a Forms Server Runtime process for each client, as well as network communications between the client and its associated Forms Server Runtime process.
The desktop client sends HTTP requests and receives HTTP responses from the web server. The HTTP Listener on the web server acts as the network endpoint for the client, keeping other servers and ports from being exposed at the firewall.

What is Forms Socket Mode?
Initial releases of the Oracle Forms Server product used a simple method for connecting the client to the server. The connection from the desktop client to the Forms Listener process was accomplished using a direct socket connection. The direct socket connection mode was suitable for companies providing thin client access to Forms applications within their corporate local area networks. For the direct socket connection mode, the client had to be able to see the server and had to have permission to establish a direct network connection.

Although the direct socket connection mode is perfectly suited for deployments within a company’s internal network, it's not the best choice for application deployment via unsecured network paths via the Internet. A company connected to the Internet typically employs a strict policy defining the types of network connections that can be made by Internet clients to secure corporate networks. Permitting a direct socket connection from an external client exposes the company to potential risk because the true identity of the client can be hard to determine.

Servlet Mode Advantages
1. HTTP and HTTPS traffic is easily recognizable by routers, while socket mode communications is generally considered suspect and treated on an exception basis.
2. Existing networking hardware can be used to support basic functions such as load-balancing and packet encryption for network transit.
3. More resilient to network and firewall reconfigurations.
4. More robust: servlet connections can be reestablished if network connections drop unexpectedly for Forms, Framework, and JSP-based pages.
5. Is the only supported method for generic Oracle Forms customers, and therefore is more thoroughly tested by the Forms and E-Business Suite product groups.
6. Performance traffic can be monitored via tools like Oracle Real User Experience Insight (RUEI).
7. Socket mode is not supported on Windows-based server platforms.

Socket Mode Advantages
1. Uses up to 40% less bandwidth than Forms servlet mode. This may be perceived by Wide Area Network (WAN) users as causing slower responsiveness, depending upon network latency.
2. Uses fewer application-tier JVM resources than servlet mode, due to fewer TCP turns and lack of overhead associated with HTTP POST handling.
Switching Apps Deployments Between Modes
Due to its numerous advantages, Forms servlet mode is the preferred and recommended deployment model for Forms on the web.
There may be circumstances where you need to switch between the default Forms modes. You might wish to switch your Oracle E-Business Suite Release 12 environment to socket mode to improve performance or reduce network load. You might wish to switch your Apps 11i environment to servlet mode as part of your rollout to external web-based end-users outside of your organization.
If you're running Apps 11i and would like to switch to servlet mode, see:
· Using Forms Listener Servlet with Oracle Applications 11i (Note 201340.1)
If you're running Apps 12 and would like to switch to socket mode, see:
· Using Forms Socket Mode in Oracle Applications Release 12 (Note 384241.1)

Enable Multi Language - NLS with Oracle Applications 11i

How to enable Mutilple languages (NLS) with Oracle Applications 11i instance

The below process guides through the step by step process of enable multi language in Oracle Ebiz - 11i instance.
Have taken French as example language to enable in the below steps, You can choose the language you wish to enable in the oracle applications.

Follow the below process to enable the NLS, Please note the base language will be English only.

1)Install the required Language (French) from OAM.

Enabling the Arabic from OAM, folllow the below steps

Login to OAM as a sysadmin -> sitemap -> License Manager -> License -> Languages And license the following language

Enable the "French"

Make sure you should not change the base language, it should be english.

2)Validate the language activated

Login to application with apps user and execute the below command.

Select NLS_LANGUAGE from FND_LANGUAGES where INSTALLED_FLAG in ('B','I');

Make sure you get below result.

1. AMERICAN
2. French

Here base lang is American

3)Stop the Oracle application services

cd $OAD_TOP/admin/scripts
./adstpall.sh apps/apps

4)Run Maintain Multi-lingual Tables

AD Administration Main Menu > Maintain Applications Database Entities Menu using adadmin.

5)Run Update current view snapshot from adadmin

adadmin -> Maintain Applications Files -> Maintain snapshot information -> Update current view snapshot)


6)Run the Translation Synchronization Patch utility (adgennls.pl)

Login to applmgr user in application tier, make sure enviorment is sourced properly and execute the following command

perl $AD_TOP/bin/adgennls.pl

Above command will genertate the manifest file which you need to upload to support. Menifist file will be on following location:

$APPL_TOP/admin/$TWO_TASK/out/adgennls.txt

7)Upload the manifest file to oracle support, use the below steps.

Upload the adgennls.txt file to https://updates.oracle.com/TransSync make sure you give your exact email id.
Once you upload the file, select the option Get Latest Translstions and click on next it will provide you the patch number which support is going to generate for NLS syncronization.

A Translation synchronization patch will be generated specifically based on your manifest for each of your active language. The patch will synchronize the language file versions and American English file versions in your Applications instance.
Note : it is suggested option: If you select the option to get latest translations, the patch will also bring your translations up-to-date.

If you do not receive any email regarding your request within 48 hours, you may contact Oracle Support for assistance.

this patch will generate NLS media patck, it will take some time to generate


8)Apply the Translation Synchronization patch

Follow the instructions in the README file to apply the patch.

note: Before Applying patch make sure enough space in appl top directory, patch initially copy all required files to appl top create new lang patch Choose a directory that contains enough space for the NLS updates (about 10 GB for each language Minimum).


9)AD Administration utility to generate message files from the Generate Applications Files menu.

10)Compile the invalid objects using utlrp.

11)Complie Forms and Reports

12)Complile Apps schema and validate apps schema

13)Bring up the applications services

What is FNDLOAD

What is FNDLOAD
==============

The Generic Loader is a concurrent program named FNDLOAD. The concurrent executable takes the following parameters:
FNDLOAD apps/pwd 0 Y mode configfile datafile entity [ param ... ]

where

The APPS schema and password in the form
username/password[@connect_string]. If connect_string is omitted, it is taken in a
platform–specific manner from the environment using the name TWO_TASK.

<> Concurrent program flags

mode UPLOAD or DOWNLOAD. UPLOAD causes the datafile to be uploaded to the
database. DOWNLOAD causes the loader to fetch rows and write them to the datafile.

The configuration file to use (usually with a suffix of .lct, but not enforced or
supplied by the loader).

The data file to write (usually with a suffix of .ldt, but not enforced or supplied by
the loader). If the data file already exists, it will be overwritten.

The entity(ies) to upload or download. When uploading, you should always upload
all entities, so specify a ”–” to upload all entities.

< [param] > Zero or more additional parameters are used to provide bind values in the access
SQL (both UPLOAD and DOWNLOAD). Each parameter is in the form
NAME=VALUE. NAME should not conflict with an attribute name for the
entities being loaded.



Syntax
=======

An example of downloading is:
----------------------------

FNDLOAD apps/apps@TEST 0 Y DOWNLOAD testcfg.lct out.ldt FND_APPLICATION_TL APPSNAME=FND

This command does the following:

connects to apps/apps@devd
downloads data using the configuration file testcfg.lct
writes data to data file out.ldt
downloads the FND_APPLICATION_TL entity with APPSNAME parameter defined as value FND’


An example of uploading is:
--------------------------

FNDLOAD apps/apps@custdb 0 Y UPLOAD fndapp.lct fnd_exmpl.ldt

This command does the following:
connects to apps/apps@custdb
uploads data using the configuration file in fndapp.lct from datafile in fnd_exmpl
The contents of the entire data file is uploaded.


FNDLOAD Load Options
---------------------

Application level OR single entity level download
Entire OR Partial upload of a data file
Custom mode force update
Support for NLS uploads



AOL ENTITIES
-------------

FNDLOAD an be used for the below Application entities.


Concurrent program definitions
Request groups
Request Sets
Lookup types and lookup values
Profile options and profile option values
Flexfields setup data
Flexfield Value Sets
Descriptive Flexfields
Key Flexfields
Flexfield Value Security Rules
Flexfields Value Hierarchies (Rollup Groups)
Flexfields Values
Attachments definitions
Messages
Menus
Responsibilities
Security information
Etc..



Examples:
========

A)Concurrent Program Definitions:
---------------------------------

The concurrent program configuration file afcpprog.lct downloads and uploads concurrent program definitions. It takes as parameters program name and application name. The following table lists the entities, sub-entities (if any), and download parameters for this configuration file.


Download
-----------
FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="prod" CONCURRENT_PROGRAM_NAME="concurrent name"

Upload
-----------
FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt

B)Request Groups Configuration File:
------------------------------------

Use the file afcpreqg.lct for loading request group data. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.


Download
---------

FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="prod"

Upload
------
FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt

C)Request Sets Configuration File
----------------------------------

Use the file afcprset.lct for loading request group data. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.

Download
---------
FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME="prod" REQUEST_SET_NAME="request set"

Upload
---------
FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt


D)Lookups Configuration File
----------------------------

Use the file aflvmlu.lct for loading Lookup types and Lookups values. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.

Download
---------
FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="prod" LOOKUP_TYPE="lookup name"

Upload
-----
FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt

E)Profile Options and Profile Values Configuration File:
-------------------------------------------------------
Use the file afscprof.lct for loading profile options and profile values. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.

Download
---------
FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="prod"

Upload
---------

FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt



F)Flexfield Value Sets:
----------------------
The entity VALUE_SET includes the following table details of table validated value sets, and user exit details of special/pair validated value sets. It does not include the values, security rules, rollup groups, or value hierarchies for the value set. These entities should be
downloaded and uploaded separately.
The key for this entity is FLEX_VALUE_SET_NAME.

Download
---------
FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

Upload
---------

FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

G)Responsibilities Configuration File:
-------------------------------------
Use the file afscursp.lct for downloading and uploading forms, functions, menus, and menu entries. The following table lists the entities, sub–entities (if any), and download parameters for this configuration file.

Download
---------

FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility"

Upload
---------

FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt

Download Scripts:

Program Name	Scripts For Downloading
Concurrent Program	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME="prod" CONCURRENT_PROGRAM_NAME="concurrent name"
Request Groups	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME="request group" APPLICATION_SHORT_NAME="prod"
Request Sets	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME="prod" REQUEST_SET_NAME="request set"
Lookups	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="prod" LOOKUP_TYPE="lookup name"
Profile Options	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME="profile option" APPLICATION_SHORT_NAME="prod"
Value Sets	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"
Descriptive Flexfield	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX P_LEVEL=?COL_ALL:REF_ALL:CTX_ONE:SEG_ALL? APPLICATION_SHORT_NAME="prod" DESCRIPTIVE_FLEXFIELD_NAME="desc flex name" P_CONTEXT_CODE="context name"
Key Flexfield	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX P_LEVEL=?COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL? APPLICATION_SHORT_NAME="prod" ID_FLEX_CODE="key flex code" P_STRUCTURE_CODE="structure name"
Value Sets with values	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"
Messages	FNDLOAD apps/apps@db 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct file_name.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='prod' MESSAGE_NAME='message name'
Menus	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME="menu_name"
Responsibilities	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY="responsibility"
Printer Styles	FNDLOAD apps/apps@db O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME="printer style name"
Spread Table	FNDLOAD apps/apps@db 0 Y DOWNLOAD $FND_TOP/patch/115/import/jtfgrid.lct IEX_CASE.ldt JTF_GRID_DATASOURCES GRID_DATASOURCE_NAME="IEX_CASE"

Upload Scripts:

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

Program name	Scripts For Uploading
Concurrent Program	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt
Request Groups	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt
Request Sets	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt
Lookups	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt
Profile Options	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt
Value Sets	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt
Descriptive Flexfield	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt
Key Flexfield	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt
Value Sets with values	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt
Messages	FNDLOAD apps/apps@db 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct file_name.ldt
Menus	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt
Responsibilities	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt
Printer Styles	FNDLOAD apps/apps@db O Y UPLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt
Spread Table	FNDLOAD apps/apps@db 0 Y UPLOAD $FND_TOP/patch/115/import/jtfgrid.lct IEX_CASE.ldt