Oracle E-Business Suite 12.2 Now Available

Finally long wait for Oracle E-Business Suite 12.2 is over. Now officially available from Oracle

Oracle E-Business Suite 12.2 Now Available

Cheers!!!

Getting Started as an E-Business Suite DBA

There is an excellent article from Mr. Lauren Cohn about getting started as an Apps DBA.

I think, the best answer to "How does one become an EBS DBA?" you can find best answer from the link

Getting started as an E-business suite DBA

Cheers!!!

Error While Loading Shared Libraries: libdb.so.2 on RedHat Linux 5

After clonning (or installing) an Oracle Applications Release 12.0 or 12.1 instance on Linux 5, an error may occur while starting up the Apache service. The error would be this: 

You are running adapcctl.sh version 120.6.12000000.4
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
adapcctl.sh: exiting with status 204


After review the HTTP log file. The error is very clear about the missing soft link. It would show this error:

/u01/apps/AJI_apps12/ora/10.1.3/Apache/Apache/bin/apachectl startssl: execing httpd
/u01/apps/tech_st/10.1.3/Apache/Apache/bin/httpd: error while loading shared
libraries: libdb.so.2: cannot open shared object file: No such file or directory

Soft link libdb.so.2 is missing.


To solve this issue, Shut down all Oracle Application Services

As root user, create a soft link as follows:
# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

Start up all Oracle Application Services

Cheers!!!

Glimpses of E-Business Suite 12.2: WebLogic Server and Online Patching

Finally 12.2 is on the way. Read more from Steven Chan blog
There are lots of updates coming in this release, but from a technology stack perspective, EBS 12.2 will be notable for two things:

1. Replacing Oracle Containers for Java (OC4J) 10g with WebLogic Server 11g
2. Online Patching support via 11gR2 Edition-Based Redefinition

Cheers!!!

Blank Page Accessing R12 - 'Missing class: _RF' in OACore application.log

On 12.0, trying to connect to the home page, which shows a blank page.

Further more, the application.log file of the OACore OC4J shows the following error stack:

javax.servlet.ServletException: oracle.classloader.util.AnnotatedClassNotFoundException:

Missing class: _RF

Dependent class: oracle.jsp.runtimev2.JspPageInfo
Loader: oc4j:10.1.3
Code-Source: /oracle/apps/tech_st/10.1.3/j2ee/home/lib/ojsp.jar
Configuration: code-source in META-INF/boot.xml in /oracle/apps/tech_st/10.1.3/j2ee/home/oc4j.jar

This load was initiated at oacore.web.html.jsp8892557:0.0.0 using the loadClass() method.

The missing class is not available from any code-source or loader in the system.
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:387) 
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:478) 
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:401) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64) 
at oracle.apps.jtf.base.session.ReleaseResFilter.doFilter(ReleaseResFilter.java:26) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15) 
at oracle.apps.fnd.security.AppsServletFilter.doFilter(AppsServletFilter.java:318) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:627) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:299) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:187) 
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260) 
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230) 
at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33) 
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831) 
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303) 
at java.lang.Thread.run(Thread.java:595)

To solve this issue, there are two ways
1. Set the JSP compilation to Automatic
2. Recompile the JSP manually

How to set the JSP compilation to Automatic
Use the vi editor to edit the $CONTEXT_NAME.xml context file used by AutoConfig and change the value for "s_jsp_main_mode" from "justrun" to "recompile" (without the double quotes)

Backup the context file before editing it.

Run Autoconfig to propagate the changes to the configuration files.

Verify that now the
$INST_TOP/ora/10.1.3/j2ee/oacore/application-deployments/oacore/html/orion-web.xml has

init-param
[param-name]main_mode[/param-name]
[param-value]recompile[/param-value]
/init-param

Restart the Middle Tier services and access the applications to load JSP's which will cause them to be recompiled on the run.

After successfully accessing the applications, use the vi editor to edit the $CONTEXT_NAME.xml context file used by AutoConfig and revert the value for "s_jsp_main_mode" to "justrun" (without the double quotes) in order not to hamper the performance of your system.

Run AutoConfig to propagate the changes.

How to recompile the JSP manually

You can always use the this option to compile JSP's manually at any time.
Connect application tier using applmgr user and source the environment by running the script:

