Oracle recently announced certification
for E-Business Suite 11i on Oracle Enterprise Linux 5
So, today I gave it a try, together with a colleague.
The requirements for installing
E-Business Suite on OEL5 can be found in Metalink Note 316806.1
Basically this was the note I followed.
We set up a Virtual Machine running OEL5
â€“ Update 1, and applied all the prerequisites mentioned in the
Installation Update Notes (Metalink Note 316806.1)
After installation of OEL, the
following packages were downloaded from
Under â€œSetting the environmentâ€,
bullet 2 there is an instruction to modify ld. Because there was an
existing ld binary, we decided to backup this one and then create the
<font face="Courier 10 Pitch"># mv /usr/bin/ld /usr/bin/ld.org<br /># ln -s /usr/bin/ld215 /usr/bin/ld</font>
We were then instructed to download and
apply the OS library patch 6078836 from OracleMetaLink and
create the following symbolic link (the patch will instruct you to
copy libdb.so.2 to /usr/lib only):
<font face="Courier 10 Pitch"># ln -s /usr/lib/libdb.so.2 /usr/lib/libdb.so.3</font>
After this, things became rather
(Quote from the Installation Update
Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux
Enterprise Server 10 customers, the LD_ASSUME_KERNEL environment
variable should be unset before starting the installation. The
installation fails when the LD_ASSUME_KERNEL variable is set by the
adgetlnxver.sh file during the course of the installation.
contains the fix for adgetlnxver.sh file. The below mentioned
procedure is a guideline for replacing the adgetlnxver.sh file in the
Oracle Applications 11i shiphome.
Download the patch 6365595 from OracleMetalink.
Follow the Oracle
Applications Installation guide and set up the stage area.
Set the STAGE_TOP environment variable to the top level
directory of the stage area that contains the subdirectories
startCD, oraApps, oraDB, oraiAS and oraAppDB. Make sure that the
stage area is read writable.
Create the following directories in the stage area.
mkdir -p $STAGE_TOP/oraDB/Disk3/db/stage/appsutil/bin
# mkdir -p
Copy the adgetlnxver.sh file in the patch 6365595 to the
following directories created in earlier step.
# cp -p
# cp -p
Update the zip archive with the fix (adgetlnxver.sh file).
# zip -u dboh0_appsutil
# zip -u ad_CORE0
When we applied the above instructions,
we found out that $STAGE_TOP/oraDB/Disk3/db/stage/dboh0_appsutil.zip
could not be modified this way. Somehow, zip -u wouldn’t update the
zip file. Instead, we unzipped this file into a different location,
copied the patched adgetlnxver.sh into its appropriate location, and
zipped the directory structure using zip -r and put the new zip file
back into place. ad_CORE0.zip didn’t report any problems. It just
told us that adgetlnxver.sh was added to the archive (with 79%
Having completed all of the remaining
pre-installation activities, we fired off rapidwiz.
Rapidwiz reported problems on the
system utilities check: PD KSH wasn’t found. I couldn’t find it on
the OEL Cd’s, so I just ignored the warning (found some post on otn
forums that it could be safely ignored…) and started the
installation. It went on fine, until the Post Install Checks were
The Post install checks failed for DBC
file, HTTP, JSP and PHP. Apparently the DBC hadn’t been created,
HTTP, JSP and PHP failing subsequently.
We opened a terminal and started
investigating. First, we sourced the Applications Tier environment
file. Funny enough, after sourcing this file, we weren’t able to do
much more than change directories. Commands like ls, ps, etc. simply
didn’t work anymore, because of missing libraries (librt.so.1,
libdl.so.2, etc). We got the feeling that somehow, LD_ASSUME_KERNEL
was being set, even though we applied the patched version of it to
the zipfiles in the stage area of 11i before starting the
installation. Sourcing the environment file once again and issuing
<font face="Courier 10 Pitch">$unset LD_ASSUME_KERNEL</font>
we were able again to do ls, ps, etc.
Apparently, LD_ASSUME_KERNEL was being set after all…
Then, we found out that
$AD_TOP/bin/adgetlnxver.sh was the original (unpatched) version. We
copied the file from the patch once again, this time straight into
$AD_TOP/bin, and ran autoconfig again (we tried this earlier with
errors as a result). This worked. Autoconfig completed successfully.
We restarted the application processes
using adstrtal.sh and ran the Post Install Checks by rapidwiz once
more. This time everything checked OK.
Now, we have to upgrade our database to
10G Release 2, because 9i is not supported on OEL5.
We will be busy for a while…