This chapter describes issues associated with Oracle Fusion Middleware installation and configuration. It includes the following topics:
This section describes installation issue and workarounds. It includes the following topics:
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.
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
$ Mount_Point/runInstaller -ignoreSysPreReqs other required install options
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:
null null null
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.
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:
From the Start menu, right-click on the shortcut that generated the error message.
In the shortcut tab, go to the target node.
Change the domain name to the correct domain name.
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.
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.
If you are performing a fresh installation of Oracle Identity Management 11gR1 (Release 22.214.171.124.0) or 11gR1 PS1 (Release 126.96.36.199.0), you must install the software on the C:\ drive. If you try to install the software on a different drive, the installation will fail.
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.
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:
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
wc_contentserverconfig.sh script is run.
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:
Go to Administration.
Go to Folder Configuration.
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:
Ensure you can edit marked folders:
/custom/Folders_g/folders_environment.cfg (on UNIX) or
\custom\Folders_g\folders_environment.cfg (on Windows) file.
Verify that the
CollectionReadOnlyMarkedFolders value is set to
Restart the Content Server if you changed the
Log in to the Content Server Home Page as a user with Administrator privileges.
Go to Administration.
Go to Folder Configuration.
Go to System Folder Configuration.
Click on the green dot next to Trash. This will disable the Trash folder and will turn the dot grey.
Restore the value of
CollectionReadOnlyMarkedFolders if you had changed it and restart the Content Server.
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.
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.
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.
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.
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
password with the actual password for the SYS user.
Alternatively, you can check the values by querying the
prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;
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:
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.
Deinstall the binaries in the Oracle Home directory using the deinstaller in the
Delete all the managed servers from the failed installation in the
config.xml file by using the Administration Console or WLST.
Delete all directories in the
This procedure will enable you to reinstall the software to the same location, using the same managed server names.
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.
If you run the Integration Repository Creation Assistance Tool (
irca.sh on UNIX operating systems or
irca.bat on Windows operating systems) against an Oracle 10g database, you will get a
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.
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:
GRANT ALL ON dbms_aqadm TO user WITH GRANT OPTION; GRANT ALL ON dbms_aq TO user WITH GRANT OPTION;
user in the command with the name of your database user.
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.
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
[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 188.8.131.52.08 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 10.3.1.2.0 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.
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:
This section describes configuration issues and their workarounds. It includes the following topics:
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.
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.
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
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.
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.
When you run the
applyClone command on Windows operating systems, a
java.io.FileNotFoundException is thrown to the console.
This exception can be safely ignored and the
applyClone operation will be successfully completed.
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 nodemanager.properties file must be set to true. For example:
To configure Oracle Identity Management when the
StartScriptEnabled parameter is set to
false, you must:
StartScriptEnabled parameter to true.
Stop, then restart the Node Manager utility.
Configure Oracle Identity Management using either the Install and Configure option or the Configuration Wizard.
Note:The nodemanager.properties file is located in the WL_HOME/common/nodemanager/ directory.
If you choose to configure Oracle Internet Directory (OID) with Oracle Data Vault:
Apply patch 8897382 (see the README file in the patch for instructions).
/ldap/datasecurity/dbv_oid_command_rules.sql (on UNIX operating systems) or
\ldap\datasecurity\dbv_oid_command_rules.sql (on Windows operating systems) file, find the following code:
/declare . begin . dvsys.dbms_macadm.CREATE_COMMAND_RULE( command => 'CONNECT' ,rule_set_name => 'OID App Access' ,object_owner => 'ODS' ,object_name => '%' ,enabled => 'Y'); . commit; . end;/
Change the following line:
,object_owner => 'ODS'
,object_owner => '%'
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
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.
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 ( # )
Note: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.
In order for OCM configuration to work properly on Windows operating systems, make sure the
PATH environment variable is set to
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.
After running the Oracle Fusion Middleware Configuration Wizard to expand a cluster, the
EMD_URL parameter in the
/EMAGENT/EMAGENT/sysman/config/emd.properties (on UNIX) or
\EMAGENT\EMAGENT\sysman\config\emd.properties (on Windows) file contains the values shown below:
You must edit this parameter and replace
localdomain with the actual host and domain information of your environment. For example, using
5160 as the port number:
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.
After upgrading Oracle Identity Management from Release 10g (10.1.4.3) to 11g Release 1 (11.1.1), the Oracle Directory Service schemas (
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.
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.
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:184.108.40.206.0]: Failed while destroying servlet: usermanager. java.lang.RuntimeException: The server could not initialize properly: oracle.security.fed.sec.util.KeySourceException: 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.
Oracle SOA Suite, Oracle WebCenter, and Application Developer all contain the
unpack.sh (on UNIX systems) or
unpack.cmd (on Window systems) commands in their respective
/common/bin (on UNIX systems) or
\common\bin (on Windows systems) directories.
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
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.
unpack.cmd commands will fail if any installed products are missing from the machine where you are running the
If you are running the
unpack.sh (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
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
\config\OHS\instance_name\httpd.conf file and change the
ServerName entry to include the port number. For example:
should be changed to:
port with the actual port number.
This section describes known issues. It includes the following topics:
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.
This section describes documentation errata. It includes the following topics:
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:
Navigate to the
/wlserver_10.3/common/nodemanager (on UNIX operating systems) or
\wlserver_10.3\common\nodemanager (on Windows operating systems) directory.
nodemanager.properties file and set the
StartScriptEnabled property as follows:
Restart Node Manager.
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.
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.
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.
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.
In the Installation Guides and Quick Installation Guides for Oracle SOA Suite, Oracle WebCenter, and Application Developer, the following note may appear:
Note: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.