You’ve attempted to
install Oracle Applications / E-Business Suite R12 on Windows, and perhaps the installation has not gone smoothly. What with the extensive prerequisites, the patches, the need to download software from third parties, the version sensitivity, the highly fragmented documentation, the poor quality of the pre-installation checks, the bugs, and the instability / non-reproducibility of the installation process, the probability of a smooth, error free installation on a first attempt is comparable to that of finding ... let’s say ... finding a “snowball in a hot hell”!
In this article, we’ll examine some of the most common issues that arise when installing Oracle Applications / E-Business Suite R12 on a Windows server.
| Installation Reproducibility |
Q: I’ve tried installing OAPP R12 in exactly the same way on the same kit and I get different results on different attempts?
Well, what can we say? Been there, seen that! We’ve tried on several occasions to install Oracle Applications / E-Business Suite R12 using identical cloned VMs and the same Rapid Install configuration parameters, only to find that the installation failed in different ways on different occasions (for example, on one occasion by bringing up an error pop-up mid way through the installation and on another only failing when it got to the post-install checks screen).
As to why the installation is not reproducible, our guess is that it has to do with timeouts. If you do get E-Business Suite successfully installed, then you’ll have noted that when you boot up the server on some occasions all the Oracle E-Business Suite services start up of their own accord, and on others some of them time out and need to be started manually. During the installation process there is a lot of starting and stopping of services, so if any of these tasks time-out then the installation process may well fail, even when the starting point and the configuration parameters are identical on each occasion.
Whether or not this is an issue will depend on a whole host of factors, such as the kit, product version, and patches applied. While it’s more likely to occur with low-end kit, it can certainly happen with certified hardware / software, and when all the pre-installation checks have passed.
To minimize the chances that this non-reproducibility will lead to a failed installation, ensure that no users have access to the server and no other software is running concurrently during the installation process (especially software like a virus checker than might start up of its own accord).
It’s worth noting that even if you have a set of installation steps that work, they can cease to work as a result of a very minor change to the operating system. You might think you’re installing on the same “kit” as before, but it could be slightly different – perhaps a security patch has been applied. For example, we’ve found that a base install of Microsoft Windows 2003 R2, Standard Edition, SP2 works, but if the critical updates recommended by Microsoft Windows Update are applied then the installation of E-Business Suite fails. It’s still the same service pack, just subtly different. This version sensitivity could have considerable implications for a production installation: E-Business Suite patching and maintenance are working fine; a critical operating system patch is applied; and E-Business Suite patching and maintenance cease working as they should.
Q: When a Windows Oracle Applications R12 installation has been successful what services should be up and running?
Assuming that the:
SID is “PROD”
Host name is “winhost”
Installation is single node
Pre-install checks have passed
Post-install checks have passed
No errors have occurred during the installation
Machine has been restarted following the installation
then the following 11 services should be present, and 5 services (as indicated in Figure 1) should be up and running.
Figure 1 - Windows Services
It’s normal for the “Oracle Fulfillment Server PROD_winhost” process to start and then stop.
It can take 5-10 minutes for the processes to start up with 4 GB of memory (and much longer if the memory is significantly less).
It’s common for some processes to time-out during start-up. If so, and they are still flagged as “Starting”, then they will usually eventually come up; if not, then restart the processes, and they may well come up on a second attempt.
It’s important to note that even if Oracle Applications appears to work – you can logon and bring up forms – then that does not, in itself, mean that the installation has been successful. If errors have occurred during the installation or if the post-install checks have not passed first time around, then Oracle Applications may appear to work, but you’ll usually find that some of the services have not been installed (often “OraclePROD_winhost_TOOLSASControl” and “OraclePROD_winhost_TOOLSProcessManager”). If the purpose of the installation is for a trial or product evaluation, then a partial installation may not matter, but if the installation is for production purposes, then it would be wise to change the installation procedure / prerequisites and reinstall.
Q: I’ve got a pop-up that’s asking me to look in the log file. Where do I find it?
Unfortunately, it’s a case of “Where do I find them?”, rather than “Where do I find it?”
The details of an Oracle Applications / E-Business Suite installation are recorded in about 400 odd logs files. Now, with such a large number of log files, you might think that good practice would dictate than the vendor would arrange the log files in a meaningful hierarchy, and then place them within a hierarchy of log file directories to ease access, or perhaps create a set of hyperlinked HTML pages, with the leaf pages providing links to the individual logs. Unfortunately, Oracle doesn’t seem to think so. Instead, the log files are scattered across the many installation subdirectories. If you want a complete list, here it is:
C:\Oracle\PROD\apps\apps_st\appl\admin\PROD_winhost\log\ApplyAppsTechStack.log
C:\Oracle\PROD\apps\apps_st\appl\admin\PROD_winhost\log\installAppl.log
C:\Oracle\PROD\apps\apps_st\appl\fnd\12.0.0\log\icmhandle.log
C:\Oracle\PROD\apps\apps_st\appl\irc\12.0.0\mds\ircrefactorMap.log
C:\Oracle\PROD\apps\apps_st\appl\per\12.0.0\mds\refactorMap.log
C:\Oracle\PROD\apps\apps_st\comn\clone\jre\bin\javacache.log
C:\Oracle\PROD\apps\apps_st\comn\clone\jre_BAK_1238630347828\bin\javacache.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\config.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\PROD_ap702app\4871220.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\PROD_ap702app\5336212.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\PROD_ap702app\5394474.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\VIS_ap702app\4.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\VIS_ap702app\4871220.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\VIS_ap702app\5336212.log
C:\Oracle\PROD\apps\apps_st\comn\webapps\oacore\autobuild\log\VIS_ap702app\5394474.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\4742501\Apply_4742501_01-02-2007_09-19-28.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\4742501\Apply_4742501_10-19-2007_23-12-02.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\4742501\RollBack_4742501_02-06-2007_09-38-35.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\4745950\Apply_4745950_01-02-2007_09-20-45.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\4745950\RollBack_4745950_02-06-2007_09-38-57.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5456500\Apply_5456500_01-02-2007_09-28-10.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5456500\RollBack_5456500_02-06-2007_09-39-19.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5563264\Apply_5563264_01-02-2007_10-17-31.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5563264\RollBack_5563264_11-01-2007_12-26-02.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5634746\Apply_5634746_01-02-2007_10-19-43.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5635164\Apply_5635164_01-02-2007_09-20-06.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5635164\RollBack_5635164_11-01-2007_12-23-49.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5689224\Apply_5689224_02-06-2007_09-37-58.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5689224\Apply_5689224_10-19-2007_23-01-46.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5689224\RollBack_5689224_10-19-2007_23-02-20.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5689224\RollBack_5689224_11-01-2007_12-25-08.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5719534\Apply_5719534_01-02-2007_10-16-51.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5907304\Apply_5907304_11-27-2008_12-45-02.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\5907304\RollBack_5907304_03-26-2009_07-53-18.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\6002686\Apply_6002686_01-17-2008_05-03-30.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\6075343\Apply_6075343_01-17-2008_05-04-17.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\6280667\Apply_6280667_01-17-2008_05-00-02.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7140405\Apply_7140405_03-26-2009_07-50-40.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7229760\Apply_7229760_03-26-2009_07-47-55.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7230258\Apply_7230258_03-26-2009_07-49-20.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7329300\Apply_7329300_03-26-2009_08-01-11.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7423007\Apply_7423007_03-26-2009_07-49-58.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7462914\Apply_7462914_03-26-2009_07-48-39.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7486619\Apply_7486619_03-26-2009_07-57-11.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\7608327\Apply_7608327_03-26-2009_07-59-03.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\8300196\Apply_8300196_03-26-2009_08-02-02.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\LsInventory__10-26-2007_12-40-25.log
C:\Oracle\PROD\apps\tech_st\10.1.2\.patch_storage\LsInventory__10-26-2007_12-40-32.log
C:\Oracle\PROD\apps\tech_st\10.1.2\Apache\modplsql\cache\database\dbstatus.log
C:\Oracle\PROD\apps\tech_st\10.1.2\bibeans\log\install_bibeans_common.log
C:\Oracle\PROD\apps\tech_st\10.1.2\BIN\opmn_status.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\configtools2007-01-02_08-55-34AM.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\configtools2007-11-01_08-52-23PM.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\configtools2008-11-27_12-41-29PM.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\emagent.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\emagentfetchlet.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\em-application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\emdctl.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\emias.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\em-web-access.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\formsConfig.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\ipm.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\jaznca.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\ons.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\OracleAPPS_C_HOMEASControlexit.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\OracleAPPS_C_HOMEASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\OraclePROD_ap702app_TOOLSASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\OracleVIS_TOOLS_D_ab_apps_VIS_apps_tech_st_10_1_2ASControlexit.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\OracleVIS_TOOLS_D_ab_apps_VIS_apps_tech_st_10_1_2ASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\reportsConfig.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\server.log
C:\Oracle\PROD\apps\tech_st\10.1.2\cfgtoollogs\service.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory\Templates\bibeans\log\install_bibeans_common.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory\Templates\jlib\log\install_bigraphbean_thin.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory\Templates\reports\jlib\log\install_xrolap.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory-6080584\Templates\bibeans\log\install_bibeans_common.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory-6080584\Templates\jlib\log\install_bigraphbean_thin.log
C:\Oracle\PROD\apps\tech_st\10.1.2\inventory-6080584\Templates\reports\jlib\log\install_xrolap.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\DevSuite\application-deployments\reports\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\DevSuite\log\default-web-access.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\DevSuite\log\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\DevSuite\log\server.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\application-deployments\ADFBCManager\home_default_island_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\application-deployments\BC4J\home_default_island_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\application-deployments\IsWebCacheWorking\home_default_island_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\log\home_default_island_1\default-web-access.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\log\home_default_island_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\log\home_default_island_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\log\home_default_island_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\home\log\home_default_island_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\application-deployments\formsapp\OC4J_BI_Forms_default_island_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\application-deployments\reports\OC4J_BI_Forms_default_island_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\log\OC4J_BI_Forms_default_island_1\default-web-access.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\log\OC4J_BI_Forms_default_island_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\log\OC4J_BI_Forms_default_island_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\log\OC4J_BI_Forms_default_island_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\log\OC4J_BI_Forms_default_island_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.2\jdk\sqlnet.log
C:\Oracle\PROD\apps\tech_st\10.1.2\jlib\log\install_bigraphbean_thin.log
C:\Oracle\PROD\apps\tech_st\10.1.2\NETWORK\log\apps_prodxb19.log
C:\Oracle\PROD\apps\tech_st\10.1.2\opmn\logs\ipm.log
C:\Oracle\PROD\apps\tech_st\10.1.2\opmn\logs\ons.log
C:\Oracle\PROD\apps\tech_st\10.1.2\opmn\logs\service.log
C:\Oracle\PROD\apps\tech_st\10.1.2\reports\jlib\log\install_xrolap.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\j2ee\application-deployments\Oc4jDcmServlet\application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\emagent.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\emagentfetchlet.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\em-application.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\emdctl.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\emias.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\em-web-access.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\OracleAPPS_C_HOMEASControlexit.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\OracleAPPS_C_HOMEASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\OraclePROD_ap702app_TOOLSASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\OracleVIS_TOOLS_D_ab_apps_VIS_apps_tech_st_10_1_2ASControlexit.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\OracleVIS_TOOLS_D_ab_apps_VIS_apps_tech_st_10_1_2ASControlsrvc.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.2\sysman\log\server.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\4880540\Apply_4880540_01-02-2007_10-31-30.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\4912149\Apply_4912149_01-02-2007_10-35-47.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\4952820\Apply_4952820_01-02-2007_10-43-52.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\4992357\Apply_4992357_01-02-2007_10-49-44.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\4997187\Apply_4997187_01-02-2007_10-30-43.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5017026\Apply_5017026_01-02-2007_10-28-52.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5132392\Apply_5132392_01-02-2007_10-41-38.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5249974\Apply_5249974_01-02-2007_10-37-35.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5249974\RollBack_5249974_01-17-2008_05-06-35.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5336264\Apply_5336264_01-02-2007_10-33-04.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5348943\Apply_5348943_01-02-2007_10-33-53.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5389100\Apply_5389100_01-02-2007_10-36-33.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5389204\Apply_5389204_01-02-2007_10-32-23.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5389204\RollBack_5389204_02-06-2007_09-36-00.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5460977\Apply_5460977_02-06-2007_09-28-56.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5460977\RollBack_5460977_01-17-2008_05-10-11.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5472947\Apply_5472947_01-02-2007_10-44-47.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5472947\RollBack_5472947_01-17-2008_05-08-31.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5475997\Apply_5475997_01-02-2007_10-43-11.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5499395\Apply_5499395_01-02-2007_10-51-48.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5513480\Apply_5513480_01-02-2007_10-50-22.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5526722\Apply_5526722_01-02-2007_10-49-07.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5527265\Apply_5527265_01-02-2007_10-48-14.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5576216\Apply_5576216_01-02-2007_10-51-02.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5689163\Apply_5689163_01-02-2007_10-34-30.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5689163\RollBack_5689163_02-06-2007_09-31-22.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5689180\Apply_5689180_01-02-2007_10-35-06.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5863202\Apply_5863202_02-06-2007_09-35-20.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5907304\Apply_5907304_11-27-2008_11-10-05.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\5907304\RollBack_5907304_03-26-2009_08-14-16.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\6083647\Apply_6083647_01-17-2008_05-06-15.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\6488072\Apply_6488072_03-26-2009_08-07-40.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\6702510\Apply_6702510_03-26-2009_08-05-16.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\6877627\Apply_6877627_03-26-2009_08-08-20.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7139320\Apply_7139320_03-26-2009_08-06-53.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7139339\Apply_7139339_03-26-2009_08-10-31.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7147682\Apply_7147682_03-26-2009_08-03-02.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7165764\Apply_7165764_03-26-2009_08-04-33.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7393405\Apply_7393405_03-26-2009_08-09-45.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7411481\Apply_7411481_03-26-2009_08-09-00.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7450830\Apply_7450830_03-26-2009_08-11-24.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7484199\Apply_7484199_03-26-2009_08-06-09.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7486619\Apply_7486619_03-26-2009_08-16-26.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\7692665\Apply_7692665_03-26-2009_08-03-51.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\LsInventory__10-26-2007_12-39-50.log
C:\Oracle\PROD\apps\tech_st\10.1.3\.patch_storage\LsInventory__10-26-2007_12-40-12.log
C:\Oracle\PROD\apps\tech_st\10.1.3\Apache\modplsql\cache\database\dbstatus.log
C:\Oracle\PROD\apps\tech_st\10.1.3\appsutil\jdk\jre\bin\javacache.log
C:\Oracle\PROD\apps\tech_st\10.1.3\ascontrol_status.log
C:\Oracle\PROD\apps\tech_st\10.1.3\cfgtoollogs\configtools2007-01-02_10-22-11AM.log
C:\Oracle\PROD\apps\tech_st\10.1.3\cfgtoollogs\configtools2008-11-27_11-02-08AM.log
C:\Oracle\PROD\apps\tech_st\10.1.3\install\deletelist.log
C:\Oracle\PROD\apps\tech_st\10.1.3\install\oc4j_build.log
C:\Oracle\PROD\apps\tech_st\10.1.3\install\opmn_bpel.log
C:\Oracle\PROD\apps\tech_st\10.1.3\install\opmn_status.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\application-deployments\forms\forms_default_group_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\ascontrol-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\forms\log\forms_default_group_1\system-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\aferror.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\application-deployments\bc4j\home_default_group_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\javacache.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\ascontrol.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\ascontrol-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\home\log\home_default_group_1\system-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\application-deployments\oacore\oacore_default_group_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\ascontrol-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oacore\log\oacore_default_group_1\system-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\application-deployments\mapviewer\oafm_default_group_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\application-deployments\oafm\oafm_default_group_1\application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\applications\mapviewer\web\WEB-INF\log\mapviewer.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\ascontrol.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\ascontrol-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\global-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\jms.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\rmi.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\server.log
C:\Oracle\PROD\apps\tech_st\10.1.3\j2ee\oafm\log\oafm_default_group_1\system-application.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\HTTP_Server~1.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20081127-110429\opmn.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20081127-110429\service.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20090326-013256\opmn.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20090326-013256\service.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20130224-060209\HTTP_Server~1.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20130224-060209\OC4J~home~default_group~1.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20130224-060209\opmn.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\logs_bak_20130224-060209\service.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\OC4J~home~default_group~1.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\opmn.log
C:\Oracle\PROD\apps\tech_st\10.1.3\opmn\logs\service.log
C:\Oracle\PROD\db\tech_st\11.1.0\admin\PROD_ap702app\diag\rdbms\prod\prod\trace\alert_prod.log
C:\Oracle\PROD\db\tech_st\11.1.0\admin\prod_ap735wgs\diag\rdbms\prod\prod\trace\alert_prod.log
C:\Oracle\PROD\db\tech_st\11.1.0\admin\PROD_winhost\diag\rdbms\prod\prod\trace\alert_prod.log
C:\Oracle\PROD\db\tech_st\11.1.0\admin\VIS_ap702app\diag\rdbms\vis\vis\cdump\viscore.log
C:\Oracle\PROD\db\tech_st\11.1.0\admin\VIS_ap702app\diag\rdbms\vis\vis\trace\alert_vis.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\02240334.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\02240549\adconfig.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\02240549\NetServiceHandler.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\ApplyDatabase.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\ApplyDatabase_02240520.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\ApplyDBTechStack_02240353.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\ApplyDBTechStack_02240400.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\dbInstall.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\NetServiceHandler.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\PROD_winhost\ohclone.log
C:\Oracle\PROD\db\tech_st\11.1.0\appsutil\log\VIS_ap702app\StageDBTechStack_04011300.log
C:\Oracle\PROD\db\tech_st\11.1.0\Bundle\Patch7\sqlnet.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\catbundle\catbundle_WINBUNDLE_VIS_APPLY_2009Mar26_05_57_35.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\catbundle\catbundle_WINBUNDLE_VIS_GENERATE_2009Mar26_05_57_31.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2008-11-26_08-20-10-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2008-11-26_08-20-13-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2009-01-14_10-42-00-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2009-01-14_11-39-23-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2009-03-25_11-42-36-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\CfmLogger_2013-02-24_03-59-54-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2008-11-26_08-20-14-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2009-01-14_10-42-01-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2009-01-14_10-42-02-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2009-03-25_11-42-38-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.assistants.server_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.has.common_2008-11-26_08-20-14-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.has.common_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.has.common_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.has.common_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.network.client_2008-11-26_08-20-13-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.network.client_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.network.client_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.network.client_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.patchset.db_2009-01-14_10-42-01-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.rdbms.util_2008-11-26_08-20-11-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.server_2008-11-26_08-20-13-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.server_2009-01-14_11-39-23-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.server_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.server_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2008-11-26_08-20-14-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2009-01-14_10-42-01-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2009-01-14_10-42-02-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2009-03-25_11-42-38-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.ccr_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.console.db_2008-11-26_08-20-14-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.console.db_2009-01-14_10-42-01-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.console.db_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.console.db_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\oracle.sysman.console.db_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\OuiConfigVariables_2008-11-26_08-20-14-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\OuiConfigVariables_2009-01-14_10-42-01-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\OuiConfigVariables_2009-01-14_11-39-24-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\OuiConfigVariables_2009-03-25_11-42-37-PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\cfgfw\OuiConfigVariables_2013-02-24_03-59-56-AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\logs\sqls.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\logs\trace.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\Oracle_Server.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\Oracle_Text.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\PostUpgrade.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\PreUpgrade.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\sqls.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\trace.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\PROD\upgrade1\Upgrade_Directive.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\Oracle_Server.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\PostUpgrade.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\PreUpgrade.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\sqls.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\trace.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\ultraSearchCfg.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\dbua\VIS\upgrade1\Upgrade_Directive.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\emca\emca_2008_11_26_10_26_09.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\emca\emca_2009_01_14_23_10_11.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\opatch\opatch2009-03-26_05-35-02AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\opatch\opatch2009-03-26_05-35-57AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\opatch\opatch2009-03-26_05-37-41AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\cloneActions2009-01-14_11-35-50AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\cloneActions2009-03-25_11-37-59PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\cloneActions2013-02-24_03-53-37AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\installActions2008-11-26_08-07-32AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\installActions2008-11-26_08-20-18AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\installActions2009-01-14_10-28-21PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2008-11-26_08-07-32AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2008-11-26_08-20-18AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2009-01-14_10-28-21PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2009-01-14_11-35-50AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2009-03-25_11-37-59PM.log
C:\Oracle\PROD\db\tech_st\11.1.0\cfgtoollogs\oui\silentInstall2013-02-24_03-53-37AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\database\oradim.log
C:\Oracle\PROD\db\tech_st\11.1.0\diag\clients\user_apps\host_452966407_11\trace\sqlnet.log
C:\Oracle\PROD\db\tech_st\11.1.0\diag\rdbms\vis\vis\trace\alert_vis.log
C:\Oracle\PROD\db\tech_st\11.1.0\diag\tnslsnr\ap702app\prod\trace\prod.log
C:\Oracle\PROD\db\tech_st\11.1.0\diag\tnslsnr\ap702app\vis\trace\vis.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc1.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc2.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc3.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc4.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc5.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc6.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\ap702app\client\clsc7.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\diag\tnslsnr\ap702app\vis\trace\vis.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\diag\tnslsnr\winhost\prod\trace\prod.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc1.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc2.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc3.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc4.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc5.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc6.log
C:\Oracle\PROD\db\tech_st\11.1.0\log\winhost\client\clsc7.log
C:\Oracle\PROD\db\tech_st\11.1.0\md\admin\sqlnet.log
C:\Oracle\PROD\db\tech_st\11.1.0\oc4j\cfgtoollogs\opatch\opatch2008-10-01_06-24-13AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\oc4j\cfgtoollogs\opatch\opatch2008-10-01_06-26-33AM.log
C:\Oracle\PROD\db\tech_st\11.1.0\RDBMS\trace\OraVSSW.Log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\02240741\adconfig.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\02240741\DependencyModeller.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\02240741\NetServiceHandler.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\02240742\DependencyModeller.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\ApplyApplTop_02240741.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\ApplyAppsTechStack_02240600.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\ApplyAppsTechStack_02240610.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\ohclone.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\PROD_winhostjkey.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\02240334.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\aferror.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\CM_PROD_winhost.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\javacache.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\L393191.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\L393192.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\reviver_2013-02-24_14_25_06.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\sqlnet.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\conc\log\startcp.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\rgf\javacache.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\rgf\TXK\Sun_Feb_24_07_43_23_2013\txkSetPathSep_Sun_Feb_24_07_43_23_2013.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\rgf\TXK\Sun_Feb_24_07_45_08_2013\txkSystemJAZNDataMerge_Sun_Feb_24_07_45_08_2013.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\appl\rgf\TXK\txkSetJaznCredentials_Sun_Feb_24_07_44_56_2013.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\jtff_srv_env.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\opmn_env.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.2\network\apps_prod.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\Apache\mod_rewrite.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\Apache\sec_audit.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\Apache\sec_debug.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\global-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\jms.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\rmi.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\server.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\forms\forms_default_group_1\system-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\global-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\jms.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\rmi.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\server.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oacore\oacore_default_group_1\system-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\ascontrol-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\global-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\jms.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\mapviewer-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\rmi.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\server.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\j2ee\oafm\oafm_default_group_1\system-application.log
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\ora\10.1.3\opmn\opmn.log
C:\Oracle\PROD\inst\apps\PROD_winhost\ora\10.1.3\j2ee\oafm\log\ascontrol.log
C:\Oracle\PROD\inst\apps\PROD_winhost\ora\10.1.3\opmn\logs\default_group~forms~default_group~1.log
C:\Oracle\PROD\inst\apps\PROD_winhost\ora\10.1.3\opmn\logs\default_group~oacore~default_group~1.log
C:\Oracle\PROD\inst\apps\PROD_winhost\ora\10.1.3\opmn\logs\default_group~oafm~default_group~1.log
C:\Oracle\PROD\inst\apps\PROD_winhost\ora\10.1.3\opmn\logs\HTTP_Server~1.log
TOTAL: 397 files found
As to the particular log that is associated with an error pop-up. If you were expecting that an error pop-up might name the log file in question, or, preferably, might provide a link that opens up the log at the line containing the error in question, then prepare to be disappointed. Error messages tend to be generic, and the name of the log file that contains the relevant error is not specified in the pop-up.
As a guideline (assuming a SID of PROD and a base installation directory of “C:\Oracle”), the most useful log files are found in the sub-directories of:
C:\Oracle\PROD\inst
In particular, the following two logs usually contain the summary level error details:
C:\Oracle\PROD\inst\apps\PROD_winhost\logs\<99999999>.log
C:\Oracle\PROD\inst\apps\PROD_winhost\admin\log\
<99999999>\adconfig.log
though, you will have to drill down based on the error text to uncover the details.
Q: The log files contain 100s of errors. How do I know which errors are real errors?
With about 400 log files, some of them containing dozens of pages, it’s not practical to manually read through them all when it comes to locating errors. So you’ll need to search the log files to pick out the set of errors that have caused an installation to fail. Unfortunately, errors are not tagged with an identifier that would allow them to be picked up in a search. There is no simple way of distinguishing between lines that are associated with errors and those that are not (for example, a search for “error” will throw up a dozen or so irrelevant lines for every line that is associated with an error). However, if you search using a regex, such as:
([^ ]: Error| Error: [^']|: ORACLE error)
then you should be able to retain the genuine error lines, whilst eliminating most of the spurious ones. This regex will still throw up spurious errors when they are contained within quotes (errors that could be eliminated by a more complex regex), but it will reduce the number of error lines to manageable proportions.
Another headache is that the logs for almost any Oracle product installation will contain a number of errors even when the installation has succeeded and the product is functioning correctly. In the case of E-Business Suite, you can expect the regex above to return hundreds of errors for a successful installation, some of them quite menacing, such as “Fatal error: server exiting”.
If you do succeed in successfully installing E-Business Suite, then it’s a very good idea to run a regex through the log files, and keep the output for future reference when it comes to additional installations and upgrades.
But, if the installation has failed, how do you distinguish the genuine errors from the spurious ones? If you run the regex above on the “C:\Oracle\PROD\inst” subdirectory, then following a successful install you will typically get about nine errors in four files, errors relating to “metrics”, an error relating to “keytool”, and a “Error: 61” error relating to no listener. So, if you run the same regex for a failed installation, then any other errors that you may find are probably genuine, and may shed some light as to why the installation has failed.
Q: Could using the wrong version of unzip be causing corruption of the staging area?
Possibly, but probably not!
Where is Unzip / Zip Used?
Unzip is used in various ways in the course of an E-Business Suite installation. If you’ve downloaded the installation files from E-Delivery, then you first have to unzip these files into the staging area (for example, “C:\StageR12”). By default, Windows does not have a command line “unzip” command. However, as part of the prerequisites you’ll have created a Unix Toolkit Directory and placed it on the system path (typically, you’ll have installed “Cygwin” and placed directory “C:\Cygwin\bin” on the path). So, when you run a batch file containing an “unzip” for each downloaded E-Delivery file it is the version of “unzip” in this directory that will be used.
However, many of the E-Business Suite files are “double zipped”: many of the files in the staging area are themselves zipped. Once the “Rapid Install” wizard starts running, it spends most of its time unzipping these files. However, the “Rapid Install” wizard uses its own version of “unzip”, one that it sources from the staging area, in directory “C:\StageR12\startCD\Disk1\rapidwiz\unzip\NT”.
To make matters even more complicated, the staging area also contains another version of “unzip” (and also “zip”). These files are themselves zipped within file “C:\StageR12\oraAS\Disk2\appsts\stage\tools6_bin.zip”. When the “Rapid Install” wizard is unzipping all the files in the staging area, it also unzips these “unzip / zip” files and places them in directory “C:\oracle\PROD\apps\tech_st\10.1.2\bin”. The “Rapid Install” wizard also places this directory at the beginning of the system path. Hence, any subsequent reference to “unzip” or “zip” will make use of the files in this directory.
The net result is that one version of “unzip” is used to create the staging area files from the downloaded E-Delivery files, another version is used to create the installation files from the staging area files, and yet another version is used subsequently for system maintenance. Clear as mud!
Which Versions of Unzip / Zip should be used?
Now we must ask which version of “unzip” should you be using. The key source is the
Info-ZIP page that details the issues and bugs associated with various versions of “zip” and “unzip”. As far as Windows platforms are concerned:
“Zip” versions before 2.31 and “unzip” versions before 5.52 have a buffer-overrun vulnerability that leads to a privilege-escalation vulnerability.
(in passing, “unzip” versions on Unix before 6.00 have a race-condition vulnerability that could impact security).
The recommendation from Info-ZIP is therefore to use “zip” 2.31 or later and “unzip” 5.52 or later, though it seems to think it is unlikely that the earlier versions would cause any problems in practice.
Oracle, in documents such as Metalink Note ID 230672.1, recommends using “zip” 2.3 or later and “unzip” 5.52 or later – which suggests that Oracle has got it wrong as far as the version of “zip” is concerned.
Which Versions of Unzip / Zip are actually used?
The version of “unzip” that is used to create the staging area will depend on the version of “Cygwin” that is deployed. Oracle states that version 1.7.1-1 or higher is acceptable. The current version is 1.7.17-1. It contains “unzip” version 6.00 by Cygwin (original by Info-ZIP) and zip version 3.0 by Info-ZIP. So while the “zip” version is compliant, the “unzip” version is not compliant with either Info-ZIP’s or Oracle’s recommendations, as it is a modified version of Info-ZIP 6.00.
The version that the “Rapid Install” wizard uses for unzipping the files found in the staging area, the version in “C:\StageR12\startCD\Disk1\rapidwiz\unzip\NT”, is 5.50 from Info-ZIP. So this version is not compliant with either Info-ZIP’s or Oracle’s recommendations.
The versions used for product maintenance post-install, the versions in directory “C:\oracle\PROD\apps\tech_st\10.1.2\bin”, are 5.52 by Info-ZIP for “unzip” and 2.3 by Info-ZIP for “zip”. So the “unzip” version is compliant, but the “zip” version is not compliant with Info-ZIPs recommendations.
Does any of this actually matter?
However, these discrepancies between versions are unlikely to make any difference.
We have usually used “unzip” 5.52 for creating the staging area files. To determine if the “Cygwin” modified 6.00 version of “unzip” might be problematic, we first created a staging area using “unzip” 5.52. For E-Business Suite R12.1, the staging area contains 8727 files spread across 1462 directories. We calculated the MD5 hash of each file and stored it in an XML database. Then we created a second staging area, this time using the “Cygwin” modified 6.00 version of “unzip”. We calculated all the MD5 hashes and compared them with those in the database, and got a perfect match. So, our conclusion is that the “Cygwin” modified 6.00 version of “unzip” is not going to cause any problems.
The other potential problem is that the version of “unzip” used by the “Rapid Install” wizard, 5.50 by Info-Zip, is known to be buggy. However, we’ve successfully installed E-Business Suite using this version, so it is not problematic, at least for E-Business Suite 12.1.
If you’re still concerned, then it might be worthwhile replacing all the “unzip” executables with version 5.52 and all the “zip” executables with version 2.32 and retry the installation / maintenance procedure that has failed. But doing so is unlikely to make a difference.
Q: What should the system path be for an Oracle Applications R12 install?
If you’ve a fresh Windows install the system path will be:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;
Once you’ve finished the prerequisites (assuming you’ve used “Cygwin” as the “Unix Toolkit”), the system path will be:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Cygwin\bin;
If you have to add path components for any other software, then it’s best to place them at the end of this path.
Once the “Rapid Install” wizard has completed the installation, it will have updated the system path to (assuming a SID of PROD):
c:\oracle\PROD\apps\tech_st\10.1.2\bin;
c:\oracle\PROD\apps\tech_st\10.1.2\jdk\jre\bin\classic;
c:\oracle\PROD\apps\tech_st\10.1.2\jdk\jre\bin;
c:\oracle\PROD\apps\tech_st\10.1.2\jlib;
c:\oracle\PROD\apps\tech_st\10.1.3\bin;
c:\oracle\PROD\db\tech_st\11.1.0\bin;
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Cygwin\bin;
| | Post-Install Check Failure |
Q: I’ve got to the post-install screen and only the first four buttons are green?
A common problem when the installation process has been completed is that the “Post-Install Checks” screen appears as follows:
Figure 2 - Post-Install Checks Fail
If a “Retry” doesn’t work, then press “Cancel”, and run the “Rapid Install” wizard with the “restart” option.
cd C:\StageR12\startCD\Disk1\rapidwiz
RapidWizVersion.cmd -restart
The wizard should run through the installation process within a few minutes, and this time all the “Post-Install Checks” might pass.
If not, then try to start up the Oracle E-Business Suite processes directly. Press “Start”, and select the “Administrative Tools” followed by the “Services” menu items. Look down at the list of Oracle processes, and start up any that have failed to start (see Figure 1). The most common culprits are:
OracleServicePROD
Oracle Process Manager for PROD_winhost
These processes often fail to start on a first attempt (note that “OracleServicePROD” will usually start “OracleConcMgrPROD_winhost” as they are dependent services). If so, then restart them. Once all the processes have started, press “Retry” on the “Post-Install Checks” screen. This time all the buttons should go green, and you can finish the installation process.
Note, we’ve found that when the post-install checks fail it’s almost always the case that the installation is incomplete, and some of the services have not been created. You can usually login to E-Business Suite and bring up forms (though you may well have to fix a “FRM-92101” error), which may be good enough if you’re only installing E-Business Suite for evaluation purposes.
Q: I’ve got a “RW-50004: Error code received when running external process. Check log file for details. Running APPL_TOP Install Driver for PROD instance” error?
The RW-50004 error code occurs quite frequently:
Figure 3 - Error Running External Process
Oracle doesn’t specify which of the 400 odd log files it has in mind, but to begin with it’s worth searching all log files under directory “C:\Oracle\VIS\inst”. As the error code is generic, the reasons for the error may vary.
We’ll examine a common case in which the search reveals errors in file (assuming a SID of VIS and a hostname of “ap702app”):
C:\Oracle\VIS\inst\apps\VIS_ap702app\logs\<99999999>.log
and these errors are similar to the following:
RW-50004: Error code received when running external process - Running APPL_TOP Install Driver for VIS instance (line 854)
RW-50010: Error: - script has returned an error: 1 (line 1117)
RW-50004: Error code received when running external process (line 1118)
The first error reported is a consequence of those that occur latter in the log file. The error is reported when the installer processes the “driver” file:
C:\StageR12\startCD\Disk1\rapidwiz\template\adriapps.drv
This file defines two templates to be instantiated, “adrunias.cmd” and “adrunat.cmd”, corresponding to entries:
ad
/template adrunias.cmd INSTE8_APPLY adrunias.cmd
ad
/template adrunat.cmd INSTE8_APPLY adrunat.cmd
The log file confirms that these files have been instantiated (substitutions have been made for the configuration variables in the templates to produce runnable scripts):
instantiate file:
source : C:\StageR12\startCD\Disk1\rapidwiz\template\adrunias.cmd
dest : C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunias.cmd
backup : C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunias.cmd to
C:\Oracle\VIS\apps\apps_st\appl\admin\
VIS_ap702app\out\templbac\adrunias.cmd
instantiate file:
source : C:\StageR12\startCD\Disk1\rapidwiz\template\adrunat.cmd
dest : C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd
backup : C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd to
C:\Oracle\VIS\apps\apps_st\appl\admin\
VIS_ap702app\out\templbac\adrunat.cmd
The log file then records that the execution of file “adrunat.cmd” has commenced:
Executing: C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd
The other two errors are associated with the execution of this file. They occur when the following line is processed:
adrunat.cmd" == "C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd" (if not ""runProcess_3"" == "FALSE" (goto :"runProcess_3" ) else (goto :runProcess_1 ) )
The installer is complaining because “runProcess_3” is delimited by two pairs of double quotes. Searching for occurrences of this syntax error within files under “C:\Oracle\VIS\inst” gives:
FILE: C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd
if not ""runProcess_3"" == "FALSE" (
FILE: C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunias.cmd
if not ""runProcess_3"" == "FALSE" (
If we look in the source file “C:\StageR12\startCD\Disk1\rapidwiz\template\adrunias.cmd” or “C:\StageR12\startCD\Disk1\rapidwiz\template\adrunat.cmd” we find the code block:
if "%s_masterscript%" == "%0" (
if not "%s_rerunprocess%" == "FALSE" (
goto :%s_rerunprocess%
) else (
goto :runProcess_1
)
)
but by the time these files have been instantiated the code block has become:
if "C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\adrunat.cmd" == "%0" (
if not ""runProcess_3"" == "FALSE" (
goto :"runProcess_3"
) else (
goto :runProcess_1
)
)
So the error occurred when the installer made the substitution for variable “%s_rerunprocess%”.
To understand how the installer made this error, we can look at the “restart” file, “C:\Oracle\VIS\inst\apps\VIS_ap702app\temp\restart.xml” which contains the instructions that drive the instantiation. In this file we find the entry:
<installprocess oa_var="s_rerunprocess">"runProcess_3"</installprocess>
Clearly, “"runProcess_3"” has an extra pair of quotes. As this value was not entered by the user when specifying the configuration, the error is clearly down to bug in the “Rapid Install” software.
To fix this bug we need to continue execution with the double quotes removed, either:
Remove the extra quotes from “restart.xml” entry above, press “Cancel” to exit the installer, and then rerun the installer with the “restart” option (rapidwiz.cmd -restart), or
Remove the extra quotes from the entries in files “adrunias.cmd” and “adrunat.cmd” and press “Retry”.
After applying a fix like this you can usually login to E-Business Suite and bring up forms (though you may well have to fix a “FRM-92101” error), which may be good enough if you’re only installing E-Business Suite for evaluation purposes. However, when an error occurs between the pre-install and post-install checks, then it’s almost always the case that the installation is incomplete, and some of the services will not have been created (see Figure 1).
Q: I can logon to Oracle Applications, but when I try to start a form I get “FRM-92101 Forms session <1> failed during startup”?
Ah! So near, and yet so far! You’ve been able to logon to E-Business Suite, only to find that when you bring up a form the window seems to hang, and finally displays:
Figure 4 - Forms Server Failure
The following fix may work (assuming a SID of VIS):
Look in directory “C:\Oracle\VIS\apps\tech_st\10.1.2\forms” and see if subdirectory “mesg” exists.
If not, then copy all the “.msb” files from “C:\Oracle\VIS\apps\tech_st\10.1.2\forms” to “C:\Oracle\VIS\apps\tech_st\10.1.2\forms\mesg”.
Restart the server.
If this fix works, and you’re only installing E-Business Suite for evaluation purposes then that’s fine. However, when this error occurs there are usually other issues with the installation, such as missing services, so if it’s for production you’ll need to correct the underlying fault if you’re going to have any confidence in the stability of the installation.
Q: I can logon to Oracle Applications, but when I try to start a form I get “FRM-92050 Failed to connect to Server on trying to open form” error?
This is a straight forward issue that occurs with the more recent versions of the Internet Explorer browser (not with IE6). By default, a cross-scripting filter is enabled in these browsers, and this prevents a forms window from being displayed.
The solution is to disable the filter as follows: select the “Tools” menu item, the “Internet Options” menu item; then on the “Security” tab, press the “Custom Level” button; scroll down to the “Scripting” group, and within that group find the “Enable XSS Filter” group; select the “Disable” radio button.
After exiting the pop-up hierarchy, try to open the form once again.
Q: Oracle Applications seems to be working okay but I get an ORA-12560 error when logging on to SQL*Plus?
Even though E-Business Suite may be up and running that doesn’t mean you will be able to access the database using SQL*Plus.
If you open up the SQL*Plus command window (press “Start”, and select, in turn, the menu items “All Programs”, “ORACLE - <SID>_db111_RDBMS”, “Application Development”, and “SQL Plus”), and try to logon to the database using account “system” and password “manager”. You’ll get a “TNS:protocol adapter error”.
Figure 5 - RDBMS Connection Failure
This problem occurs because the ORACLE_SID environment variable is not set during the installation processs. Open a command window and confirm that the environment variable is undefined (echo %ORACLE_SID%). Create the environment variable and set its value to that entered in the “Rapid Install Configuration Details” screen. Echo the variable to ensure that it is set correctly, and then try to logon to SQL*Plus as before.
Figure 6 - RDBMS Connection Succeeds
