Sunday, July 22, 2012

Fusion Applications Installation FAQ - I

=> Why Oracle Fusion Applications?

Designed from the ground up using the latest technology advances and incorporating the best practices gathered from Oracle's thousands of customers, Oracle Fusion Applications are 100 percent open-standards-based business applications that set a new standard for the way we innovate, work, and adopt technology. Built on a set of unique design principles, only Oracle Fusion Applications set a new standard for business.

Oracle Fusion Applications are a complete, standards-based platform.
Oracle Fusion Applications also provide a flexible approach to adoption and deployment.
Oracle Fusion Applications application and process leadership give you the “best-of-the-best” combination.

=> What ar ethe different version of the Fusion Applications Available now?

The base (First) Version of Fusion Applications is
Oracle Fusion Applications 11g (11.1.1.5.1)  -
Oracle Fusion Applications 11g (11.1.2.0.0)  - RUP1
Oracle Fusion Applications 11g (11.1.3.0.0)  - RUP2
Oracle Fusion Applications 11g (11.1.4.0.0)  - RUP3 (Latest)
=> You can directly install any version or upgrade to that version, i.e IN order to install RUP3, We dont require the base version to be installed first.
 Directly RUP3 can downloaded and installed.


=> How big is it?
The software size is approx 50GB

=> What are the different components of Fusion Applications ?

Fusion Applications is combination of two families

1)IDM Family
2)Fusion Applications Family

1) Identity Management (IDM) for Fusion Applications involves installation of the following:

• Oracle Database 11g R2
• JDK (JRockit 64-bit)
• Oracle WebLogic Server
• Oracle Fusion Middleware Web Tier (Oracle HTTP Server)
• Oracle Fusion Middleware SOA Suite
• Oracle Identity Management (OID and OVD)
• Oracle Identity and Access Management (OIM and OAM)
• Oracle Access Manager WebGate

2) Fusion Applications installation of the following:

• Oracle Database 11g R2
• JDK (JRockit 64-bit)
• Oracle WebLogic Server
• Oracle Fusion Middleware Web Tier (Oracle HTTP Server)
• All the modules of Fusion Applications deployed as Weblogic Domains
  - The numbers of managed/applications servers depends on the number of modules chosen to install, This number can go as high as 60+

...watch this space for more updates on Fusion Applications

Saturday, July 21, 2012

Fusion Applications (FA) Installation

Have completed Fusion Applications Installations, 

Watch this space for more information on Fusion Applicatins Installation and Administration........

Below are the logn screens of Fusion Applications




Oracle EM 12C Grid Installation


Have recently Installed Oracle EM 12C Grid on Linux x86_64.

EM 12C Grid contains weblogic and JDK , It is installed automatically along with the EM (If you have not already installed weblogic separetely)

Installing Database 11G (11GR1 or 11GR2) is a pre-requisite for installing EM 12c.

Modify the recomended parameters (these will shown while installing) for better performence of EM.

Below are the high level steps:

1) Install Oracle database 11G ( Have installed 11GR2)
2) Remove the EM schema components (SYSMAN) from the database, Using the below command.

$<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>
 3) Install EM 12c by running runinstaller.

Login to EM 12c :

https://exmaple.oracle:7801/em
Login using User ID sysman and password chosen during the install

https://exmaple.oracle.com:7102/console
Login using User ID sysman and password chosen during the install

How To start EM Grid Control follow the steps below:

1. Start the listener
2. Start the database
3. Start OMS11g using the command <EM OMS Oracle Home>/bin/emctl.sh start oms -all
5. Go to the WLS Console and start the EM Domain (if not already started)


Find the below step by step screen shots of EM Installation ....










Friday, March 2, 2012

Upgrade Oracle 11.1.0.7 database to 11.2.0.3 with EBS R12

Upgrade Oracle 11.1.0.7 database to 11.2.0.3 with EBS R12

The below provides high level steps for the upgrade of the EBS database from 11.1.0.7 to 11.2.0.3
The main document to be followed for this upgrade is "Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763.1] "

STEPS:
=====
1)Install 11.2.0.3 software in a different oracle home
If the existing database oracle home is /u01/TEST/db/tech_st/11.1.0, You can create directory /u01/TEST/db/tech_st/11.2.0 and install it on this location.

2)Drop SYS.ENABLED$INDEXES (conditional)
If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it:
SQL> drop table sys.enabled$indexes;

3) Run the Pre-Upgrade Information Tool by executing the utlu112i.sql script:
SQL> SPOOL upgrade.log
SQL> @utlu112i.sql

4)Shutdown Apps & DB services

4)Set the environment variables to the new home 11.2.0.3 i.e /u01/TEST/db/tech_st/11.2.0
 a.The ORACLE_BASE environment variable must be set accordingly.
 b.The ORACLE_HOME environment variable points to the new 11.2.0 Oracle home.
 c.The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).
 d.The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.
 e.The PERL5LIB environment variable points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version])

