Issues and Fixes with OBIEE

For Installation of the OBIEE please follow my previous post http://balajiabhi.blogspot.com/2009/07/installation-and-configuration-of-obiee.html


Issue:
The login page failed to login using Administrator/Administrator
Fix:
1. Shutdown the oc4j using
$(ORACLE_BI_HOME)/setup/oc4j

oc4j will give the options like
-start
-shutdown -port (ORMI Port) -password (Password which you gave during the installation) for oc4jadmin

ORMI Port:
Locate rmi.xml in the
$ORACLE_BI_HOME/oc4j_bi/j2ee/home/config/rmi.xml
Inside you can get the port of the ORMI Port.
In my case it was 23971
I stopped oc4j
like

ORACLE_BI_HOME/setup/oc4j -shutdown -port 23971 -password Welcome1
Shutdown OC4J instance...

The locate the xmlp-server-config.xml inside
$ORACLE_BI_HOME/ xmlp/ XMLP/ Admin/ Configuration /xmlp-server-config.xml

Change the variableproperty name=”SECURITY_MODEL” value=”BI_SERVER“/
TO
property name=”SECURITY_MODEL” value=”XDO“/
3. Restart the oc4j from
$ORACLE_BI_HOME/setup/oc4j -start
Now the Administrator/Administrator will work
You can now navigate to Admin page from welcome page.

Issue 2:
When you access the Dashboard from the OBIEE Page, you may encounter

500 Internal Error: - servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.

I resolved the issue like this:
1. Edit ./oc4j_bi/j2ee/home/applications/analytics/analytics/WEB-INF/web.xml

Replace the port as 9703 instead of 9710

2. Go to $ORACLE_BI_HOME/setup/

$run-sa.sh stop

wait for 10 seconds

$run-saw.sh stop

wait for 10 seconds

$run-sa.sh start

$run-saw.sh start.

Now click on the application Dashboard. It will work fine.

Installation and Configuration of OBIEE 10.1.3.4.1

The Blog is about installation and Configuration of OBIEE 10.1.3.4 (Basic Installation)

You can obtain OBIEE here

The Prerequisites:
1. JDK1.5.0 or above Download JDK

A Server with temporary tablespace of around 200 MB

Considerations:
The Document follows the installation procedure on RHEL 4 update 5

1. Unzip the biee_linux_x86_redhat_101341.zip
2. It will deploy
about.jsp
biee_linux_x86_redhat_101341_1of1.tar
META-INF
WEN-INF

3. untar the biee_linux_x86_101341_1of1.tar using
$tar -xvf biee_linux_x86_101341_1of1.tar

4. It will create RH_LINUX
Run: Server/Oracle_Business_Intelligence/setup.sh

You follow the screens, and specify the necessary informations

5. Follow the install log located in
$ORACLE_BI_HOME/log/install.log

Once completed you will be given an output stating to browse the html page in the location of Oracle BI HOME

Start working using
http://hostname:port (port will be 9704)/xmlpserver

Issue:
The login page failed to login using Administrator/Administrator
1. Shutdown the oc4j using
$(ORACLE_BI_HOME)/setup/oc4j

oc4j will give the options like
-start
-shutdown -port (ORMI Port) -password (Password which you gave during the installation) for oc4jadmin

ORMI Port:
Locate rmi.xml in the
$ORACLE_BI_HOME/oc4j_bi/j2ee/home/config/rmi.xml
Inside you can get the port of the ORMI Port. In my case it is 23971

I stopped oc4j like
ORACLE_BI_HOME/setup/oc4j -shutdown -port 23971 -password Welcome1
Shutdown OC4J instance...

The locate the xmlp-server-config.xml inside
$ORACLE_BI_HOME/ xmlp/ XMLP/ Admin/ Configuration /xmlp-server-config.xml

Change the variable
property name=”SECURITY_MODEL” value=”BI_SERVER“/
TO
property name=”SECURITY_MODEL” value=”XDO“/

3. Restart the oc4j from
$ORACLE_BI_HOME/setup/oc4j -start

Now the Administrator/Administrator will work

You can now navigate to Admin page from welcome page.

Issues:

When you access the Dashboard from the OBIEE Page, you may encounter

500 Internal Error: - Server error: An exception occured. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.

I resolved the issue like this:

1. Edit ./oc4j_bi/j2ee/home/applications/analytics/analytics/WEB-INF/web.xml

Replace the port as 9703 instead of 9710

2. Go to $ORACLE_BI_HOME/setup/

$run-sa.sh stop

wait for 10 seconds

$run-saw.sh stop

wait for 10 seconds

$run-sa.sh start

$run-saw.sh start.

Now click on the application Dashboard. It will work fine.

Routine AFPPRD has encountered a fatal error. ORA-01000: maximum open

After upgrade during Data Loading using Java Program we got the error :

Routine AFPPRD has encountered a fatal error. ORA-01000: maximum open
cursors exceeded

The Concurrent for Importing the items errored out. The log file of the concurrent is


