Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Microsoft Windows x64

Part Number E14774-11
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

2 Installation and Configuration

This chapter describes issues associated with Oracle Fusion Middleware installation and configuration. It includes the following topics:

2.1 Installation Issues and Workarounds

This section describes installation issue and workarounds. It includes the following topics:

2.1.1 Installing Oracle Portal, Forms, Reports and Discoverer on Windows with IPv6

If you are installing Oracle Portal, Forms, Reports and Discoverer on a Windows operating system that supports IPv6 (for example, Windows Vista or Windows 7), the components in the installation will not start if IPv6 is enabled.

Make sure that IPv6 is disabled on your Windows operating system before you install these components.

2.1.2 Prerequisite Warnings During Installation

Vendor release updates cummulative patches and/or packages that may superseed our listed Oracle Fusion Middleware 11g Release 1 prerequisites for platforms. As long as vendor approved patches and/or packages are installed, the prerequisite warnings could be ignored and the installation completed.

Another option is to use -ignoreSysPreReqs command line additional argument to the runInstaller as:

$  Mount_Point/runInstaller -ignoreSysPreReqs other required install options

2.1.3 "Null" Dialog Box Appears When Installing Oracle Identity Management to FAT32 File System on Windows

If you install the Oracle Home directory to a File Allocation Table 32 (FAT32) file system during Oracle Identity Management installation, a pop-up dialog box containing the following text appears on the Specify Installation Location screen:




The following is the dialog box text that is hidden by the erroneous "null null null" message:

The Windows FAT file system allows any user to create, modify and delete all files 
on the file system. Oracle recommends use of NTFS on windows operating systems 
because it preserves permission restrictions on files. Do you want to Continue?

To work around this issue, click Yes on the dialog box to continue the installation, or click No to cancel the installation.

2.1.4 Missing Shortcuts in the Oracle Portal, Forms, Reports and Discoverer Installation

During the Installation of Oracle Portal, Forms, Reports and Discoverer, if you choose to extend your domain or expand a cluster and specify a domain name other than the default "ClassicDomain," you will see a "Missing Shortcut" error when you try to start and stop the managed servers.

The work around for this issue is as follows:

  1. From the Start menu, right-click on the shortcut that generated the error message.

  2. In the shortcut tab, go to the target node.

  3. Change the domain name to the correct domain name.

  4. Click Apply.

2.1.5 JRF Startup Class Exceptions May Appear in Oracle WebLogic Managed Server Logs After Extending Oracle Identity Management Domain

After extending an Oracle Identity Management domain, you may see exception messages related to JRF Startup Class in the managed server log files. For example:

Failed to invoke startup class "JRF Startup Class",
oracle.jrf.PortabilityLayerException: Fail to retrieve the property for the Common
Components Home.
oracle.jrf.PortabilityLayerException: Fail to retrieve the property for the Common
Components Home.

You can safely ignore these exception messages—there is no loss in functionality.

2.1.6 WebLogic Administration Server Must Be Running When Extending Oracle Identity Management Domains

When you install Oracle Identity Management, you have several options for choosing how the Oracle Identity Management components are installed in relation to an Oracle WebLogic Server administration domain. If you select the Extend Existing Domain option on the installer's Select Domain screen, Oracle Identity Management components are installed in an existing Oracle WebLogic Server administration domain.

To install Oracle Identity Management components in an existing administration domain using the Extend Existing Domain option, the Oracle WebLogic Administration Server instance must be running.

2.1.7 Oracle Identity Management Must Be Installed on the C:\ Drive