/oracle/apps/apps_st/appl/APPSSID_host.env

Run the commands
UNIX 
cd $FND_TOP/patch/115/bin
perl ojspCompile.pl --compile --flush -p 2

Windows
cd %FND_TOP%\patch\115\bin
- perl -x ojspCompile.pl –compile –flush

Restart the Middle Tier services.


Cheers!!!

R12 - How to enable Apache, OC4J and OPMN logging

Whenever raise SR with Oracle support for R12 application logging related issue, they will ask you to produce the logging details by enabling the Apache, OC4J and OPMN components and its services. Compared to 11i, Oracle Applications R12 introduces new easy way in order to enable logging for any of the components that are being used within it. The details about how to enable logging of these component you can also follow as explained in this post.

Oracle Configuration Home for Apache, OC4J & OPMN is
$ORA_CONFIG_HOME/10.1.3

Apache server is still being used and its configuration path is as following:
$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf

but OC4J services, by default Oracle Applications R12 creates 3 OC4J instances:
1. OACore: runs OA Framework-based applications
2. Forms: runs Forms-base applications
3. OAFM (Oracle Apps Fusion Middleware): runs web services, mapviewer, ascontrol

Configuration files path for the above 3 OC4J instances is:
$ORA_CONFIG_HOME/10.1.3/j2ee/[oacore, forms, oafm]/config

Configuration file used to adjust log file path for the above 3 OC4J instances is:
$ORA_CONFIG_HOME/10.1.3/j2ee/[oacore, forms, oafm]/application-deployments/[oacore, forms, oafm]/orion-application.xml

Log files types:
Oracle Applications / E-Business Suite R12 can be configured to generate one of two types of logs files as following:

1. Plain text (default):
         - No log rotation available
         - Log files need to be manually removed
2. Oracle Diagnostics Logging (ODL) XML:
         - Logs rotation based on filesize, directory size
3. R12 logs by default are configured to generate plain text

Log files locations:
All log files are written in one home ( $LOG_HOME ) which is by default the (logs) directory under ($INST_TOP ).

Please note that after enbaling the logging for any of the following services you have to bounce the services in order the changes to take effect.

Steps to enable Apache logging:
Apache Logging ( Plain Text )

1) Edit the file $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf and set
LogLevel warn (s_apache_loglevel in context file)
2) Bounce the apache
3) Try to access the home URL or reproduce the issue.
4) Collect the following logfiles from $LOG_HOME/ora/10.1.3/Apache
  access_log.
  error_log.

Values that can be set to LogLevel variable in httpd.conf file
LogLevel = emerg,alert,crit,error,warn,notice,info,debug.

Apache Logging (ODL Logging)
1) Set the following parameters in file $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
OraLogMode [oracle|odl|apache]
OraLogSeverity [message type]:[message level]

Message type: INTERNAL_ERROR, ERROR, WARNING, NOTIFICATION & TRACE
Message level: 1-32 (1 most severe, 32 least)
2) Bounce the apache
3) Try to access the home URL or reproduce the issue.
4) Collect the logfiles from $LOG_HOME/ora/10.1.3/Apache/oracle

Steps to enable OC4J logging:

Log file path is specified in the file
$ORA_CONFIG_HOME/10.1.3/j2ee/[oacore, forms, oafm]/application-deployments/[oacore, forms, oafm]/orion-application.xml

1. Open the file to set the following log level $ORA_CONFIG_HOME/10.1.3/j2ee/[oacore, forms, oafm]/config/j2ee-logging.xml
2. Come to the location located as
logger name=’oracle’ level=’NOTIFICATION:1‘ …..
3. Set the desired logging using following values
message type:message level
Message type: INTERNAL_ERROR, ERROR, WARNING, NOTIFICATION & TRACE
Message level: 1-32 (1 most severe, 32 least)
4. Locate the log file path from the file
$ORA_CONFIG_HOME/10.1.3/j2ee/[oacore, forms, oafm]/application-deployments/[oacore,forms,oafm]/orion-application.xml
(Will be identified with tag : log file path=… /log)
5. Bounce the OC4J instance and reproduce the issue
6. Collect the log files from the following locations .

Plain text
$LOG_HOME/ora/10.1.3/j2ee/[oacore, forms, oafm]/[oacore,forms,oafm]_[default_group_1]/application.log