+---------------------------------------------------------------------------+
Inventory: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
INCOIN module: Import Items
+---------------------------------------------------------------------------+
Current system time is 22-JUL-2009 11:04:39
+---------------------------------------------------------------------------+
**Starts**22-JUL-2009 11:04:40
**Ends**22-JUL-2009 11:05:25
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
Import Items
--------------------------------------------------------------------------------
Argument 1 (ORG_ID) =
Argument 2 (ALL_ORG) = 1
Argument 3 (VAL_ITEM_FLAG) = 1
Argument 4 (PRO_ITEM_FLAG) = 1
Argument 5 (DEL_REC_FLAG) = 1
Argument 6 (PROCESS_SET) = 1001
Argument 7 (MODE) = 1
--------------------------------------------------------------------------------
************************************
TRANSACTION ID : 13652
ORGANIZATION ID : 103
TABLE NAME : MTL_SYSTEM_ITEMS_INTERFACE
COLUMN NAME :
MESSAGE NAME : BOM_PARSE_ITEM_ERROR
ERROR MESSAGE :
************************************
TRANSACTION ID : -1
ORGANIZATION ID : -1
TABLE NAME : MTL_SYSTEM_ITEMS_INTERFACE
COLUMN NAME :
MESSAGE NAME : INV_IOI_ERR
ERROR MESSAGE : *** BAD RETURN CODE b ***
************************************
TRANSACTION ID : -1
ORGANIZATION ID : -1
TABLE NAME : ENI_OLTP_ITEM_STAR
COLUMN NAME :
MESSAGE NAME : INV_IOI_ERR
ERROR MESSAGE : FND+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
ORACLE error 1000 in AFPRSR
Cause: AFPRSR failed due to ORA-01000: maximum open cursors exceeded
.
The SQL statement being executed at the time of the error was: and was executed from the file .
ORA-01000: maximum open cursors exceeded
Routine AFPPRD has encountered a fatal error. ORA-01000: maximum open cursors exceeded

Contact your system administrator or support representative.
Shutting down Concurrent Manager : 22-JUL-2009 11:05:25
ORACLE error 1000 in AFPRSR
Cause: AFPRSR failed due to ORA-01000: maximum open cursors exceeded
.
The SQL statement being executed at the time of the error was: select FND_CONC_PRIVATE_UTILS.get_resub_time(:b0) into :b1:b2 from DU and w
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPPRD has encountered a fatal error. ORA-01000: maximum open
cursors exceeded

Contact your system administrator or support representative.
_ 2 _
Routine AFPPRD has encountered a fatal error. ORA-01000: maximum open
cursors exceeded

Contact your system administrator or support representative.
.............................................................................


As per the Metalink advise, we increased the open_cursors to double the value, still no improvement.
We were restricted to load the data only upto 1500 records at a stretch.

We fixed the problem like this
1. Identify the tablespace and datafile the table is residing in.
2. Add a datafile in the tablespace. (in my case the MTL_Tables were residing in APPS_TS_INTERFACE

3. The error resolved.

Upgrade Oracle E Business Suite 12.0.X to 12.1.1

This blog is about to describe the upgrading from 12.0.x to 12.1.1

This includes Challanges and issues and fixes during the process of upgrade.

This document refers to Redhat Enterprise Linux 4 update 5., Database 10.2.0.2, Forms server version 10.1.2.0.1 and 10g AS Web server 10.1.3

Take a backup of the production before doing (Strong Recommendation)

Metalink Document to refer: 752619.1 (But many challanges ahead if you follow the document)

The as-is server is being 12.0.5 and database is of 10.2.0.2, we upgraded the Database to 10.2.0.4 using Patchset 6810189

Phase I: Process of Database Upgrade:

1. Unzip the p6810189_10204_Linux-x86.zip to a temporary directory which is obtained from metalink.

Source the Database Enviroment File from RDBMS_ORACLE_HOME.

Being the database is of version 10gR2 (10.2.0.2) no need to verify the timezone using v$timezone.

2. Shut down all the application services, DB, listener, isqlplus and emctl dbconsole.

Please do remember, Take a backup of the database and inventory.

3. Go to unzipped directory and run ./runInstaller

if you are using local inventory then use

./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc

If you want to attach your home to the central inventory then do:

$ORACLE_HOME/oui/bin/runInstaller -silent -attachHome -invPtrLoc /etc/oraInst.loc ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=(SID)_DB_HOME_Version

You will get your oracle Home attached with the central Inventory. You can verify using runInstaller -> Installed Products

Select the home and location from the OUI and then proceed to next.

Once completed, startup the database using

$sqlplus as sys user

SQL> startup upgrade;

SQL> spool 'upgrade10204.log'

SQL> @$ORACLE_HOME/rdbms/catupgrd.sql

At the end the script will return the results of upgrade validity. Verify the validity of the database after upgrade.

SQL> shut immediate;

SQL> Startup;

SQL> $ORACLE_HOME/rdbms/utlrp.sql

This will compile all the invalid objects that are added and not compiled during upgrade.

After compilation:

Shutdown the instance and apply the additional RDBMS Patches using Opatch for E Business Suite upgrade.

Please be sure to have OPatch in the PATH

To Include OPatch in the path use

$export PATH=$PATH:$ORACLE_HOME/OPatch

Using Opatch Apply the following Patches

4247037
6600051
6870937
6991626

Don't forget to run adstats.sql from $APPL_TOP/admin again the upgrade process of APPL_TOP. 12.1.1. patchset will run it during its run.

Startup the database. (Time taken for the process to complete ~1h 15mins)

Phase II: (Upgrade 10gAS 10.1.3 to 10.1.3.4)

Important:

1.Take a backup of inventory before proceeding.

2. Source the environment file from $INST_TOP/ora/10.1.3

3. Verify echo $ORACLE_HOME as $ORACLE_APPS_BASE/apps/tech_st/10.1.3

4. Ensure that all the OC4J services are up and running.

1. Unzip and Apply Patch 7272722 obtained from metalink using ./runInstaller

If you are using local inventory please use

./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc

During the process, the OPMN services will be down and started up by the OUI.

When prompted please give the OC4J admin password as either 'secret' or 'oafm' (As I upgraded two instance, one (12.0.6) was successful with 'secret' and another (12.0.5) by 'oafm'.)

This will complete the 10gAS (10.1.3.0.1) to be upgraded with 10.1.3.4

Time taken for this procedure ~ 1 hour.

Shutdown the services, Run Autoconfig on the apps Tier.

As per the metalink document, dont upgrade Opatch version to 1.0.0.0.62, it failed two times for me during the other patches. I advise you to keep the current Opatch as opatch tool.

Be sure, the path of the Opatch is present in the PATH variable.

Apply the following patches:

(if you are using local inventory, then use

Patch_Directory$opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc)

1. 6702510

(The issue is that.. being a general platform Patch, Opatch will fail at the verification of platform)

use $export OPATCH_PLATFORM_ID=0,

then rerun the opatch apply.

2. Apply 6771776 (If you are getting error during opatch as Platform as 196 then use OPATCH_PLATFORM_ID = 46)

3. 7484199

4. 7411481

5. 7139320

6. 7139339

Post Upgrade steps

Source Application environment file

Regenerate appsborg.zip and appsborg2.zip using adadmin

Navigation: adadmin -> Choose Option 1-> Regenerate Product JAR files -> Force Option: No

Run autoconfig in application tier system.

Verify the Upgrade using:

either:

use ./runInstaller and then select installed products, it will show you the components from WEB_OH that are all upgraded to 10.1.3.4

or:

use opatch lsinventory -detail

Look for Oracle Application Server Patchset as 10.1.3.4 as follows:

Installed Patch List:

=====================

1) Patch 7139339 applied on Fri Jul 17 20:03:46 IST 2009 [ Base Bug(s): 7139339 ]