5)Create nls/data/9idata directory
On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.
After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 11g Oracle home.

6)Apply additional 11.2.0.3 RDBMS patches 
Apply the following patches on the NEW ORACLE_HOME:
For all UNIX/Linux platforms:
4247037
9858539
12942119
12960302
13004894

7) Copy initSID.ora from old oracle_home to new oracle_home 11.2.0.3
 set at the initSID.ora
 compatible = '11.2.0'

8)Upgrade the database instance
sqlplus "/ as sysdba"
SQL> STARTUP UPGRADE
Run the catupgrd.sql script, this script is doing the UPGRADE
SQL> spool upgrade.log
SQL>@$ORACLE_HOME/rdbms/upgrade/catupgrd.sql
SQL>spool off
SQL> STARTUP
Run utlu112s.sql to display the results of the upgrade as follows:
SQL> @utlu112s.sql

9)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

10) Set CTXSYS parameter
 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');

11) Copy the listner & tnsnames.ora from old oracle home to new oracle home and modify the oracle home & all the refrences of old entries to new oracl home

12)Copy the old appsutil from 11.1.0.7 ORACLE_HOME to the new ORACLE_HOME. and change in all the files inside appsutil all the references from 11.1.0 to 11.2.0

13)Copy the $ORACLE_11.1.0_HOME/SID_host.env to $ORACLE_11.2_HOME/SID_host.env, make the necessary changes to point the new 11.2.0 home and source the environment.

14)Copy $APPL_TOP/admin/adstats.sql from the apps tier to the database home and execute it in database restrict mode.

15)Run adadmin - recreate grants and synonyms and compile apps schema

16)Upgrade completed - Start the Applications:

Thursday, February 2, 2012

opmnctl start: failed. Can not resolve test.oracle.com for interface any

This issue happned while installing OBIEE 11G and when the installer trying to configure the components its unable to start the opmn.
The further analysing the problem revealed its issue with the opmnctl and its unable to startup

OPMN ERROR:
----------
Can not resolve test.oracle.com for interface any
opmnctl start: failed.

SOLUTION:
---------
The issue is due to improper entries in the /etc/hosts file,
Validate your /etc/hosts and verify the loopback entries (127.0.0.1), The loopback address should be in the below format.
127.0.0.1        localhost.localdomain localhost

If still you have the issue, verify the your network adapters using ifconfig -a

Monday, January 23, 2012

Unable to determine SMTP server to use: set FND_SMTP_HOST

Outpost Processot has encoutered the below error.

This error can be found in OPP logs:
----------------------------------------
[GC 14000K->8905K(20284K), 0.0074280 secs]
ProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST
        at oracle.apps.fnd.cp.opp.EmailDeliveryProcessor.deliver(EmailDeliveryProcessor.java:66)
        at oracle.apps.fnd.cp.opp.DeliveryProcessor.process(DeliveryProcessor.java:91)
        at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
----------------------------------------

Solution:1. Log into System Administrator responsibility.
2. Navigate to Profile - System.
3. Query up the %smtp% profiles.
4. Set the following profile values to the defined host and port:
FND:smtp Host
FND:smtp Port

The Output Post-processor is running but has not picked up this request.


OPP Error in the Log file:

------------------------------------------------------------------------
The Output Post-processor is running but has not picked up this request.
No further attempts will be made to post-process this request, and the request will be marked
with Warning status.
Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.
------------------------------------------------------------------------

Solution:

A) Restart the Output Post Processor and re-test the issue

B) If the above ddint solve your issue, Increase the below profile options and re-test the issue

Concurrent:OPP Process Timeout to 600 (300*2)

Concurrent:OPP Response Timeout TO 240 (120*2)

C) If A and B didnt work, Increase the procesess of the Outpost Processor (double it i.e if you have 1 increase it to 2) from Concurrent - Manager - Define screen

and restart the OPP, That should resolve this issue.

Tuesday, January 17, 2012

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.

k BAD Command received in Invalid state

Workflow Notification Configuration Issue:

Have come across the below issue during the mailer setup using microsoft exchange server:

$ telnet hostname.domain imap
Trying 192.111.111.11...
Connected to hostname.domain .
Escape character is '^]'.
* OK Microsoft Exchange Server 2007 IMAP4 service ready
k login wfuser wfpassword
k BAD Command received in Invalid state.

Solution:
========

Perform the following steps:
1. Oracle Application Manager (OAM)
2. Workflow - Service Components
3. Select Workflow Notification Mailer and click on Edit button
4. Check "Inbound SSL Enabled"
This will allow mailer to use the SSL port 993 of the IMAP server and fix the "Command received in Invalid state" error.