ODL Log
$LOG_HOME/ora/10.1.3/j2ee/[oacore, forms, oafm]/[oacore,forms,oafm]_[default_group_1]/log.xml

Steps to enable OPMN logging:
There are 3 log files generated:
          - (opmn.log): contains commands, exit status
          - (opmn.dbg): contains debug log messages
          - (opmn.out): contains stdout & stderr messages

1) Open the file $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml to set the logging parameter
2) Logging is enabled per component (internal, ons or pm)
3) Levels that can be set are (component codes) as following:
   none, fatal, error, warn, notify          (written to .log)
   debug1, debug2, debug3, debug4    (written to .dbg)
Ex :
  opmnctl set target=log comp=warn
  opmnctl set target=debug comp=debug1
4) Bounce opmn services and reproduce the issue
5) Collect the opmn log files generated in $LOG_HOME/ora/10.1.3/opmn
   opmn.log , opmn.dbg and opmn.out

NOTE : Logfiles can be enabled for rotation using parameter s_opmn_log_rotation_size, s_opmn_log_rotation_time in opmn.xml

Components (Services) Status & Logs:
1. You can check the status of the services/components by passing 'status' parameter to any AD script in $ADMIN_SCRIPTS_HOME.

adapcctl.sh status

2. The various logs written while starting and stopping the services are created in ($LOG_HOME/appl/admin/log/), the logs files are:

TNS Listener Start/Stop log                          - adalnctl.txt
Fulfillment Server Start/Stop log                    - jtffmctl.txt
Oracle HTTP Server start/stop log                 - adapcctl.txt
Concurrent Managers and ICM start/stop log - adcmctl.txt
Forms OC4J start/stop log                           - adformsctl.txt
OACore OC4J start/stop log                         - adoacorectl.txtq
OAFM OC4J start/stop log                           - adoafmctl.txt
OPMN start/stop log                                    - adopmnctl.txt

(adstpall.log) and (adstrtal.log) will record the messages while starting or stopping all services.
See also
how to enable and logging Apache, OC4J and OPMN
How to enable and logging Apache and Jserv in 11i

Cheers!!!

Cloning Oracle Applications Release 12 with Rapid Clone

Prerequisite Tasks

Before cloning, prepare the source system by applying any required patches and running AutoConfig.

1. Verify OS requirements on target system
   Before cloning to a new server, ensure the target system meets all the requirements for Oracle Applications Release 12 stated on the Oracle Applications Release Notes, and on the Oracle Applications Installation and Upgrade Notes for each Platform.
2. Apply the latest AD patch
   Apply patch 6510214 (R12.AD.A.DELTA.4) or higher.
3. Apply the latest AutoConfig template patch
   Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.
4. Apply the latest Rapid Clone patches
   Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches to all Applications nodes. For Release 12.0: 5484000 Oracle E-Business Suite 12.0.2 Release Update Pack (RUP2) or higher and 9171651:R12.OAM.A - 12.0 RAPIDCLONE CONSOLIDATED FIXES JUL/2010
   For Release 12.1: 9171651:R12.OAM.B -12.1 RAPIDCLONE CONSOLIDATED FIXES JUL/2010
   Other Patches (All releases): 8246709 - Required for Microsoft Windows if using OracleAS 10.1.3.4. This patch must be re-applied to the OracleAS 10.1.3.4 ORACLE_HOME before every cloning operation.
5. Run AutoConfig on the application tiers
6. Synchronize appsutil on the database tier nodes
7. Run AutoConfig on the database tier
8. Maintain snapshot information

Log in to each application tier node as the APPLMGR user, and run "Maintain Snapshot information" in AD Administration.  

Cloning Tasks

1. Prepare the source system
   Execute the following commands to prepare the source system for cloning:
1. Prepare the source system database tier for cloning
   Log on to the source system as the ORACLE user, and run the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier

2. Prepare the source system application tier for cloning
   Log on to the source system as the APPLMGR user, and run the following commands on each node that contains an APPL_TOP:

$ cd [INST_TOP]/admin/scripts
$ perl adpreclone.pl appsTier