2) Patch 7139320 applied on Fri Jul 17 20:02:23 IST 2009 [ Base Bug(s): 7139320 ]

3) Patch 7411481 applied on Fri Jul 17 20:00:42 IST 2009 [ Base Bug(s): 7411481 ]

4) Patch 6771776 applied on Fri Jul 17 19:58:55 IST 2009 [ Base Bug(s): 6771776 ]

5) Patch 6702510 applied on Fri Jul 17 19:51:41 IST 2009 [ Base Bug(s): 6702510 ]

6) Patch 5586892 applied on Sat Dec 30 08:18:37 IST 2006

[ Base Bug(s): 5586892 5126270 4689959 5238255 ]

Verification from Opatch lsinventory -detail

oracle@xyz.com 7139339]$ opatch lsinventory -detail -
Oracle Interim Patch Installer version 1.0.0.0.56

Copyright (c) 2006 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation underOPatch/docs for usage reference. We also recommend usingthe latest OPatch version. For the latest OPatch versionand other support related issues, please refer to document293369.1 which is viewable from metalink.oracle.com
Oracle Home : /oracle/ACE/apps/tech_st/10.1.3Oracle Home Inventory : /oracle/ACE/apps/tech_st/10.1.3/inventoryCentral Inventory : /oracle/ACE/inst/apps/ACE_samarth/admin/oraInventory from : /oracle/ACE/apps/tech_st/10.1.3/oraInst.locOUI location : /oracle/ACE/apps/tech_st/10.1.3/ouiOUI shared library : /oracle/ACE/apps/tech_st/10.1.3/oui/lib/linux/liboraInstaller.soJava location : /oracle/ACE/apps/tech_st/10.1.3/jre/1.4.2/bin/javaLog file location : /oracle/ACE/apps/tech_st/10.1.3/.patch_storage//*.log
Creating log file "/oracle/ACE/apps/tech_st/10.1.3/.patch_storage/LsInventory__07-17-2009_20-17-29.log"
Result:
PRODUCT NAME VERSION
============ =======
Agent Required Support Files Patch 10.1.0.5.0

Agent Required Support Files 10.1.0.2.0

Apache Module for Oracle Distributed Authoring and Versioning 10.1.2.1.0

Assistant Common Files Patch 10.1.0.5.0

Assistant Common Files 10.1.0.2.0

Bali Share 1.1.18.0.0

DataDirect Connect JDBC Drivers 10.1.2.0.1

DBJAVA Required Support Files Patch 10.1.0.5.0

DBJAVA Required Support Files 10.1.0.2.0

Documentation Required Support Files 10.1.0.3.0

Enterprise Manager Minimal Integration Patch 10.1.0.5.0

Enterprise Manager Minimal Integration 10.1.0.2.0

Enterprise Manager plugin Common Files 10.1.0.2.0

Enterprise Manager plugin Common Files 10.1.0.5.0

Extended Windowing Toolkit 3.3.18.0.0

HTTP Server Files 1.3.31.0.0

Oracle Application Server PatchSet 10.1.3.4.0

Oracle ASkernel Common 10.1.3.0.0

Oracle Business Rules 10.1.3.0.0

.

.
.
OPatch succeeded.

Now upgrade the Opatch using 6880880 (Unzip the patch directly into the 10.1.3 Oracle Home)

