Oracle released EBS 12.2.5 installation files to E-Delivery in Oct 2015. Since then, I started trying install this monster in Windows environment (obviously running in VMWare).
As expected, the installation never went smooth, or never went completed after numerous attempts. Frustration ? Not at all. This is Oracle EBS. The sun will rise from the west if the installation works well in the first attempt.
As expected, the installation never went smooth, or never went completed after numerous attempts. Frustration ? Not at all. This is Oracle EBS. The sun will rise from the west if the installation works well in the first attempt.
By the way, the title "EBS 12.2.X installation" is sort of misleading. The RapidWiz will install the 12.2.0 baseline for you only (or upgrade to 12.2.0). You have to patch it up to 12.2.X after the RapidWiz has done. Finishing the 12.2.0 installation is already an enormous task, and then you have to do all kinds of tweaking, hot patching, fixing, to prepare the RUP patching. Next apply the monster RUP, which gives never ending possible unknown errors, if possible, I simply ignore.
Every time I got an issue, I checked it up in Metalink, and if no solution could be found, I would put the Windows OS aside, and had no intention to fix it by myself. Usually waiting for a month or so a fix will be posted. But not this time. I waited for this patch, 23739986, for 6 months -- strictly speaking, I gave up long time ago (around March) and somehow I found out a patch was released in late August. I gave it a try, and bingo ! The installation finished without error !
So what has this patch fixed ? Here is the bug report….
1.1 CURRENT BEHAVIOR
================
Rapid Install with StartCD 51 fails on some Windows environments where
hostname is in upper case.
The following error is reported during application of patches on the
webtier Oracle Home:
Fatal Error: TXK Install Service
oracle.apps.fnd.txk.config.ProcessStateException: FileSys OS COMMAND Failed :
Exit=3 See log for details. CMD= cmd /c rmdir /s /q
F:\\oracle\\CFRP2\\fs2\\FMW_Home\webtier\OPatch ## Node=NodeId=1597 Type=24
TypeName=filesys_patch_action Name= RefId=927 State=init
ConfigDoc=APPS_OHS_HOME ParentDoc=null Topology=R12 Action=os_cmd at
oracle.apps.fnd.txk.config.FileSysPatchActionNode.doFileSysOSCmd(FileSysPatchActionNode.java:169)
1.2 TECHNICAL OVERVIEW
==================
On some Windows environments where hostname is in upper case, the error
mentioned in Section 1.1 is reported during Rapid Install execution.
On further review of the logs, it is found that patch application on the
webtier Oracle Home is failing as the webtier Oracle Home (OHS) has not
been installed successfully.
After further analysis, it was seen that standalone OHS install via the
installer succeeds on the instance. It is only the install via Rapid
Install that fails.
After further debugging, it was found that the issue is with the way
environment variables are set in the Rapid Install code while executing
the OHS installer.
The InstallService code used by Rapid Install is inherited from 11i and
the code (TXKEnv.java) uses the 'cmd /c set' command on Windows platform
to get the env list and parses it by tokenizing it using the "\n"
delimitor only and not the "\r" delimitor. This works on most of the
Windows environments where Rapid Install has been verified to execute
successfully.
However, on the instance where the issue is seen this logic seems to be
causing issues with the OHS installer as the environment variable values
have a "\r" at the end. This causes the OHS installer being run via RI to
fail. This code is present in TXKEnv.java.
The setRuntimeEnvArray method of TXKProcess.java API is responsible for
reading the environment variables and creating an array of the
environment variables to be passed to the process that executes the OHS
installer.
To fix the issue, the code will be modified to trim the environment
variable values before passing it on to all processes.
0 comments:
Post a Comment