2. Copy the source system to the target system
   Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed. Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database node files are owned by the target ORACLE user.For example: cd /target_dest_dir/db cp -RH /source_dir/db/*. Alternatively, the tar command can be used to compress the directories into a temporary staging area. 

1. Copy the application tier file system
   Log on to the source system application tier nodes as the APPLMGR user and shut down the application tier server processes. Copy the following application tier directories from the source node to the target application tier node:
• [APPL_TOP]
• [COMMON_TOP]
• Applications Technology Stack:
• [OracleAS Tools ORACLE_HOME]
• [OracleAS Web IAS_ORACLE_HOME]
2. Copy the database node file system
   Log on to the source system database node as the ORACLE user, and then:

1.     Perform a normal shutdown of the source system database

2.     Copy the database (.dbf) files from the source system to the target system

3.     Copy the source database ORACLE_HOME to the target system

4.     Start the source Applications system database and application tier processes

Configure the target system

Run the following commands to configure the target system. You will be prompted for specific target system values such as SID, paths, and ports.

Configure the target system database server
Log on to the target system as the ORACLE user and enter the following commands:

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and enter the following commands:

$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier

Finishing Tasks

This section lists tasks that may be necessary, depending on your implementation and the intended use of the cloned system.

1. Update profile options
   Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually.
2. Update printer settings
   If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
3. Update Workflow configuration settings
   Cloning an Oracle Applications instance will not update the host and instance-specific information used by Oracle Workflow. Review the tables and columns listed below to check for any instance-specific data in the Workflow configuration on the target system.

Workflow configuration settings

Table Name	Column Name	Column Value Details
WF_NOTIFICATION_ATTRIBUTES	TEXT_VALUE	Value starts with http://[old web host]: Update to new web host.
WF_ITEM_ATTRIBUTE_VALUES	TEXT_VALUE	Value starts with "http://[old web host]: Update to new web host.
WF_SYSTEMS	GUID	Using the Workflow Administrator Web Applications responsibility, create a new system defined as the new global database name.
WF_SYSTEMS	NAME	Replace value with the database global name.
WF_AGENTS	ADDRESS	Update database link with the new database global name.
FND_FORM_FUNCTIONS	WEB_HOST_NAME	Update with the new web host name.
FND_FORM_FUNCTIONS	WEB_AGENT_NAME	Update to point at the new PL/SQL listener name.
FND_CONCURRENT_REQUESTS	LOGFILE_NAME	Update with the correct path to the logfile directory.
FND_CONCURRENT_REQUESTS	OUTFILE_NAME	Update with the new directory path on the target system.

4. Verify the APPLCSF variable setting
   Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to a suitable directory. To modify it, change the value of the s_applcsf variable in the context file and then run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
   If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name.
6. Re-Implement SSL and SSO configuration
   If the Source System was SSL or SSO enabled, reconfigure the Target by following the SSL/SSO documentation.

Advanced Cloning Options

Refreshing a Target System

You may need to refresh the target system periodically to synchronize it with changes to the source system.

1. Prepare the source system.
2. Copy the source system to the target system.
• If the application tier file system if the APPL_TOP, COMMON_TOP, or technology stack needs to be refreshed, copy the portion of the application tier file system that has been updated
• If the RDBMS ORACLE_HOME or the database needs to be refreshed, copy the database node file system. If refreshing the database, the ORACLE_HOME should be refreshed at the same time.
3. Configure the target system.
   Specify the existing target system context file when running adcfgclone.pl commands.
1. Configure the target system database server by logging on to the target system as the ORACLE user and entering the following commands to configure and start the database:

$cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
perl adcfgclone.pl dbTier [Database target context file]

Where Database target context file is [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml

2. Configure the target system application tier server nodes by logging on to the target system as the APPLMGR user and entering the following commands:

$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier [APPL_TOP target context file]

Where APPL_TOP target context file is [INST_TOP]/appl/admin/[Target CONTEXT_NAME].xml

4. Perform the standard finishing tasks mentioned above.

Cloning a Multi-Node System

This procedure allows the source system or target system to be a multi-node system. As of Release 12, all APPL_TOPs are unified APPL_TOPs. This means that all files required for all application tier services are installed on every application tier node. Thus, only one copy of the applications tier node files needs to be copied to the target system, regardless of whether a shared file system is being used on the source or target system. Multiple application tier nodes are distinguished from each other by the services running.

1. Perform the standard prerequisite tasks.
   Carry out these steps on all source and target nodes.
2. Carry out the cloning tasks mentioned above
   Prepare, copy and configure the cloned Applications system. When creating more than one application tier node on the target system, follow these steps:
• Perform a full clone (Prepare, copy and configure steps) of the database node and primary application tier node.
• To add shared application tier nodes on the target system, follow the instructions in My Oracle Support Knowledge Document 384248.1, Section 4: Adding a node to a Shared Application Tier File System.
• To add non-shared application tier nodes, execute the copy and configure steps as on the primary node.
• Specify the services to start on each target Applications tier node when responding to the prompts during the configuration step.
3. Perform the required finishing tasks mentioned above.

Adding a New Node to an Existing System

You can use Rapid Clone to clone a node and add it to the existing Applications system, a process also known as scale up or scale out. The new node can run the same services as the source node, or different services. Follow the instructions in the Application tier part of Cloning Tasks.

1. Prepare the source system, copy it to the new node and configure it.
2. After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:

$ cd [COMMON_TOP]/clone/bin
$ perl adaddnode.pl

Note: After adding new nodes, do the set up for load balancing.

Cloning the Database Separately

Some situations require the database to be recreated separately, without using Rapid Clone. Typical scenarios are when system downtime is not feasible, or advanced database replication tools like RMAN are being used to copy the database in hot backup mode.

1. Log on to the target system as the ORACLE user
2. Configure the [RDBMS ORACLE_HOME]

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbTechStack

3. Create the target database control files manually
   In this step, you copy and recreate the database using your preferred method, such as RMAN restore, Flash Copy, Snap View, or Mirror View.
4. Start the target database in open mode
5. Run the library update script against the database

$ cd [RDBMS ORACLE_HOME]/appsutil/install/[CONTEXT NAME]
$ sqlplus "/ as sysdba" @adupdlib.sql [libext]

Where [libext] should be set to 'sl' for HP-UX, 'so' for any other UNIX platform, or 'dll' for Windows.

6. Configure the target database
    The database must be running and open before performing this step.

$ cd [RDBMS ORACLE_HOME]/appsutil/clone/bin
$ perl adcfgclone.pl dbconfig [Database target context file]

Where Database target context file is: [RDBMS ORACLE_HOME]/appsutil/[Target CONTEXT_NAME].xml.

Note: The dbconfig option will configure the database with the required settings for the new target, but it will not recreate the control files.

Cheers!!!

Configuring maintenance mode for R12.

Compared to 11i, enable/disable maintenance mode in R12 has some additional steps. The following set of instructions have to perform for configuring maintenance mode in R12 perfectly.

1. Schedule a downtime using OAM
2. Shutdown all the application processes
3. Run adadmin and switch the system to maintenance mode
4. Run the script:
txkrun.pl -script=ChangeApacheMode -contextfile=[Path to the ContextFile] -mode=Restrict
5. Start Oracle HTTP Server and oacore OC4J should you need to monitor the system . From now on, all access to e-biz will be redirected to the downtime page.

Once the maintenance is complete, switch the system back to normal mode

1. Run the script:
txkrun.pl -script=ChangeApacheMode -contextfile=[Path to the ContextFile] -mode=Normal
2. Run adadmin and switch the system to normal mode.
3. Restart oacore oc4j and start all other processes.

You may also refer to Article ID 291901.1


Cheers!!!

How to remove an Oracle E-Business Suite Release 12.x Windows Environment

There are many potential reasons for wishing to remove an environment, including an installation failure. Such a failure may result from improper install user privileges, missing prerequisite software, inadequate system resources, or other causes, if your installation does fail, you must clean your system before you attempt to re-install Oracle Applications.

For a multi-node installation, repeat the procedure for each node on your system. The procedure requires you to use the Registry Editor to alter the Windows registry, and to delete the faulty instances from your system. You should read and understand all steps described here before you begin.

Step 1. Back up the System

Back up your system and the Windows registry before you begin. 

Step 2. Alter the Windows Registry

Delete the relevant Oracle components from the Windows registry, as follows.

To delete a specific instance (in the case that there are multiple EBS instances or other Oracle software on the system):

1. Launch the Registry Editor.
2. Navigate to the HKEY_LOCAL_MACHINE\Software\ORACLE\APPLICATIONS\12.0.0 key.
3. Delete the entry corresponding to the instance to be deleted.
4. Navigate to the HKEY_LOCAL_MACHINE\System\Current Control Set\Services.
5. Carefully select and delete each Oracle service corresponding to the instance you wish to delete.  For example, if you wish to delete "PROD", delete "OraclePROD__ToolsASControl".
6. When you are finished, exit the Registry Editor. 

To delete all Oracle environments on the system:

1. Launch the Registry Editor.
2. Navigate to the HKEY_LOCAL_MACHINE\Software key.
3. Select the Apache Group subkey and delete it.
4. Select the Oracle subkey and delete it.
5. Navigate to the HKEY_LOCAL_MACHINE\System\Current Control Set\Services.
6. Carefully select and delete each service beginning with Oracle.  For example, delete "OraclePROD__ToolsASControl".
7. When you are finished, exit the Registry Editor. 

Step 3. Alter Environment Settings

Complete these steps to delete Oracle parameters from the environment.

Navigate to the Environment Variables editing screen according to your system setup.  For example, right-click My Computer and select Properties. From the Advanced tab, click the Environment Variables button.

To delete a specific instance (in the case that there are multiple EBS instances, or there is other Oracle software on the system):

1. Select the following system variable if created during the failed installation, and modify it to point to the environment(s) you would like to keep: PERL5LIB.
2. Select the Path variable, but do not delete it.  Carefully edit it and remove any component that references the failed install. For example, delete "e:\oracle\PROD\db\tech_st\10.2.0\bin;".
3. Save and exit System Properties.

Alternatively, to remove all Oracle environments from the system:

1. Select the following system variable if created during the failed installation, and delete it: PERL5LIB.
2. Select the Path variable, but do not delete it.  Carefully edit it and remove any component with "Oracle" in the name, or that otherwise references the failed install. For example, delete "e:\oracle\PROD\db\tech_st\10.2.0\bin;".
3. Save and exit System Properties.

Step 4. Clean up the Program Menu

Launch the Program menu (Start->Programs). Carefully delete all Oracle programs associated with the instance or instances to be removed. Select each one, right-click it, and choose the Delete option.

Step 5. Restart your Machine

Restart your machine.  This removes all Windows services that you deleted from the registry and frees up the files accessed by the associated processes so that they may also be deleted (see next step).

Step 6. Delete the Oracle Filesystem

It is now safe to remove the Oracle filesystem that was partially installed during the failed installation. Go to the base install directory, or top-level directory under which you installed the Database Server (DB) or the Applications Tier Server (APPS) directories, or both.
Note that you may choose to rename a directory before you delete it. This allows you to use the same directory name and start a new installation even before you finish the delete filesystem operation. For example, if you placed your filesystem in a "test" directory under "E:\oracle":

C:\>  E:
E:\>  cd oracle
E:\>  rename test oldtest
E:\>  del /s /q oldtest

Step 7. Delete Programs and Oracle Inventory Entries

To delete the inventory associated with a specific instance:

1. Start the Oracle Universal Installer using: Start >> All Programs >> Oracle-_db102_RDBMS>>Oracle Installation Products>>Universal Installer
2. Select Installed Products
3. Enable "Show empty homes"
4. Deinstall the entries in the global inventory associated with the Oracle Applications R12 instance which you removed earlier. For example, for the PROD instance, you would delete:
1. RDBMS ORACLE HOME (e.g. "PROD_DB__oracle_PROD_db_tech_st_10_2_0")
2. 10gAS ORACLE HOME (e.g."PROD_WEBOH__oracle_PROD_apps_tech_st_10_1_3")
3. Developer 10g ORACLE HOME (for example, "PROD_TOOLS__oracle_PROD_apps_tech_st_10_1_2")
5. Exit the Universal Installer

To delete the files associated with all Oracle environments on the system:

1. Open a command window and navigate to the C:\Program Files\ directory.
2. Delete the Oracle subdirectory.
3. If your Oracle Inventory directory was not C:\Program Files\Oracle\Inventory and was therefore not deleted in the previous step, locate it and delete it.

Cheers!!!