Do not Start the application services and try to login to the applications using the port. As it throws login page cannot be displayed as the variable in context are pointing to portal/AppsLogin.jsp.

This will be resolved once you complete applying the patch 7303030.

Phase 3: Upgrading the Java JDK

Download the latest JDK from http://java.sun.com/javase/downloads/index.jsp

download jdk-6u14-linux-i586.bin

1. Be sure to shutdown all the middle tier services.

(a) Perform JDK Upgrade in IAS_ORACLE_HOME:

Navigate to $IAS_ORACLE_HOME/appsutil/

$mv jdk/ jdk_old/

$mkdir jdk/

copy the jdk-6u14-linux-i586.bin to $IAS_ORACLE_HOME/appsutil/jdk

Install the bin file using

$./jdk-6u14-linux-i586.bin

This will install latest jdk in appsutil/jdk

Copy the *.ttf files from $FND_TOP/resource to $IAS_ORACLE_HOME/appsutil/jdk/jre/lib/fonts.

Important: You need to do the steps as a post upgrade step if you complete with 7303030

b) Upgrade jre in $RDBMS_ORACLE_HOME

copy the jdk-6u14-linux-i586.bin to $RDBMS_ORACLE_HOME/appsutil

Source the database environment file

1. Navigate to $ORACLE_HOME/appsutil/

2. mv jre/ jre_old/

3. mkdir jre/

Install the jdk_version_linus-i586.bin to appsutil/jre

Verification of JDK installation

$ADJVAPRG -version

[oracle@prod appl]$ $ADJVAPRG -version

"1.6.0_14"

Java(TM) SE Runtime Environment (build 1.6.0_14-b08)

Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

echo $CLASSPATH

[oracle@prod appl]$ echo $CLASSPATH

/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/lib/dt.jar:

/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/lib/tools.jar:

/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/rt.jar:

/oracle/PRODN/apps/apps_st/comn/java/lib/appsborg.zip:

/oracle/PRODN/apps/tech_st/10.1.2/forms/java:

/oracle/PRODN/apps/tech_st/10.1.2/forms/java/frmall.jar:/oracle/PRODN/apps/tech_st/10.1.2/jlib/ewt3.jar:/

oracle/PRODN/apps/tech_st/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-INF/lib/frmsrv.jar:/oracle/PRODN/apps/apps_st/comn/java/classes

$AFJVAPRG -version

[oracle@prod appl]$ $AFJVAPRG -version

java version "1.6.0_14"

Java(TM) SE Runtime Environment (build 1.6.0_14-b08)

Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

echo $AF_CLASSPATH

Each should reflect the paths belonging to latest JDK like this