If you are performing a fresh installation of Oracle Identity Management 11gR1 (Release or 11gR1 PS1 (Release, you must install the software on the C:\ drive. If you try to install the software on a different drive, the installation will fail.

2.1.8 Problems Installing in Thai and Turkish Locales

Turkish and Thai users are recommended to install and run Oracle Fusion Middleware using the English locale. Oracle Fusion Middleware does support Turkish and Thai locales as clients.

2.1.9 Installing Oracle UCM in Stand-Alone Mode

The Oracle WebCenter installation gives you the option of installing Oracle Universal Content Management (UCM). If you choose not to install Oracle UCM during the Oracle WebCenter installation, you can install Oracle UCM separately in stand-alone mode. Installation instructions are available at the following location:

These installation instructions are missing some important information, which is covered below. The following topics are covered: Do Not Include Folders_g in the Installation

The last question is during the installation procedure is:

Select components to install.
         1. ContentFolios: Collect related items in folios
         2. Folders_g: Organize content into hierarchical folders
         3. LinkManager8: Hypertext link management support
         4. OracleTextSearch: External Oracle 11g database as
            search indexer support
         5. ThreadedDiscussions: Threaded discussion management
Enter numbers separated by commas to toggle, 0 to unselect all, F to finish:

Make sure you DO NOT include number 2 (Folders_g) for this answer; you should not install Folders_g using the installation script. Folders_g will be installed when the script is run. Disable Trash in the Installation

Instead of installing an new Content Server to use with Oracle WebCenter, you have the option of using an existing Content Server. Any existing Content Server used with Oracle WebCenter should have the Trash disabled. Trash will only be in the Content Server if you have installed a foldering component.

To see if Trash is enabled in the Content Server:

  1. Go to Administration.

  2. Go to Folder Configuration.

  3. Go to System Folder Configuration.

    The colour of the dot next to the Trash folder indicates whether or not the Trash is enabled:

    • Green = enabled

    • Gray = disabled

To disable the Trash:

  1. Ensure you can edit marked folders:

    1. Open the stellent_dir/custom/Folders_g/folders_environment.cfg (on UNIX) or stellent_dir\custom\Folders_g\folders_environment.cfg (on Windows) file.

    2. Verify that the CollectionReadOnlyMarkedFolders value is set to true:

  2. Restart the Content Server if you changed the folders_environment.cfg file.

  3. Log in to the Content Server Home Page as a user with Administrator privileges.

  4. Go to Administration.

  5. Go to Folder Configuration.

  6. Go to System Folder Configuration.

  7. Click on the green dot next to Trash. This will disable the Trash folder and will turn the dot grey.

  8. Restore the value of CollectionReadOnlyMarkedFolders if you had changed it and restart the Content Server.

2.1.10 Installer Hangs When No Browser Location is Provided for the Oracle WebCenter Installation

On Portugese, German, Italian, and Spanish Windows systems, when you install Oracle WebCenter and choose to also install Oracle UCM, a window will appear asking you to provide a browser location. If you do not provide a browser location on this screen and click Close, the installer will hang.

The work around is to make sure you specify a valid browser location.

2.1.11 Oracle Web Tier Silent Install Requires Oracle Web Cache Component Name

If you are performing a silent Oracle Web Tier installation for Oracle HTTP Server, an Oracle Web Cache component name (WEBCACHE_COMPONENT_NAME parameter) must also be mentioned in the response file, even though Oracle Web Cache is not required for Oracle HTTP Server installation. Even though both component names are provided, as long as CONFIGURE_WEBCACHE is set to false then only Oracle HTTP Server will be installed and configured.

There is no work around for this issue.

2.1.12 Problems with the Oracle Home Directory Being Overwritten on Windows

If you are installing Oracle Fusion Middleware on a Windows system, and that system already contains your Oracle Database, then you may encounter issues where the ORACLE_HOME global environment variable used by the database is overwritten by the Oracle Fusion Middleware product installation.

To view the global environment variable, select System Properties > Advanced > Environment variables > System Variables and check the value of ORACLE_HOME. From here, you can set the value of ORACLE_HOME to the location of the desired product.

2.1.13 Enterprise Manager Fails with Timezone Error Message

There is a problem with the timezone detection algorithm on some versions of Windows. When the database is installed on some systems that have a fresh installation of Windows, the configuration of Enterprise Manager fails with a message that indicates that an "America/Rio_Branco" timezone has been detected.

The work around is to reset the timezone to the desired value, then re-install your Oracle Fusion Middleware product.

2.1.14 Setting the nls_length_semantics Parameter in your Database

Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics initialization parameter on the database where the schemas reside must be set to BYTE; setting this parameter to CHAR is not supported.

To check the values of this parameter using SQL*Plus, you can use the show parameters command:

prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics

Replace password with the actual password for the SYS user.

Alternatively, you can check the values by querying the V$PARAMETER view:

prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;

2.1.15 Proper Deinstallation for Reinstallation in the Event of a Failed Installation

In the event that an installation fails, and you want to deinstall the failed installation and then reinstall the software to the same location, you must do the following:

  1. Make sure that all the managed servers in the failed installation are shut down. You must verify this in the Administration Console; the word "SHUTDOWN" must appear next to the managed server name.

  2. Deinstall the binaries in the Oracle Home directory using the deinstaller in the ORACLE_HOME\oui\bin directory.

  3. Delete all the managed servers from the failed installation in the config.xml file by using the Administration Console or WLST.

  4. Delete all directories in the DOMAIN_HOME\servers directory:

This procedure will enable you to reinstall the software to the same location, using the same managed server names.

2.1.16 Verify PATH Before Starting Classic Installation on Microsoft Windows x64

Before starting Classic Application Server installation, any reference to Program Files (x86) must be removed from the PATH environment variable. On echoing PATH on the command prompt, Program Files (x86) should not be present.

2.1.17 Running or irca.bat Against an Oracle 10g Database

If you run the Integration Repository Creation Assistance Tool ( on UNIX operating systems or irca.bat on Windows operating systems) against an Oracle 10g database, you will get a java.lang.UnsupportedClassVersionError error.

This is because the Oracle 10g database contains JDK version 1.4, while the Java files in this release are compiled with a higher version of Java.

The work around is to set the JAVA_HOME environment variable to the WebLogic JDK.

2.1.18 Installing the SOAINFRA Schema with DBA Permissions

If you need to install the SOAINFRA schema and you are using a user with only DBA permissions, run the following commands on your database prior to running RCU:


Replace user in the command with the name of your database user.

2.1.19 Deinstallation Does Not Remove WebLogic Domains

There may be certain scenarios where you will need to remove WebLogic Domains that you have created. The Oracle Universal Installer is used to remove Oracle Instances and Oracle Home directories only; it does not remove WebLogic Domains.

If you need to remove a WebLogic Domain, you must do so manually. Please refer to your Oracle WebLogic Server documentation for more information.

2.1.20 Failures in the Installation Log File

Upon completing of an Oracle Web Tier, Oracle Identity Management, or Oracle Portal, Forms, Reports and Discoverer installation, the following errors may be seen in the installtime_and_date.log file:

[2009-11-04T21:15:13.959-06:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 16]
[ecid: 0000IJ2LeAeFs1ALJa5Eif1Aw^9l000007,0] OUI-10080:The pre-requisite for
the component Sun JDK  has failed.
[2009-11-04T21:15:13.960-06:00] [OUI] [NOTIFICATION] [] [OUI] [tid: 16]
[ecid: 0000IJ2LeAeFs1ALJa5Eif1Aw^9l000007,0] OUI-10080:The pre-requisite for
the component Oracle Configuration Manager  has failed.   

These messages occur because the Sun JDK and Oracle Configuration Manager are not installed in the oracle_common directory. You can safely ignore these messages.

2.1.21 Response File is Missing the MIDDLEWARE_HOME Entry

When installing Oracle Web Tier, the sample response files that are provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directories are missing an entry for specifying the Middleware Home directory.

If you plan on using these response files for silent installation, you must add the MIDDLEWARE_HOME entry to the file. For example:


2.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

2.2.1 Installing Oracle SOA Suite and Oracle Portal, Forms, Reports and Discoverer in the Same Middleware Home

Oracle Portal, Forms, Reports and Discoverer should be installed in its own Middleware home, which it can not share with any other Fusion Middleware products. All other Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter Webcenter, or Oracle Identity Management, can share a Middleware Home.

2.2.2 Extend Domain and Expand Cluster Scenarios with Remote Machines

In scenarios where you are using the Fusion Middleware Configuration Wizard to extend a domain or expand a cluster with remote machines, you must make sure that both the source and destination Middleware Home and Oracle Home directories are identical.

2.2.3 Specify Security Updates Screen Does Not Appear in the Configuration Wizard

If you use silent installation (response file) to configure Oracle Identity Management, security updates (through Oracle Configuration Manager) are not configured. However, the ocm.rsp file is created in the Oracle Home directory. If you run the Configuration Wizard GUI from the Oracle Home, you will not see the Specify Security Updates Screen because of the presence of the ocm.rsp file.

To work around this issue, delete the ocm.rsp file from the Oracle Home and run the Configuration Wizard to see the Specify Security Updates screen.

2.2.4 Unsupported Database Appears in the Configuration Wizard

When running the Configuration Wizard after an Oracle SOA Suite, Oracle WebCenter, or Oracle Application Developer installation, the "Configure JDBC Component Schema Screen" lists IBM DB2 as one of the options in the drop-down list of the "Vendor" field.

IBM DB2 is not yet supported and should not be selected on this screen.

2.2.5 FileNotFoundException When Cloning on Windows

When you run the applyClone command on Windows operating systems, a is thrown to the console.

This exception can be safely ignored and the applyClone operation will be successfully completed.

2.2.6 Configuring Oracle Identity Management When WebLogic Node Manager is Running

To configure Oracle Identity Management, using either the Install and Configure option or the Configuration Wizard, when the WebLogic Node Manager utility is running from the same Middleware Home directory where Oracle Identity Management is installed, the StartScriptEnabled parameter in the file must be set to true. For example: StartScriptEnabled=true

To configure Oracle Identity Management when the StartScriptEnabled parameter is set to false, you must:

  1. Set the StartScriptEnabled parameter to true.

  2. Stop, then restart the Node Manager utility.

  3. Configure Oracle Identity Management using either the Install and Configure option or the Configuration Wizard.


The file is located in the WL_HOME/common/nodemanager/ directory.

2.2.7 Configuring OID with Oracle Data Vault

If you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:

  1. Apply patch 8897382 (see the README file in the patch for instructions).

  2. In the ORACLE_HOME/ldap/datasecurity/dbv_oid_command_rules.sql (on UNIX operating systems) or ORACLE_HOME\ldap\datasecurity\dbv_oid_command_rules.sql (on Windows operating systems) file, find the following code:

       command => 'CONNECT'
       ,rule_set_name => 'OID App Access'
       ,object_owner => 'ODS'
       ,object_name => '%'
       ,enabled => 'Y');
  3. Change the following line:

    ,object_owner => 'ODS'


    ,object_owner => '%'

2.2.8 OIDMON Does Not Start After Configuring Oracle Internet Directory on Windows

On Windows platforms, when configuring Oracle Internet Directory using either the installer's Install and Configure option or the Configuration Wizard, OIDMON will not start if the total length of all environment variables, such as ORACLE_HOME, JAVA_HOME, PATH, and so on, exceeds 4,000 characters.

If you see an oidmon.exe application error message while configuring Oracle Internet Directory, or if the installer's log files indicate that OIDMON could not start, you may have encountered this issue.

To work around this issue, reduce the length of environment variables so that the total length of all variables is less than 4,000 characters and then attempt to configure Oracle Internet Directory again.

2.2.9 Password Requirements for Oracle Internet Directory Administrator

When configuring Oracle Internet Directory, using either the installer's Install and Configure option or the Configuration Wizard, you must enter and confirm the Administrator Password.

The following is a list of the requirements for the Oracle Internet Directory Administrator Password. The password must contain:

  • At least 5 characters

  • No more than 30 characters

  • At least one number

  • Only alpha-numeric characters, underscore ( _ ), dollar sign ( $ ), and pound/hash ( # )


If the password you enter does not satisfy these requirements, the following error message appears:
INST-07037: Administrator Password field value contains one or more
invalid characters or the value is not in proper format.

2.2.10 Setting the PATH Environment Variable for OCM

In order for OCM configuration to work properly on Windows operating systems, make sure the PATH environment variable is set to C:\windows\system32.

2.2.11 Changing the Listen Address of a Managed Server

When you run the Configuration Wizard after installing Oracle Identity Management or Oracle Portal, Forms, Reports and Discoverer, the listen address for WebLogic managed servers is left blank by default (to listen to all network interfaces). If you change the listen address to the actual host name, the managed server stops listening from outside the machine.

It is recommended that you either leave the listen address blank, or specify the IP address of the host rather than using the host name.

2.2.12 Expand Cluster Requires Changes to the File

After running the Oracle Fusion Middleware Configuration Wizard to expand a cluster, the EMD_URL parameter in the INSTANCE_HOME/EMAGENT/EMAGENT/sysman/config/ (on UNIX) or INSTANCE_HOME\EMAGENT\EMAGENT\sysman\config\ (on Windows) file contains the values shown below:


You must edit this parameter and replace localhost and localdomain with the actual host and domain information of your environment. For example, using 5160 as the port number:


2.2.13 Domain Extension Overwrites JDBC Data Source Name

When a WebLogic Domain with JDBC resources is extended to either Oracle SOA Suite or Oracle WebCenter, the JDBC data source name will be changed. This behavior is commonly observed in cases where WebLogic Server version lower than 9.x is upgraded to a version higher than 9.x and then extended to Oracle SOA Suite or Oracle WebCenter.

To work around this issue, you must manually edit the JDBC data source names.

2.2.14 Schemas Are Not Visible After Upgrade of Oracle Identity Management

After upgrading Oracle Identity Management from Release 10g ( to 11g Release 1 (11.1.1), the Oracle Directory Service schemas (ODS and ODSSM) are not visible in the Repository Creation Utility (RCU).

The reason for this is because RCU is not used during the upgrade process, and RCU only recognizes schemas that are created by RCU. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information.

2.2.15 RCU Summary Screen Issues

If you are dropping the Identity Management schemas and you select both Oracle Internet Directory (ODS) and Oracle Identity Federation (OIF) to be dropped, the RCU summary screen may not be displayed and an exception may be thrown in the console.

To work around this issue, select and drop one component at a time instead of selecting them both and dropping them together.

When other components are selected for a drop schema operation, the summary screen may display inaccurate information. However, the selected schemas will be successfully dropped from the database in spite of the erroneous information on the summary screen.

To work around this issue, select and drop only one component at a time.

2.2.16 Error Message When Configuring Oracle Identity Federation

During the configuration of Oracle Identity Federation (OIF), the following error message regarding key store and password may be seen in the configuration log file:

[app:OIF module:/fed path:/fed spec-version:2.5
version:]: Failed while destroying servlet: usermanager.
java.lang.RuntimeException: The server could not initialize properly: Invalid/unsupported
key store or incorrect password. Please verify that the password is correct
and the store is a valid PKCS#12 PFX wallet or Java KeyStore file.

This error message can be safely ignored if OIF is running properly.

2.2.17 Ensure There Are No Missing Products When Using or unpack.cmd

Oracle SOA Suite, Oracle WebCenter, and Application Developer all contain the and (on UNIX systems) or pack.cmd and unpack.cmd (on Window systems) commands in their respective ORACLE_HOME/common/bin (on UNIX systems) or ORACLE_HOME\common\bin (on Windows systems) directories.

The and pack.cmd scripts are used to create a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. The and unpack.cmd scripts are used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine.

The and unpack.cmd commands will fail if any installed products are missing from the machine where you are running the or unpack.cmd command.

2.2.18 Running or unpack.cmd on a Different Host

If you are running the (on UNIX) or unpack.cmd (on Windows) command to unpack a domain on a remote host, the Oracle Home location and the Middleware Home location on the remote host should match the locations on the host where the pack was performed.

Below is a valid example:

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

The example below is NOT valid because the Oracle Homes do not match:

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\SOA_Home

The example below is NOT valid because the Middleware Homes do not match:

Host 1:
MW_HOME = C:\Oracle\Middleware
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

@ Host 2:
MW_HOME = C:\Oracle\MWHome
ORACLE_HOME = C:\Oracle\Middleware\Oracle_SOA1

2.2.19 Rerouting to Original URL After SSO Authentication in Firefox Browser

When configuring Oracle Portal, Forms, Reports and Discoverer, when both Oracle HTTP Server and Oracle Web Cache are selected for configuration, re-routing (back to the original URL) after Single Sign-On (SSO) authentication does not work in Firefox Browser when the initial request comes from Oracle HTTP Server.

The work arounds are to either use the Internet Explorer browser, or manually modify the INSTANCE_HOME\config\OHS\instance_name\httpd.conf file and change the ServerName entry to include the port number. For example:


should be changed to:


Replace port with the actual port number.

2.3 Known Issues

This section describes known issues. It includes the following topics:

2.3.1 Forms and Reports Builder Not Supported

Forms and Reports Builder is not suported on Linux x86-64, Solaris Operating System (SPARC 64-Bit), AIX Based Systems (64-Bit), HP-UX PA-RISC (64-Bit), HP-UX Itanium, and Microsoft Windows x64 platforms. It is supported on Linux x86 and Microsoft Windows (32-Bit) platforms only.

2.4 Documentation Errata

This section describes documentation errata. It includes the following topics:

2.4.1 Oracle Portal, Forms, Reports and Discoverer Installation Guide: Missing Step for Restarting Node Manager

Section 2.7 ,"Installing in a Middleware Home Where Oracle SOA Suite or Oracle Identity Management Already Exist" in the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer is missing a third step. The complete instructions should be as follows:

If you are installing Oracle Portal, Forms, Reports and Discoverer into a Midldeware Home directory that already contains an Oracle SOA Suite or Oracle Identity Management installation, you must do the following before you install:

  1. Navigate to the MW_HOME/wlserver_10.3/common/nodemanager (on UNIX operating systems) or MW_HOME\wlserver_10.3\common\nodemanager (on Windows operating systems) directory.

  2. Edit the file and set the StartScriptEnabled property as follows:

  3. Restart Node Manager.

2.4.2 Oracle Portal, Forms, Reports and Discoverer Installation Guide: Missing Information in the Deinstallation Chapter

In the deinstallation chapter for the Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer, Step 4 in Section 3.2.1, "Stopping Oracle Fusion Middleware" is missing a piece of information.

While the documentation instructs you to stop the Administration Server, it should be noted that the Administration Server must remain up and running if you are planning to deinstall managed instances.

2.4.3 Missing Information for Deinstalling Oracle Homes

When you run the deinstaller and you choose to remove an Oracle Home, the documentation is missing some information between the Deinstall Oracle Home and Deinstallation Progress screens.

On the Deinstall Oracle Home screen, you will see and be asked to verify the Oracle Home that is about to be deinstalled. When you click Deinstall, a warning dialog box will appear with the following options:

Click on "Yes" to continue.

Click on "No" to perform deinstall without deleting the directory.

Click on "Cancel" to go back to the "Inventory Dialog".

If you select "Yes" the Oracle Home directory will be removed at the end of the deinstallation procedure.

If you select "No" you must manually remove your Oracle Home directory after the deinstall is complete. For example, if you are deinstalling Oracle SOA Suite and your SOA Oracle Home directory was /home/Oracle/Middleware/Oracle_SOA1 on a UNIX operating system:

> cd /home/Oracle/Middleware
> rm -rf Oracle_SOA1

On a Windows operating system, if your SOA Oracle Home directory was C:\Oracle\Middleware\Oracle_SOA1, use a file manager window and navigate to the C:\Oracle\Middleware directory, then right-click on the Oracle_SOA1 folder and select Delete.

2.4.4 Missing Information for Deinstalling the Oracle Common Home on Windows

If you are deinstalling an Oracle Home or the Oracle Common Home (oracle_common) directory on a Windows operating system, the directory is not automatically removed for you. After the deinstallation procedure is finished and you have dismissed the GUI, you must manually remove the Oracle Home directory after running the deinstaller.

For example, if your Oracle Home directory was C:\Oracle\Middleware\Oracle_WT1, use a file manager window and navigate to the C:\Oracle\Middleware directory, then right-click on the Oracle_WT1 folder and select Delete.

To manually remove the oracle_common directory, navigate to your Middleware Home directory (for example, C:\Oracle\Middleware, then right-click on the oracle_common folder and select Delete.

2.4.5 Invalid Oracle Home Installation Location Specified

In the installation guides for Oracle Web Tier and Oracle Portal, Forms, Reports and Discoverer, the documentation contains erroneous information regarding Oracle Home location on the Specify Installaton Location screen. The following text is incorrect:

You can specify a pre-existing Oracle Home directory (for example, you are reinstalling the software into an existing Oracle Home that was created from a previous installation that was incomplete).

If you specify an existing directory that you want to use for your Oracle Home, it must be an empty directory.

2.4.6 Invalid Note in Some Installation Guides

In the Installation Guides and Quick Installation Guides for Oracle SOA Suite, Oracle WebCenter, and Application Developer, the following note may appear:


If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.

This note is not applicable for these products and should be ignored.