[IAS_ORACLE_HOME]/appsutil/jdk/lib/dt.jar, [IAS_ORACLE_HOME]/appsutil/jdk/lib/tools.jar, [IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/rt.jar, and [IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/charsets.jar

Method:1

Create an jsp file under $OA_HTML like jdktest.jsp

The JDK version is:<%= System.getProperty("java.version") %> :<%= System.getProperty("java.version") % >

compile the jdktest.jsp using ojspcompile, syntax is:

perl -x $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s jdktest.jsp'

Dont check it now, as your middle tier services are down.

Check with Database Tier:

$cd $ORACLE_HOME/appsutil/jre/bin

./java -version

[oracle@prod jre]$ cd bin

[oracle@prod bin]$

./java -version

java version "1.6.0_14"

Java(TM) SE Runtime Environment (build 1.6.0_14-b08)

Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

Run Autoconfig on both tiers

Phase 4: Forms server Upgrade

In this Phase upgradation of Forms server from 10.1.2.0.1 to 10.1.2.3 is to be done.

Backup the inventory file.

Source the application environment file

1. Unzip 5983622 and run ./runInstall

2. Supply oc4jadmin as 'secret' when prompted.

(Note here configuration assistant will fail at oc4j configuration Assistant, Simply skip and click next. This is normal behavior for E Business Upgrade)

Once completed:

Apply the Following Patches using OPatch tool from TOOLS_ORACLE_HOME

p3559326_10105_LINUX.zip

p6880880_102000_LINUX.zip (Upgrade Opatch - Skip this patch)

p4407272_10123_LINUX.zip

p7016961_101210_LINUX.zip

p4526825_10123_LINUX.zip

p7016961_10123_LINUX.zip

p5394728_10105_LINUX.zip

p5917053_10123_LINUX.zip

p7121788_10123_LINUX.zip

p5983622_10123_LINUX.zip

p7140392_10123_GENERIC.zip

p6371228_10123_LINUX.zip

p7329300_10123_LINUX.zip

p6857221_10123_LINUX.zip

p8300196_10123_GENERIC.zip

p8374931_10123_GENERIC.zip

Note: if you face the error below during any of the Opatch or ./runInstaller: rwconverter error: like this

/ACE/apps/tech_st/10.1.2/lib//librw.a -lnsl/oracle/ACE/apps/tech_st/10.1.2//lib/

/librw.so: undefined reference to `rolgxinoci_cid'

collect2: ld returned 1 exit status

make: *** [rwbuilder] Error 1

DO the following:

Restore the file

librw.so, and librw.a

from old backup to $TOOLS_ORACLE_HOME/lib and run

$TOOLS_ORACLE_HOME/reports/lib/make -f ins_reports.mk install
The result will be
/oracle/ACE/apps/tech_st/10.1.2/lib,-rpath,/oracle/ACE/apps/tech_st/10.1.2/jdk/jre/lib/i386:/lib:/usr/lib -lm `cat /oracle/ACE/apps/tech_st/10.1.2/lib/sysliblist` -ldl -lpthread -lm -L/oracle/ACE/apps/tech_st/10.1.2/lib -L/oracle/ACE/apps/tech_st/10.1.2/lib/stubs/ -lsnls10 -lpthread -ljvm -lhpi -Wl,-rpath,/usr/X11R6/lib -L/usr/X11R6/lib -lXm -lXt -lX11 -lm -lXp -lXext /oracle/ACE/apps/tech_st/10.1.2/lib//librw.a -lnslmv rwbuilder /oracle/ACE/apps/tech_st/10.1.2/bin/rwbuilderchmod 700 /oracle/ACE/apps/tech_st/10.1.2/bin/rwbuilder

then proceed with the patch, it should complete normally.

Create formsapp.ear

$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp

Enter Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome (or current password)
? No ">Run Autoconfig ? No

If you are prompted for oc4jadmin password

and is incorrect as 'secret' or 'oafm' then

Do the following:
$INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml

$cp system-jazn-data.xml system-jazn-data-ori.xml

$vi system-jazn-data.xml
locate oc4j-admin section
[user]
[name]oc4jadmin[/name]
[display-name]OC4J Administrator[/display-name]
[guid]88836370D11611DC9F30F9C1CD6F1A73[/guid]
[description]OC4J Administrator[/description]
[credentials]{903}F+iG1A46edXG9RdfY0pD2O4Ge/qyEjsg[/credentials]
[/user]

replace
{903}F+iG1A46edXG9RdfY0pD2O4Ge/qyEjsg
with

!Welcome [Please note '!' is important]

then issue oc4jadmin password as 'Welcome'. it will pass the step.

Run Autoconfig on Apps Tier

Apply Interoperability Patch 7120543

Apply OPatch 6880880 as in the previous section to upgrade Opatch tool to 1.0.0.0.62

Rebuild Forms and Reports executables
cd $ORACLE_HOME/forms/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/forms/lib
$ make -f ins_forms.mk install
cd $ORACLE_HOME/reports/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/reports/lib
$ make -f ins_reports.mk install

Regenerate appsborg.zip and appsborg2.zip using adadmin

Phase V upgrading to 12.1.1

Apply AD.B.1 Patch (7461070)

Copy adgrants.sql from patch/admin directory to $RDBMS_ORACLE_HOME/appsutil/admin directory

If it is not present create a directory /admin inside $RDBMS_ORACLE_HOME/appsutil

run adgrants.sql as sys user with syntax

$adgrants.sql apps

once finished, Apply the patch AD.B.1

Recreate grants and synonyms using adadmin

Apply the Main patch 7303030 (Contains 8 parts)

During the patch run, please expect

XDOLoader.class will fail on user xdo

Follow the procedure from http://balajiabhi.blogspot.com/2009/07/rebuilding-xdo-objects-failed-worker-on.html

(Completed within 15 hours)

Apply online Help patch 7303031 using adpatch. (It takes 28 minutes)

Apply the product specific patches as per the metalink document stated above.

Start the application services using adstrtal.sh from $ADMIN_SCRIPT_HOME

Verify the forms version using 'About Applications' from Forms session.

It should show the version as follows

To get other versions, enable about this page link in LOGINPAGE of the server
To do this please do the following:

set the profile option FND: Diagnostics = Yes

Then bounce the middle tier services, you will see a link 'About This Page' at the bottom of the web page

The output of the About this page will give all the particulars about the version upgrade.

Cheers!!! and Best of Luck!!!

FRM-92150: WEB client version too new

The error i faced after upgradation of 12.0.6 to 12.1.1 during forms startup.

FRM-92150: WEB Client version too new

The fix is as below:
Go to TOOLS_ORACLE_HOME (10.1.2)
cd forms/lib (in case of Linux) forms/lib32 (in case of other OS)
run
make -f ins_forms.mk sharedlib
it will create shared library functionalites again to run the forms.
The error will not be there..

Rebuilding XDO objects (Failed worker on 12.1.1 upgradation)

To build XDO objects if you face table or view not found during patching and if worker fails with status Failed on XDOLoader.class on product xdo on user xdo

Then try this:
First verify the application has been licensed with xdo.
1. select object_name,object_type,owner from dba_objects where object_name like 'XDO%';
you should have returned with 153 rows.
2. Select application_id,application_short_name from apps.fnd_application where application_short_name = 'XDO';

3.Recreate objects in XDO using
goto:
$XDO_TOP/patch/115/odf

use the command:
adodfcmp odffile=XDOTMGR.odf userid=applsys/apps changedb=yes priv_schema=system/manager mode=tables touser=apps/apps logfile=xdotables.log

adodfcmp odffile=XDOTMGR.odf userid=applsys/apps changedb=yes priv_schema=system/manager mode=indexes touser=apps/apps logfile=xdoindexes.log

adodfcmp odffile=XDOTMGR.odf userid=applsys/apps changedb=yes priv_schema=system/manager mode=sequences touser=apps/apps logfile=xdosequenc.log

adodfcmp odffile=XDOTMGR.odf userid=applsys/apps changedb=yes priv_schema=system/manager mode=views touser=apps/apps logfile=xdoviews.log

Rerun the patch or restart the failed worker.

OPatch detects your platform as 46 while this patch 6702510 supports platforms:

The Issue with applying the Opatch 6702510 as a process of upgrading the AS 10g 10.1.3.0 to 10.1.3.4

The Issue:
Creating log file "/oracle/PRODN/apps/tech_st/10.1.3/.patch_storage/6702510/Apply_6702510_07-13-2009_10-52-56.log"
Invoking fuser to check for active processes.
OPatch detects your platform as 46 while this patch 6702510 supports platforms:
0 (Generic Platform)
This patch is not suitable for this operating system.
Please contact support for the correct patch.
ERROR: OPatch failed during pre-reqs check.

The Fix:
[oracle@prod 6702510]$ export OPATCH_PLATFORM_ID=0
[oracle@prod 6702510]$ opatch apply
Oracle Interim Patch Installer version 1.0.0.0.56
Copyright (c) 2006 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation underOPatch/docs
for usage reference. We also recommend usingthe latest OPatch version.
For the latest OPatch version
and other support related issues, please refer to document293369.1 which is viewable from metalink.oracle.com
Oracle Home : /oracle/PRODN/apps/tech_st/10.1.3
Oracle Home Inventory : /oracle/PRODN/apps/tech_st/10.1.3/inventoryCentral Inventory : /oracle/oraInventory
from : /etc/oraInst.locOUI location : /oracle/PRODN/apps/tech_st/10.1.3/ouiOUI
shared library : /oracle/PRODN/apps/tech_st/10.1.3/oui/lib/linux/liboraInstaller.so
Java location : /oracle/PRODN/apps/tech_st/10.1.3/jre/1.4.2/bin/java
Log file location : /oracle/PRODN/apps/tech_st/10.1.3/.patch_storage//*.log
Creating log file "/oracle/PRODN/apps/tech_st/10.1.3/.patch_storage/6702510/Apply_6702510_07-13-2009_10-53-29.log"
Invoking fuser to check for active processes.
Backing up comps.xml ...
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Please shut down Oracle instances running out of this ORACLE_HOME(Oracle Home = /oracle/PRODN/apps/tech_st/10.1.3)Is this system ready for updating?Please respond YN >YApplying patch 6702510...
Patching jar files...

Inventory is good and does not have any dangling patches.
Updating inventory...
Verifying patch...
Verifying that patch ID is in Oracle Home inventory.
Verifying jar files.
OPATCH_VERIFY_OK: Patch has been applied.
Backing up comps.xml ...
OPatch succeeded.

Recreating the Central Inventory for Oracle DB Home

Today, when i was about to upgrade the 10.2.0.1 database to 10.2.0.4, i found no home registered in the inventory as told by the OUI.

The OS was formated with root, boot and swap partitions and leaving the oracle software partition unchanged. This removed the central inventory in Linux BOX.

I searched thro the $ORACLE_HOME/Opatch/opatch lsinventory
we got the error message as
[oracle@cvsserver OPatch]$ ./opatch lsinventory
Invoking OPatch 10.2.0.1.0
Oracle interim Patch Installer version 10.2.0.1.0Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home : /oracle/product/10.2.0/db_1
Central Inventory : /home/oracle/oraInventory from : /oracle/product/10.2.0/db_1/oraInst.loc
OPatch version : 10.2.0.1.0OUI version : 10.2.0.1.0
OUI location : /oracle/product/10.2.0/db_1/oui
Log file location : /oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch-2009_Jul_08_13-06-10-IST_Wed.log
LsInventory Session failed:
OPatch failed to locate Central Inventory.
Possible causes are: The Central Inventory is corrupted
The oraInst.loc file specified is not valid.
OPatch failed with error code 72

We recreated the Central Inventory using
$ORACLE_HOME/oui/bin/runInstaller

[oracle@cvsserver bin]$ ./runInstaller -silent -attachHome -invPtrLoc /etc/orainst.loc ORACLE_HOME=$ORACLE_HOME ORACLE_HOME_NAME=OraDBHome_1
Starting Oracle Universal Installer...
No pre-requisite checks found in oraparam.ini, no system pre-requisite checks will be executed.
Please execute the '/home/oracle/oraInventory/orainstRoot.sh' script at the end of the session.
'AttachHome' was successful.

When I search again the opatch lsinventory, i got
[oracle@cvsserver OPatch]$ ./opatch lsinventory
Invoking OPatch 10.2.0.1.0
Oracle interim Patch Installer version 10.2.0.1.0
Copyright (c) 2005, Oracle Corporation. All rights reserved..
Oracle Home : /oracle/product/10.2.0/db_1
Central Inventory : /home/oracle/oraInventory from : /oracle/product/10.2.0/db_1/oraInst.loc
OPatch version : 10.2.0.1.0
OUI version : 10.2.0.1.0
OUI location : /oracle/product/10.2.0/db_1/oui
Log file location : /oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch-2009_J ul_08_13-46-03-IST_Wed.log
Lsinventory Output file location : /oracle/product/10.2.0/db_1/cfgtoollogs/opatc h/lsinv/lsinventory-2009_Jul_08_13-46-03-IST_Wed.txt
--------------------------------------------------------------------------------
Installed Top-level Products (1):
Oracle Database 10g
10.2.0.1.0
There are 1 products installed in this Oracle Home.
There are no Interim patches installed in this Oracle Home.
--------------------------------------------------------------------------------
OPatch succeeded.

Cheers!!!

The requested url /em is not found on the server

During the navingation of Application Server enterprise manager in the SOA Suite, i received a message that ' The requested url /em is not found on the server'

The Cause is that:
During installation of SOA Suite, mistakenly i forgot to check the "Configure this as an Administration OC4J instance".

So the Enterprise Manager control is not enabled in our SOA Suite,
Everything is turned off after this, i had the fix from here
Fix:
The two files you need to touch:
ORACLE_HOME/j2ee/oc4j_soa/config/server.xml
ORACLE_HOME/j2ee/oc4j_soa/config/default-web-site.xml

The values you need to change from the files:
In server.xml find ascontrol and set start="true"
in default-web-site.xml find ascontrol and set ohs-routing="true"
Restart SOA
$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/opmn/bin/opmnctl startall

The requested web page should appear now.

Cheers!!!

[ons-connect] Passive connection 127.0.0.1,6100 missing connect

Today i need to blog out my experience with SOA installation. I received an error stating in opmn.log during configuration of BPEL process manager

09/07/07 09:40:39 [ons-connect] Passive connection 127.0.0.1,6100 missing connect
09/07/07 09:40:39 [ons-connect] Passive connection 127.0.0.1,6100 missing connect

We can try a fix like this:
go to DATABASE oracle home /opmn/conf directory

vi ons.config
there you can find some entries like
localport=6100
remoteport=6200
loglevel=3

Change them safely to (add+1000)
localport=7100
remoteport=7200
loglevel=3

bounce the database listener.
Reason for local connect missing is:
Application server opmn.xml will be having the entry like

notification-server interface="ipv4"
port local="6100" remote="6200" request="6003"/

This port value gets conflict with the database ons process. So the issue arises.

Retry the operation that failed.

Oracle - APPS Configuring SSL on R12 (10gAS)

Today, i need to blog out the configuration of SSL in R12 Environment. The process and steps are as follows. It contains both Middle Tier and DB Tier configurations:

SSL stands for Secure Socket Layer. Data Transferred between Server & Client is secured (Encrypted).Usually data transmitted between client machine & server (Web Server on http protocol & Forms Server on Sockets ) is clear text packets. Any one can put Packet Sniffer between Client machine & Server & can open & read all data transaction between your machine & Server (If he/she has network access) Hacker can get your Username/Password or any sensitive data. This become critical when you have Internet access to Oracle Applications 11i (Usually Self Service Implementation)
The Communication Process between the Tiers:
Communication between Client & Oracle Applications happens via three components.
Oracle Web Server (Initial Connection & all self service access is via Web Server/Apache). If your Form Server is in servlet Mode then Core Applications are also accessed via Web Server (oacore Component)
Oracle Form Server: For Core Oracle Application Access (Forms)
Database : You access web server which in turn talks to database Server via UTL_HTTP package via dad (/pls/$SID)
So You enable SSL on particular component depending on your requirement & component which is accessible over Internet & should be secured. You can Implement across all three component or only one or any two.
Further...
SSL is a technology that defines the essential functions of mutual authentication, data encryption, and data integrity for secure transactions. Exchange of data between the client and server in such secure transactions is said to use the Secure Sockets Layer (SSL).
SSL uses 2 types of Certificates:
1. User certificates:
These are Certificates issued to servers or users to prove their identity in a public key/private key exchange.
2. Trusted certificates:
These are Certificates representing entities that you trust – such as certificate authorities that sign the user certificates they issue.
How SSL works with Middle Tier Oracle HTTP Server:
The client sends a request to the server using HTTPS connection mode.
The server presents its certificate to the client. This certificate contains the server’s identifying information.
The client checks its list of Trust points and compares the information in the certificate with the server’s public key. If it matches, the server is authenticated as a trusted server.
The client sends the server a list of the encryption levels, or ciphers, that it can use.
The server receives the list and selects the strongest level of encryption that they have in common.
The client creates a session key which is used to encrypt the data and sends this session key to the server which can decrypt the data with its private key
How SSL works with Oracle Database Server:
The UTL_HTTP package is used for making HTTP callouts from SQL and PL/SQL to a Web Node (Oracle HTTP server).
When the package fetches data from a Web site using HTTPS, it specifies the location to the Oracle Wallet that resides on the database server. This wallet contains the certificate for the Certifying Authority (CA) who signed the Web node’s server certificate.
Process:
For converting the application into SSL we need to have a Digital certificate. A Certificate Authority is a trusted third party responsible for issuing, revoking, and renewing digital certificates. All digital certificates are signed with the Certificate Authority’s private key to ensure authenticity. The Certificate Authority’s Public Key is widely distributed.
A Certificate Signing Request (CSR) is a digital file, which contains your public key and your name. You send the CSR to a Certifying Authority (CA) to be converted into a real Certificate.
A digital certificate is an electronic document that binds an identity to a pair of electronic keys that can be used to encrypt and sign digital information. A trusted third party, called a Certification Authority (CA), issues certificates. The document is usually in a standard X509 format and contains three elements:
Entity attributes (information about your organization)
Public key (which is bound to your organization)
Digital signature of the trusted CA private key

Verisign (http://verisign.com/) will allow your organization to apply for a free trial certificate, which will be valid for 2 weeks for testing purposes.
Private (Server) Key:
The private key file is a digital file that you generate and for use to decrypt messages sent to you. The certificate request (CSR) that you send to your Certificate Authority (CA) is derived from this private key. Therefore, the resulting digital certificate (containing your public key), which is issued by your CA, is bound to this private key.
We will now look into the actual procedure for enabling the application with SSL. Not that below explanation is based on metalink note ID 376700.1.
Middle tier setup
To start with SSL setup we have to create a certification request through Oracle wallet manager.
Step 1) Create wallet on the apps side
Login to application tier with applmgr user ID and navigate to $INST_TOP/ora/10.1.3 directory and source .env file present at that location. This will make 10.1.3 (IAS_ORACLE_HOME) as your ORACLE_HOME.
Navigate to $INST_TOP/certs/Apache directory.
Backup Apache directory
Start Oracle wallet manager
$ owm &
Navigate Wallet -> NewAnswer No to: “Your default wallet directory doesn’t exist. Do you wish to create it now?”Set the wallet manager password (example. Welcome)
Click Yes when prompted “A new empty wallet has been created. Do you wish to create a certificate request at this time”.
Following screen appears
Common Name – Your hostnameOrganization Unit – Your department nameOrganization – Your company nameLocation/City – Your city nameState/Province – Your state nameCountry - Your country name
Press OK once you fill all information.
Save wallet in $INST_TOP/certs/Apache folder with name (server_name).cer
Once saved, it will ask, “A wallet already exist, you want to override”. You can say yes.Click on certificate Request in the list provided on left side of Oracle wallet manager window and you can see your request contents on right side as seen in below screen.
Wallet -> Autologin (Enable)
Wallet -> Save
Once you get the request content, you have to get the certificates from certifying Authority like verisign. Currently the certificate request that you created is your .cer file. Using this file you can get the actual certificate file, which will be .crt file. Along with that file you will also get your private key file (.key). So after getting certificate you will have 3 files with you
Certificate request file (.cer)
Actual certificate file (.crt)
Private Key file (.key)
Once you get the certificate, you have to generate CA certification file. Since for any SSL certificate we need to have CA(Certifying Authority) file. Some of the certifying authority companies also provide CA files. But here we will see how to generate CA file from certificate file (.crt).
Step 2) Creating your certifying authority’s certificate
Copy/ftp (binary mode) .crt to the your PC desktop
Double-click the file and go to Certification Path tab
Double click on VeriSign/RSA Secure Server CA
Go to Details tab and press Copy to File…
Press Next and select “Base-64 encoded X.509(.CER)” and press next
Give the name as ca
Press Finish
A new ca.cer file will be present in your local PC. FTP back ca.cer file to your UNIX host.
Step 3) Converting the existing cert files
Source the .env file again present at location $INST_TOP/ora/10.1.3
Change dir to $INST_TOP/certs/Apache
Copy .crt, ca.crt, servername.key to the current dir.
Execute the following command:$ORACLE_HOME/Apache/Apache/bin/ssl2ossl -cert ./.crt -key ./.key -cafile ./ca.cer -wallet . -ssowallet yes
Step 4) Appstier setup

Edit the context xml file in $APPL_TOP/admin, change the SSL related variables to SSL values
SSL Related Variables in the Context File
Variable Non-SSL Value SSL Value
s_url_protocol http https
s_local_url_protocol http https
s_webentryurlprotocol http https
s_active_webport same as s_webport same as s_webssl_port
s_webssl_port N/A default is 4443
s_https_listen_parameter N/A same as s_webssl_port

s_help_web_agent url constructed with http protocol and s_webport for both
non-SSL and SSL
s_login_page url constructed with http protocol url constructed with
and s_webport https protocol and
s_webssl_port

• Execute autoconfig
• Bounce the mid-tier services

ERROR:

Ssl Nzos_handshake Failed With Error 28860 From Localhost When Using SSL Only Port For OHS

edit opmn.xml from $ORACLE_HOME/opmn/conf

Locate for ssl

Please update the wallet file location in my case, it was in the $INST_TOP/certs/opmn
Step 5)

DB Tier Setup
Once you run autoconfig on Apps Tier, you need to do wallet setup on DB tier as well. Since R12 is autoconfig enabled, there will be a directory called appsutil in ORACLE_HOME on database side. Follow below steps to carry out the setup on database side.
Login to DB tier as oracle user
Change dir to $ORACLE_HOME/appsutil
Create a new dir with name as wallet

$mkdir wallet
Start Oracle Wallet Manager (owm &)
Wallet -> New
Answer No to: “Your default wallet directory doesn’t exist. Do you wish to create it now?”
Click No when prompted “A new empty wallet has been created. Do you wish to create a certificate request at this time”
Save Wallet
Copy ca.crt from the appl_top to $ORACLE_HOME/appsutil/wallet
Navigate Operations-> Import Trusted Certificate
Navigate to ca.crt
Once import completed. Save wallet
Navigate wallet-> autologin (enable)
Save wallet
Step 6) Sanity check
New Appslogin url: https://(hostname):(port)/OA_HTML/AppsLogin
Notice the lock sign in the statusbar (bottom) of the browser. Click on the sign to verify the certificate
Sanity check all the components.
Login to db as sqlplus apps/(apps password)
select utl_http.request(’https://(hostname):(port)’,null,’file:(path to ORACLE_HOME/appsutil/wallet)’, null) from dual;
It should display the first 2000 Chars of the html page.