2 Installation, Patching, and Configuration

2.1.1.1 Installing Oracle SOA Suite on a Dual Stack Host with IPv4

If you install Oracle SOA Suite on a dual stack host and the SOA front end URL is only set to IPv4, Oracle BPM Worklist or asynchronous callbacks from IPv6-only clients may have problems resolving IPv4 callback URLs (and vice-versa).

The work around is to use either a split Domain Name System (DNS) or another forward proxy configuration. This enables the IPv6-only client to connect to a dual stack box through its IPv6 interface.

2.1.1.2 Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment

If you are installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish environment, there will be some functionality loss for Oracle Enterprise Manager Fusion Middleware Control.

There is no work around for this issue. Oracle recommends that you avoid installing in a Turkish environment and install in an English environment instead.

2.1.1.3 Configuring Oracle SOA Suite Might Fail After Installing Oracle WebLogic Server With IBM JDK7

After installing Oracle WebLogic Server Release 10.3 with IBM JDK7, configuring Oracle SOA Suite and Oracle Enterprise Content Management Suite might fail. This issue might also be seen when configuring Oracle Secure Backup and Oracle Web Center. The java core dump issue is noticed due to insufficient memory.

To work around this issue, perform the following steps:

1. Modify the commEnv.sh file located in the WLS_HOME/common/bin directory. Change the value for MEM_ARGS to:

   IBM)
   JAVA_VM=
   MEM_ARGS="-Xms256m -Xmx1024m -Xiss512m -Xss1024m"
   

2. Export JAVA_HOME and JAVA_VENDOR before configuring Oracle SOA Suite and Oracle Enterprise Content Management Suite with the following values:

   export JAVA_HOME=IBM_JDK7_location
   export JAVA_VENDOR=IBM
   

3. Reconfigure Oracle SOA Suite and Oracle Enterprise Content Management Suite

2.1.2.1 Oracle Configuration Manager Fails During Domain Configuration of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0)

After upgrading Oracle Portal, Forms, Reports, and Discoverer to 11g Release 1 (11.1.1.7.0), or after installing Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.7.0), if you choose to configure Oracle Configuration Manager during domain configuration, the configuring Oracle Configuration Manager fails.

The workaround for this issue is as follows:

1. Navigate to the following location on your system:

   ORACLE_HOME/ccr/bin
   

2. Run the following commands in the Oracle Instance home:

   $ setupCCR
   $ configCCR
   $ emCCR collect
   $ emCCR status
   

To configure Oracle Configuration Manager after configuring the domain, do the following:

1. Navigate to the ORACLE_HOME/ccr/bin directory on your system.

2. Set the variable ORACLE_CONFIG_HOME in your Oracle Instance home directory.

3. Run the following commands:

   $ setupCCR
   $ configCCR
   $ emCCR collect
   $ emCCR status
   

2.1.2.2 Considerations When Installing Oracle Portal 11g

Before you install a new Oracle Portal, Forms, Reports, and Discoverer 11g environment, be sure to review the following important resources:

• Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer

• My Oracle Support document ID 1364497.1

2.1.2.3 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.2.4 Running the rootpre.sh Script

Running the rootpre.sh script is one of the preinstallation requirements during the installation of WebTier, Identity Management, Portal, Forms, Reports, and Discoverer, on the AIX platform.

The rootpre.sh script should be run only once on a system, to load the right kernel extensions required for Oracle Database or Oracle Fusion Middleware.

Your platform requires the root user to perform certain preinstallation operating system preparations. The root user should run the shell script rootpre.sh before proceeding with Oracle installation. rootpre.sh can be found at the top level of the CD or the stage area.

Once the runInstaller is started on IBM AIX, the rootpre.sh message is automatically prompted. The following is an example of the rootpre.sh message:

./runInstaller

  Answer 'y' if root has run 'rootpre.sh' so you can proceed with Oracle installation.
  Answer 'n' to abort installation and then ask root to run 'rootpre.sh'.

  Has 'rootpre.sh' been run by root? [y/n] (n)

  Answer 'y', if root has run 'rootpre.sh' so that you can proceed with Oracle installation.
  Answer 'n', to abort installation and then ask root to run 'rootpre.sh'.

To skip the rootpre.sh prompt on systems where it has run before, set the SKIP_ROOTPRE environment variable to TRUE.

2.1.2.5 Prerequisite Checks Fail During the Installation of Oracle Portal, Forms, Reports, and Discoverer 11g Release 1 (11.1.1.2.0) on AIX 7.1

During the installation of Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1.2.0) on AIX 7.1 operating system, prerequisite checks fail with errors.

To work around this issue, perform any one of the following steps:

• Press Continue and continue with the installation.

• Use -ignoreSysPreReqs command line additional argument to the runInstaller:

  ./runInstaller -ignoreSysPreReqs
  

2.1.3.1 Oracle SOA Suite and Oracle Application Developer Must Be Installed Before Oracle Web Tier

To ensure that the oracle_common/soa/modules/commons-cli-1.1.jar file is installed properly, if you plan to associate Oracle Web Tier with an existing domain, you must install Oracle Web Tier after all other products are installed.

2.1.3.2 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.4.1 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.4.2 Extending the Schema in Oracle Internet Directory

If you have Oracle Identity Manager 11g Release 1 (11.1.1.7.0) against Oracle Internet Directory release prior to Oracle Internet Directory 11g Release 1 (11.1.1.6.0) through libOVD 11g Release 1 (11.1.1.7.0) (with oamEnabled set to true and LDAPSync enabled), when you try to create a new user, the following error is displayed:

javax.naming.directory.SchemaViolationException:[LDAP: error code 65 -Failed to find orclpwdexpirationdate in mandatory or optional attribute list.
]

Workaround:

You need to extend the schema in Oracle Internet Directory that you have installed. To change the backend IDStore schema, do the following:

1. Create a new attribute.

   attributetypes: ( 2.16.840.1.113894.200.1.7 NAME 'orclPwdExpirationDate' EQUALITY caseIgnoreMatch SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' SINGLE-VALUE USAGE userApplications).
   

2. Modify the existing orclIDXPerson objectclass to include orclPwdExpirationDate as an optional attribute.

2.1.4.3 Deinstalling a 11g (11.1.1.7.0) Oracle Internet Directory Instance Does Not Clean Up the OID Schema

When deinstalling a configured Oracle Internet Directory instance from Oracle Identity Management 11g (11.1.1.7.0) the file-based instance directory is removed, but the related Oracle Internet Directory instance configuration is not deleted. Hence, any future configuration adds to the instance count by including the deleted instances.

The following logic is missing from the command to remove a OID instance:

ldapdelete -p <oid ldap port> -D cn=orcladmin -w <password> "cn=<OID 
instance name as defined in the ODS
schema>,cn=osdldapd,cn=subconfigsubentry"

Workaround:

After deleting an instance and before recreating the instance run the command:

ldapdelete -p <oid ldap port> -D cn=orcladmin -w <password> "cn=<OID
instance name as defined in the ODS schema>,cn=osdldapd,cn=subconfigsubentry 

2.1.4.4 Information about the Oracle Virtual Directory Adapters

Oracle Virtual Directory adapters are not listed in the Home page.

To work around this issue on Linux operating systems, copy the osdt_cert.jar file from the Oracle Common home to the directory under ORACLE_HOME/inventory/Scripts/ext/lib/Oracle_IDM1.

To work around this issue on Windows operating systems, copy the jar prior to the configuration phase because it does not work if you copy it later.

2.1.4.5 Enabling the Retry Button

To retry a failed Oracle Identity Management configuration you must enable the Retry button. Check the box on the left side of the failed item to enable the Retry button.

2.1.4.6 Server Startup Failures on Linux Operating Systems

When starting the Oracle Identity Management server (Managed server or Administration server), the server may fail to start. You may see the following error:

Failed to push ldap config data to
libOvd for service instance "idstore.ldap" in JPS context "default", cause:
java.io.FileNotFoundException: /tmp/.ovdlock.tmp (Permission denied)> 

To work around this issue, run the following command and the start he server again:

chmod 666 /tmp/.ovdlock.tmp

2.1.4.7 Configuring OPMN Request Port

The static ports.ini for the Oracle Identity Management 11g Release 1 (11.1.1.7.0) installer has an OPMN request port specified. This port is not used in the Oracle Identity Management configuration and does not serve any specific functional purpose.

To configure the port you have to manually add the entry to opmn.xml after the oracle instance is provisioned.

2.1.4.8 Silent Install with Privileged Ports on Linux Operating Systems

To install and configure privileged ports in silent mode on Linux operating systems, do the following:

1. Complete only a silent install with Oracle Identity Management 11g Release 1 (11.1.1.7.0).

2. Run the oracleroot.sh and oidroot.sh scripts in the Oracle home.

   You must run these scripts as root user.

3. Change .apachectl permissions.

   Run the following as root user:

   /bin/chown root /$OH/ohs/bin/.apachectl
   /bin/chmod 6750 /$OH/ohs/bin/.apachectl
   

4. Complete a silent configuration with the privileged ports.

2.1.5.1 Specifying the JRE Location if Installing with Automatic Updates

If you are ins7talling one of the following Oracle Fusion Middleware products:

• Oracle SOA Suite

• Oracle WebCenter Portal

• Oracle Service Bus

• Oracle WebCenter Content

• Oracle Data Integrator

• Oracle Identity and Access Management

And you will choose to configure automatic updates on the Install Software Updates screen by selecting Download and install updates from My Oracle Support you must specify the location of a JRE on your system by using the -jreLoc parameter from the command line when you start the installer.

If you do not use the -jreLoc parameter and instead wait for the installer to prompt you for a JRE location, an exception will be seen during the installation.

2.1.5.2 Out of Memory Errors When Using JDK 6 Update 23

If you are experiencing out-of-memory errors when using JDK 6 Update 23, consider the following.

In JDK 6 Update 23, the escape analysis feature was enabled by default.This is an optimization within the hotspot compiler, which may require an increased memory footprint. When there is very little free space in the process for additional native memory allocations, for example due to a very large Java heap, this could lead to an out of memory situation.

The workaround for this issue is to add the following JVM argument when you start your application:

-XX:-DoEscapeAnalysis

You can identify JDK 6 Update 23 by using the java -version command, as follows:

java -version
   java version "1.6.0_24"
   Java(TM) SE Runtime Environment (build 1.6.0_24-b50)
   Java HotSpot(TM) Server VM (build 19.1-b02, mixed mode)

2.1.6.1 Installer Produces Errors When Checking for Software Updates on My Oracle Support

On the Install Software Updates screen, if you select the Search My Oracle Support for Updates option, provide the proper user credentials, and then click Search for Updates, the following error is seen in the installation log file:

java.net.NoRouteToHostException: No route to host

The work around is to use the Search Local Directory for Updates option on the Install Software Update screen and select a patch that has already been downloaded and is available locally. Patches can be downloaded manually from My Oracle Support or they can be obtained from your Oracle Support representative.

2.1.7.1 Error Encountered While Loading the Oracle Internet Directory (ODS) Schema

If you have password policy enabled at the database level on your Oracle database, you will receive the ORA-28003 error when loading the Oracle Internet Directory (ODS) schema.

To work around this issue, temporarily disable password policy, load the schema, then enable password policy again.

2.1.7.2 Setting the Correct Permission for the DBMS_REPUTIL Database Package

If you are creating the Oracle Internet Dirctory schemas in Oracle Database version 11.2.0.4 or later, use the following work around if you encounter an error from RCU:

1. Connect to the database as administrator and execute the following:

   GRANT EXECUTE ON DBMS_REPUTIL TO PUBLIC;
   

2. Re-start RCU and create the schema.

3. After the schema is successfully created, connect to the database again as administrator and execute the following:

   REVOKE EXECUTE ON DBMS_REPUTIL FROM PUBLIC;
   

2.1.7.3 Setting the Correct Permission for the DBMS_JOB Database Package

If you are creating the Oracle Internet Directory schema in an Oracle database using RCU, you may encounter the following error messages:

ORA-04063: package body "ODS.TSPURGE" has errors
ORA-06508: PL/SQL: could not find program unit being called: "ODS.TSPURGE"
ORA-06512: at line 3

To work around this issue:

1. Stop RCU and drop any Oracle Internet Directory schemas already created. Refer to "Dropping Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide for instructions.

2. Log into the database using SQL*Plus and run the following command:

   SQL> grant execute on sys.dbms_job to PUBLIC
   

3. Run RCU again and create the schemas.

2.1.7.4 Database Connection Failure During Schema Creation When Installing Oracle Internet Directory

If the installation of Oracle Internet Directory fails due to timeout or connection failure when connecting to a database for schema creation, you can try to reset the timeout parameter in the rcu.properties file. This file is located in the IDM_HOME/rcu/config directory-.

Open the rcu.properties file in a text editor, search for the property JDBC_LOGIN_TIMEOUT, and set its value to 30.

2.1.7.5 Using RCU 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1)

If you are using the version of RCU that is available in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) with Oracle Database 11g (11.2.0.1), you will receive the following warning message:

The database you are connecting is not a supported version. Enter Database
with version equal to or higher than 10.2.0.4.0 in 10g or version equal to
higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for
supported DB versions.

This warning can be safely ignored and you can proceed with your RCU operations.

This warning will not appear in the version of RCU available in Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or later.

2.1.8.1 Error Messages When Installing on IBM AIX 7.1

When installing Oracle Fusion Middleware 11g products on IBM AIX 7.1, you may see the following errors during the prerequisite checking portion of the installation:

Checking operating system certification
Expected result: One of 5300.08,6100.02
Actual result:: 7100.xx
Check complete. The overall result of this check is: Failed <<<<
Problem: This Oracle software is not certified on the current operating system
 
Checking recommended operating system patches
Check complete: The overall result of this check is: Not executed <<<< 

These messages can be safely ignored. Selecting Continue in the dialog box will allow the installation to proceed.

2.1.8.2 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.8.3 Sun JDK and Oracle Configuration Manager 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 1.6.0.14.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.

2.1.9.1 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.9.2 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.2.2.1 Patch Set Assistant Fails When Updating the SOAINFRA Schema in SQL Server Databases

If you attempt to update the SOAINFRA schema in a Microsoft SQL Server database, then the Fusion Middleware Patch Set Assistant fails to complete the operation. This is a known issue with no current workaround. Contact Oracle Support or refer to My Oracle Support for more information:

http://support.oracle.com/

2.2.2.2 Exception Seen When Extending Your Existing Oracle SOA Suite Domain with Oracle Business Process Management Suite

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and are extending your existing domain to include Oracle Business Process Management Suite:

javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested exception
 is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
 org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
 ORA-02292: integrity constraint (DB9128_SOAINFRA.BPM_CUBE_ROLE_FK1) violated -
 child record found.
Error Code: 2292
Call: DELETE FROM BPM_CUBE_PROCESS WHERE (PROCESSID = ?)
        bind => [247]
Query: DeleteObjectQuery(CubeProcess(domain:default, composite:counter_extended,
 revision:1.0, name:Process, hasNametab:true));
nested exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
 org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9128_SOAINFRA.BPM_CUBE_ROLE_FK1) violated -
 child record found

This is a harmless exception. To avoid seeing this exception, do the following:

1. Connect to your database as the SOA schema user.

2. Drop the BPM_CUBE_ROLE_FK1 constraint by executing the following:

   ALTER TABLE BPM_CUBE_ROLE DROP CONSTRAINT BPM_CUBE_ROLE_FK1;
   

3. Recreate the BPM_CUBE_ROLE_FK1 constraint by executing the following:

   ALTER TABLE BPM_CUBE_ROLE ADD CONSTRAINT BPM_CUBE_ROLE_FK1 FOREIGN KEY @
   (ProcessId) REFERENCES BPM_CUBE_PROCESS(ProcessId) ON DELETE CASCADE;
   

4. Restart the Oracle SOA Managed Server.

2.2.2.3 Exception Seen When Undeploying any SOA Composite with Range-Based Dimension Business Indicators

The following intermittent exception may be seen in cases where you have upgraded your Oracle SOA Suite software to release 11.1.1.3.0 with the Patch Set Installer, and have undeployed SOA composites that have range-based dimension business indicators:

javax.ejb.EJBTransactionRolledbackException: EJB Exception: ; nested
exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9967_SOAINFRA.BPM_CUBE_NAMETAB_RANGE_FK1)
violated - child record found
 
Error Code: 2292
Call: DELETE FROM BPM_CUBE_NAMETAB WHERE ((EXTENSIONID = ?) AND (NAMETABID =
?))
        bind => [0, 603]
Query:
DeleteObjectQuery(oracle.bpm.analytics.cube.persistence.model.CubeNametab@b7b8
2a); nested exception is: javax.persistence.PersistenceException: Exception
[EclipseLink-4002] (Eclipse Persistence Services - 2.0.2.v20100323-r6872):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException:
ORA-02292: integrity constraint (DB9967_SOAINFRA.BPM_CUBE_NAMETAB_RANGE_FK1)
violated - child record found 

This exception is harmless and can be safely ignored. To avoid seeing this exception, do the following:

1. Connect to your database as the SOA schema user.

2. Drop the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

   ALTER TABLE BPM_CUBE_NAMETAB_RANGE  DROP CONSTRAINT BPM_CUBE_NAMETAB_RANGE_FK1;
   

3. Recreate the BPM_CUBE_NAMETAB_RANGE_FK1 constraint by executing the following:

   ALTER TABLE BPM_CUBE_NAMETAB_RANGE ADD CONSTRAINT BPM_CUBE_NAMETAB_RANGE_FK1
   FOREIGN KEY @ (ProcessId, NametabId, ExtensionId) REFERENCES
   BPM_CUBE_NAMETAB (ProcessId, NametabId, ExtensionId) ON DELETE CASCADE;
   

4. Restart the Oracle SOA Managed Server.

2.2.2.4 Running Oracle Business Process Management Suite with Microsoft SQL Server 2008 Database

If you have patched your existing Oracle SOA Suite installation with the Patch Set Installer to include Oracle Business Process Management Suite and you are using a Microsoft SQL Server 2008 database, the following procedure is required after you have patched your software:

1. Login to the Administration Console.

2. In the "Connection Pools" tab, add the following property in the "Properties" section for the mds-owsm and mds-soa data sources:

   ReportDateTimeTypes=false
   

2.2.2.5 Update to Oracle SOA Suite Release 11.1.1.3.0 Does Not Remove the b2b.r1ps1 Property

After you update your Release 11.1.1.2.0 software to Release 11.1.1.3.0, and login to the Oracle Enterprise Manager Console and navigate to the b2b Properties screen, the b2b.r1ps1 property (used to enable Release 11.1.1.2.0 features such as DocProvisioning and TransportCallout) is still visible. This property is removed for Release 11.1.1.3.0.

To remove this property, use the MBean browser remove property operation in Fusion Middleware Control. For more information, see "Configuring B2B Operations" in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite.

2.2.2.6 Manual Steps for Migrating Oracle UMS and Oracle MDS

If you migrate your database schemas from Release 11.1.1.1.0 to Release 11.1.1.2.0 with the BAM Alone option:

ant master-patch-schema -DpatchMaster.Componentlist=BAM

The Oracle BAM server will not start and you will receive UMS and MDS exceptions. After executing above command, if no errors are seen in the log files and if the version in schema_version_registry is changed to 11.1.1.2.0 for Oracle BAM, then the following commands must be executed to manually migrate Oracle UMS and MDS:

ant master-patch-schema -DpatchMaster.Componentlist=MDS
ant master-patch-schema -DpatchMaster.Componentlist=UMS

Then, start the Oracle BAM server after running these commands.

2.2.2.7 Monitored BPEL Processes Generate Warning Messages in Log File After Applying 11g Release 1 (11.1.1.4.0) Patch Set

If you deployed BPEL processes that are instrumented with monitors, then Oracle BAM might generate warning messages in the SOA diagnostic log file after you apply the 11g Release 1 (11.1.1.4.0) patch set.

This is because a new business indicator data object field ("LATEST") was added for Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0).

To avoid the warning message and to take advantage of the new data object field, redeploy the BPEL process after you apply the 11g Release 1 (11.1.1.4.0) patch set.

For more information about the LATEST data object field, see "Understanding Business Indicator Data Objects" in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

2.2.2.8 Oracle Rules Error in Administration Server Log Files After Patching an 11g Release 1 (11.1.1.2.0) Domain

If you are applying the latest Oracle Fusion Middleware 11g patch set to an 11g Release 1 (11.1.1.2.0) Oracle home, then you might see the following error in the Administration Server log files:

<Unresolved optional package references (in META-INF/MANIFEST.MF):
[Extension-Name: oracle.rules, referenced from: 
/app/orasoa/product/soa11g/middleware/user_projects
   /domains/soadev/servers/AdminServer/tmp/_WL_user/emai/xalnv4]
Make sure the referenced optional package has been deployed as a library.>

You will see this error if deployed a Oracle SOA Suite composite application to the domain previous to applying the patch set. This because, starting with Oracle Fusion Middleware 11g Release 1 (11.1.1.3.0), the Rules library (oracle.rules) must be targeted to the Administration Server, as well as to the SOA managed servers.

To avoid this message:

1. Use the Oracle WebLogic Server Administration Console to select the oracle.rules shared library and target it to the Administration Server as well as to the SOA managed servers in the domain.

2. Redeploy the application to the domain using Oracle JDeveloper 11g Release 1 (11.1.1.3.0) or later.

2.2.2.9 Incorrect Instance State of Composite Applications After Applying the Latest Patch Set

If you deployed any composite applications in Oracle SOA Suite 11g Release 1, and then you apply the latest 11g Release 1 patch set, then you might find that the instance state of some of your composite applications appears incorrect.

For example, if any of your composite applications were in a "recovery required" state before you applied the patch set, then those composite applications may be identified as completed when you view them on the Dashboard tab of the SOA Composite page in Fusion Middleware Control.

In these cases, you can ignore the "completed" indicator. The instances are actually still running and will be treated as such by other operations, such as a purge operation.

After you install the patch set, you should analyze each of these instances to determine whether they should be completed, aborted, or left to continue.

For more information about monitoring the state of SOA Composite applications, see "Monitoring SOA Composite Applications" in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle BPM Suite.

2.2.3.1 Problem Using WebCenter Portal: Spaces Customizations with .jsp Pages after Installing the 11.1.1.7.0 Patch Set

If you extended WebCenter Portal: Spaces 11g Release 1 (11.1.1.2.0) or Release 1 (11.1.1.3.0) with your own customizations, then before you upgrade, you must ensure that the customization shared library uses .jspx pages and not .jsp pages.

After you upgrade to WebCenter Portal: Spaces 11.1.1.7.0, custom site templates will not render if they use .jsp pages.

Note that if you followed the white paper Customizing Site Templates in WebCenter Spaces to develop your custom site templates, then your pages should already be .jspx pages.

2.2.3.2 Errors When Updating Oracle WebCenter Portal Using WLST Commands

If you are updating Oracle WebCenter Portal using WLST commands, you may see some error messages as described in this section. These errors can be safely ignored provided that when the command completes there is some text indicating the successful completion of the command.

When running the upgradeWebCenterDomain WLST command, you may see the following error message:

Error: addTemplate() failed. Do dumpStack() to see details.

When running the upgradeWebCenterPermissions command, you may see the following error message:

Command FAILED, Reason: JPS-04204: Cannot revoke permissions.

2.2.3.3 Errors When Adding Tagging and Search Task Flows to Pages

In your Oracle WebCenter 11.1.1.4.0 instance if you used a resource catalog based on the Default Page Template Catalog, then in your patched WebCenter Portal 11.1.1.7.0 instance you may encounter problems while adding the Tagging and Search task flows to pages. To address this issue, in your patched instance, you must edit your resource catalog, and add the Tagging and Search task flows again.

2.2.3.4 Personalization Settings in Activity Graph Task Flows Lost When WebCenter Portal is Patched

Personalization settings made for Activity Graph task flows, such as Similar Items and Recommended Connections, may be lost and task flows may revert to default settings when you patch WebCenter Portal to the latest release. You must make all the personalization settings again for your Activity Graph task flows as required.

2.2.3.5 Language Not Displayed in the List of Languages Offered in Spaces

If you extended the Spaces application to add support for a new language, you may encounter problems working with the language after you patch to WebCenter Portal 11.1.1.7.0. The language may not display in the default list of languages offered in Spaces. To resolve this issue, you must re-upload the supported-languages.xml file containing the entry for the required language.

2.2.4.1 Access Denied When Running the oimPS1PS2upgrade Script

If you are upgrading Oracle Identity Management and need to run the oimPS1PS2upgrade.sh script, you must add the following to the grant() method in the JAVA_HOME\jre\lib\security\java.policy file:

// JMX Java Management eXtensions
permission javax.management.MBeanTrustPermission "register";

After making this change, stop and restart all the servers.

2.2.4.2 Installer Prompts for OID Privileged Ports Twice During the Patch Installation

If you are patching an existing Oracle Internet Directory installation to 11g Release 1 (11.1.1.7.0), you will be prompted to run the oracleRoot.sh script near the end of the patch installation, which in turn will ask for the following:

Do you want to run oidRoot.sh to configure OID for privileged ports?(yes/no)

Depending on the OID version being patched, you may be asked this question a second time. Make sure you enter the same response ("Yes" or "no") both times in order for the script to run correctly.

There is no work around for this issue.

2.2.4.3 Installer Does Not Detect Existing Oracle Home

If you are upgrading to Oracle Identity Management to 11g Release 1 (11.1.1.7.0) from 11g Release 1 (11.1.1.4.0), the installer does not detect the existing Oracle home directory for upgrade in the following environments:

• On 64-bit Windows operating systems, using the Traditional Chinese, Simplified Chinese, or Korean locales.

• On 64-bit Linux operating systems, using the Non UTF-8 locale for Japanese, Korean, Simplified Chinese and Traditional Chinese.

This is caused because the English word "Optional" gets translated in the MW_HOME/oracle_common/inventory/ContentsXML/comps.xml file.

There are two work arounds for this issue:

1. Manually specify the Oracle Identity Management Oracle home directory you want to update, and then continue with the upgrade installation.

2. Find all occurrences of the translated word and replace them with the English word "Optional" in the comps.xml file and then run the installer after you are finished making the changes. The word "Optional" appears with the following two parameters in the comps.xml file:

   DEP_GRP_NAME="Optional"
   EXT_NAME="Optional"
   

   Note:

   The comps.xml file is an important file used by the Oracle Universal Installer so it is important that you do not make any errors while editing this file. You should make a backup copy of this file before you make any changes.

2.2.4.4 Uploading Third Party JAR Files to the Database

During the update of Oracle Identity and Access Management to 11g Release 1 (11.1.1.5.0), third party JAR files (for example, ldapbp.jar which is required for connector functionality) that are present in the file system are not uploaded to database by the upgrade process. You must manually upload these JAR files to the database using the UploadJars.sh utility.

For more information, see the "Upload JAR and Resource Bundle Utilities" chapter in Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager.

2.2.4.5 Access Policy With Approval Does Not Work After Patch

In 11g Release 1 (11.1.1.5.0), the following new policies are introduced for Oracle Entitlements Server (OES):

• SelfServiceUserManagementPolicies.xml

• UserManagementPolicies.xml

Because of this change, a request for approval is not generated when a new policy with approval is added.

To work around this issue, add the "Request Administrator" role to the "Access Policy Based Provisioning" request template:

1. Login to "Advance Console."

2. Go to Request Templates on the Configuration tab.

3. Search for and open the "Access Policy Based Provisioning" request template.

4. Go to the Template User Roles tab on the Template Details page.

5. From the left pane in "Available Roles," search for and assign the "Request Administrators" role.

   The assigned role will appear in the right pane under "Selected Roles."

6. Save the request template.

2.2.4.6 OID and OVD Saved Connections Not Available After Patch From 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0)

If you are patching Oracle Internet Directory (OID) or Oracle Virtual Directory (OVD) from 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0) to 11g Release 1 (11.1.1.4.0) or later, your saved connections in the previous releases will not be available after the patch.

If you are patching from 11g Release 1 (11.1.1.4.0) to any later release, then your saved connections in OID and OVD will be available.

There is no work around for this issue.

2.2.4.7 Harmless Error When Running the upgradeOpss() Command When Upgrading Oracle Identity Management

During the upgrade of Oracle Identity Manager 11g Release 1 (11.1.1.3.0) to 11g Release 1 (11.1.1.5.0), you are asked to run the upgradeOpss WLST (online) command to update Oracle Platform Security Services (OPSS).

The following message will be visible on the console when you run the upgradeOpss command:

WLS ManagedService is not up running. Fall back to use system properties for configuration.
date_and_time oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy <init>
WARNING: No identity store associate with policy store found.
Upgrade of jps configuration and security stores is done.

This message is harmless and can be safely ignored.

2.2.4.8 Harmless Errors in the Log Files After Patching Oracle Identity Management to 11g Release 1 (11.1.1.4.0)

After patching and configuring Oracle Identity Management to 11g Release 1 (11.1.1.4.0), the following errors are seen in the wls_oif1-diagnostics.log file when Single Sign-On is used for Oracle Identity Federation:

[2010-08-05T13:05:30.754-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
42ef6c66fe18f3ad:291f353a:12a43da27c1:-8000-0000000000000021,0] [APP:
OIF#11.1.1.2.0] [arg: certvalidationtimeout] Property was not found:
certvalidationtimeout.
.
[2010-08-05T13:05:37.174-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
42ef6c66fe18f3ad:291f353a:12a43da27c1:-8000-0000000000000021,0] [APP:
OIF#11.1.1.2.0] [arg: schemavalidationenabled] Property was not found:
schemavalidationenabled

[2010-08-06T17:09:23.861-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
f6d9b81289e40cee:42d4f595:12a49b7af7a:-8000-000000000000086f,0] [APP:
OIF#11.1.1.2.0] [arg: certpathvalidationenabled] Property was not found:
certpathvalidationenabled.
 
[2010-08-06T17:11:27.173-07:00] [wls_oif1] [INCIDENT_ERROR] [FED-10174]
[oracle.security.fed.model.config.Configuration] [tid:
[ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: <anonymous>] [ecid:
f6d9b81289e40cee:42d4f595:12a49b7af7a:-8000-00000000000009a0,0] [APP:
OIF#11.1.1.2.0] [arg: httpheaderattrcollector] Property was not found:
httpheaderattrcollector. 

There errors are harmless and can be safely ignored.

To avoid seeing these errors, run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py script after you have patched your software to 11.1.1.4.0 as described in "Updating Configuration Properties in Oracle Identity Federation" in the Oracle Fusion Middleware Patching Guide.

2.2.4.9 Harmless Warning Message When Migrating Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0)

When you are using the Patch Assistant migration scripts to migrate Oracle Identity Federation from 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0), you may see the following error message:

WLSTException: Error occured while performing addHelpCommandGroup : Error
getting resource bundle: : Can't find bundle for base name
oifWLSTResourceBundle, locale en_US

This message is harmless and can be safely ignored.

2.2.4.10 Harmless Errors Logged When Patching Oracle Identity Management 11g Release 1 (11.1.1.2.0) to 11g Release 1 (11.1.1.3.0)

You may see some of the following error messages in installation log files after patching an Oracle Identity Management 11g Release 1 (11.1.1.2.0) installation to 11g Release 1 (11.1.1.3.0):

External name..INVALID_ORACLE_DIRECTORY_MSG_STRING

In doFinish method checking for inventory lock...InstallProgressPage

Next page is a progress page and the inventory lock is false

/bin/chmod: changing permissions of ORACLE_HOME/install/root.log': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmhs': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmb': Operation not permitted

/bin/chmod: changing permissions of ORACLE_HOME/bin/nmo': Operation not permitted

inventoryLocation: /scratch/aime1/oraInventory

Mode:init

Such messages can be ignored.

2.2.4.11 Harmless Exception Seen When Starting Oracle Identity Management Server 11g Release 1 (11.1.1.5.0)

After updating Oracle Identity Management to 11g Release 1 (11.1.1.5.0), the following exception may be seen when starting Oracle Identity Management Server:

java.lang.ClassNotFoundException: ADP ClassLoader failed to load:com.thortech.xl.schedule.tasks.tcTskScheduledProvision

This error is harmless and can be safely ignored.

2.2.5.1 Granting Access to Network-Related Packages for the Oracle Portal Schema

While running the Patch Set Assistant to upgrade the schema for Oracle Portal 11g Release 1 (11.1.1.4.0) in an environment where Oracle Single Sign-On 10.1.4.3 is running against Oracle Internet Directory 11g and Oracle Database 11.2.0.2, the following exception is encountered:

ORA-24247: network access denied by access control list (ACL)

To address this issue when executing network-related packages, access must be granted to the user using these packages. You must create the ACL for the ORASSO schema user, and assign it to the OID host. Then, you must run the wdbigra.sql script, which gives the required grants to Oracle Portal schema.

1. Grant the ACL for the PORTAL schema user and assign it for the OID host.

   Connect as sys as sysdba and assign the ACL as in the example below, where examplehost.exampledomain.com is the OID hostname and the DEV_PORTAL is the Oracle Portal schema specified for the installation:

   DECLARE
   acl_path VARCHAR2(4000);
    
   BEGIN
    
   SELECT acl INTO acl_path FROM dba_network_acls
   WHERE host = 'examplehost.exampledomain.com' AND lower_port IS NULL AND upper_port IS NULL;
   dbms_output.put_line('acl_path = '|| acl_path);
   dbms_output.put_line('ACL already Exists. Checks for Privilege and add the Privilege');
   IF DBMS_NETWORK_ACL_ADMIN.check_privilege(acl_path,'DEV_PORTAL','connect') IS NULL THEN
      DBMS_NETWORK_ACL_ADMIN.add_privilege (
      acl => acl_path,
      principal => 'DEV_PORTAL',
      is_grant => TRUE,
      privilege => 'connect');
   END IF; 
   END;
   /
   COMMIT;
   

   When no ACL has been assigned for the OID host, create the ACL:

   EXCEPTION
   WHEN no_data_found THEN
   
   DBMS_NETWORK_ACL_ADMIN.create_acl (
      acl => 'sso_oid.xml',
      description => 'ACL for SSO to connect to OID',
      principal => 'ORASSO',
      is_grant => TRUE,
      privilege => 'connect');
    
   DBMS_NETWORK_ACL_ADMIN.assign_acl (
      acl => 'sso_oid.xml',
      host => 'examplehost.exampledomain.com');
   END;
   /
   COMMIT; 
   

   Use the following SQL command to verify that the ACL was created:

   select * from dba_network_acls; 
   

2. Modify the values of the host and schema in the wdbigra.sql file, located in the ORACLE_HOME/upgrade/portal/admin/plsql/wwv directory.

   Change the following:

   host varchar2(1)        := '*';
   schema varchar2(2000)   := upper('&&1'); 
   

   To the following:

   host varchar2(1)        := '&OID_HOST';
   schema varchar2(2000)   := upper('&PORTAL_SCHEMA'); 
   

3. Run the wdbigra.sql script to give the grants to the Oracle Portal schema.

   The script will prompt you for the following:

   • The value for the oid_host.

     Specify the host where Oracle Internet Directory is running (for example, examplehost.exampledomain.com).

   • The value for the portal_schema.

     Specify the prefix and schema name (for example, DEV_PORTAL).

2.2.5.2 Redeploy System Components to Ensure Proper Deinstallation

After you have patched your system component software (Oracle Portal, Forms, Reports and Discoverer, Oracle Identity Management, or Oracle Web Tier) and started all services, you must manually redeploy your system components if you are extending your existing domain. To do so, follow the instructions to redeploy in the "Upgrading System Components" section of the Oracle Fusion Middleware Patching Guide.

If you do not redeploy your system components, you will encounter problems when you attempt to remove them.

2.2.5.3 Setting Execute Permissions for emctl When Migrating System Components

When you migrate any 11g Release 1 (11.1.1.1.0) system component to 11g Release 1 (11.1.1.2.0), the following error message can be seen on the console window:

Process (index=1,uid=1270434032,pid=0)
Executable file does not have execute permission.

INSTANCE_HOME/EMAGENT/EMAGENT/bin/emctl
failed to start a managed process after the maximum retry limit
Executable file does not have execute permission.

The work around is to manually change the permissions of the emctl executable. For example:

chmod +x INSTANCE_HOME/EMAGENT/EMAGENT/bin/emctl

After changing the permissions, restart all the opmnctl processes.

2.2.6.1 Oracle SOA Suite Tasks Not Visible in Firefox Browser After Upgrade

If you are upgrading Oracle SOA Suite to 11g Release 1 (11.1.1.7.0) from any previous release, not all tasks may be visible in Firefox browser after the upgrade is complete.

To work around this issue, refresh your browser's cache to see all tasks.

2.2.6.2 Some Applications Show Old Version Number After Patching

After you patch your Oracle Fusion Middleware environment, some applications still show the version number from previous releases. For example, after you patch Oracle WebLogic Server 10.3.4 to the latest release, the version number is still shown as 10.3.4.

There is no work around for this issue.

2.2.6.3 MDS Schema Version Number is Incorrect

If you are running Fusion Middleware products that use the Metadata Services schema (MDS) and your Fusion Middleware products are older than 11g Release 1 (11.1.1.4.0), the schema version number for the MDS schema in Enterprise Manager will be the previous release number, even if you have updated the MDS schema to 11g Release 1 (11.1.1.4.0).

In order for the MDS schema version number to appear correctly, both the schema and the Fusion Middleware product software must be up to date with the most recent version.

2.2.6.4 Oracle BI Components Show Incorrect Version Number After Patching

After you patch your existing Oracle Business Intelligence (BI) software to 11g Release 1 (11.1.1.4.0), some Oracle BI components (for example, Oracle BI Publisher or Oracle RTD) will still show the version number from your previous release when viewed using Oracle Enterprise Manager.

There is no work around for this issue.

2.2.6.5 Adding the Version Number for the odi-sdk-ws Application in config.xml

In 11g Release 1 (11.1.1.6.0), the odi-sdk-ws application was updated to introduce a version number. If you are upgrading the odi-sdk-ws application to 11g Release 1 (11.1.1.6.0) from any previous release, this version number must be added to the config.xml file prior to starting the Administration server or Managed Servers in the domain.

To do this:

1. Edit the DOMAIN_HOME/config/config.xml file.

2. Change the following line:

   <name>odi-sdk-ws</name>
   

   To add a version number, as follows:

   <name>odi-sdk-ws#11.1.1.6.0.1</name>
   

3. Start or restart the Administration Server and Managed Servers in the domain.

2.2.7.1 Pages in Oracle Enterprise Manager and Oracle Directory Services Manager do not Display Correctly

After upgrading to 11g Release 1 (11.1.1.7.0), if you encounter problems with pages in Oracle Enterprise Manager (EM) or Oracle Directory Services Manager (ODSM) not being displayed correctly, do the following before starting all the servers in the domain:

1. Add the value -XX:-UseSSE42Intrinsics to the DOMAIN_HOME/bin/setDomainEnv.sh file as follows:

   Find the following section of code:

   if [ "${JAVA_VENDOR}" = "Sun" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE}"
           export MEM_ARGS
   fi
    
   if [ "${JAVA_VENDOR}" = "HP" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
           export MEM_ARGS
   fi
    
   if [ "${JAVA_VENDOR}" = "Apple" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE}"
           export MEM_ARGS
   fi
   

   And change it to:

   if [ "${JAVA_VENDOR}" = "Sun" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_DEV_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
           export MEM_ARGS
   fi
    
   if [ "${JAVA_VENDOR}" = "HP" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
           export MEM_ARGS
   fi
    
   if [ "${JAVA_VENDOR}" = "Apple" ] ; then
           MEM_ARGS="${MEM_ARGS} ${MEM_MAX_PERM_SIZE} -XX:-UseSSE42Intrinsics"
           export MEM_ARGS
   fi
   

2. For Oracle EM, remove the .css file from the following directory:

   On UNIX operating systems:

   DOMAIN_HOME/servers/AdminServer/tmp/_WL_user/em/random_dir/public/adf/styles/cache
   

   On Windows operating systems:

   DOMAIN_HOME\servers\AdminServer\tmp\_WL_user\em\random_dir\public\adf\styles\cache
   

3. For ODSM, remove the .css file from the following directory:

   On UNIX operating systems:

   DOMAIN_HOME/servers/wls_ods1/tmp/_WL_user/odsm_release/random_dir/public/adf/styles/cache
   

   On Windows operating systems:

   DOMAIN_HOME\servers\wls_ods1\tmp\_WL_user\odsm_release\random_dir\public\adf\styles\cache
   

4. Clear your browser cache to remove any browser clients that visited the sites using the .css file you just removed.

5. Start or restart all the servers in the domain.

2.2.8.1 Harmless Warnings When Running upgradeOpss()

When running the upgradeOpss() WLST command to upgrade configurations and stores to 11g Release 1 (11.1.1.4.0), the following error messages may be seen:

oracle.security.jps.internal.tools.utility.destination.apibased.JpsDstPolicy
migrateData
WARNING: cannot migrate a global grant. Reason
oracle.security.jps.service.policystore.PolicyStoreException: Found 2 permissions
in the store matching: ([PermissionEntry:class=java.util.PropertyPermission
target=weblogic.Name resourceType=null actions=read,PERMISSION, name=null,
uniqueName=null, guid=null]
[jaznGranteeDn=orclguid=AC171BF0E72711DEBF9CCF0B93FB22A1,cn=Grantees,
cn=JAASPolicy,cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod}),
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name
resourceType=null actions=read,PERMISSION, name=8228FD8036F711DEAF24DB7D80B2D07C,
uniqueName=orclguid=8228FD8036F711DEAF24DB7D80B2D07C,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod, 
guid=8228FD8036F711DEAF24DB7D80B2D07C]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaas
policy,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}1
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name 
resourceType=null actions=read,PERMISSION, name=8228FD8036F711DEAF24DB7D80B2D07C, 
uniqueName=orclguid=8228FD8036F711DEAF24DB7D80B2D07C,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod, 
guid=8228FD8036F711DEAF24DB7D80B2D07C]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name 
resourceType=null actions=read,PERMISSION, name=AC198CF0E72711DEBF9CCF0B93FB22A1, 
uniqueName=orclguid=AC198CF0E72711DEBF9CCF0B93FB22A1,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod, guid=AC198CF0E72711DEBF9CCF0B93FB22A1]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}
[jaznGranteeDn=orclguid=ac171bf0e72711debf9ccf0b93fb22a1,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}2
[PermissionEntry: class=java.util.PropertyPermission target=weblogic.Name 
resourceType=null actions=read,PERMISSION, name=AC198CF0E72711DEBF9CCF0B93FB22A1,
uniqueName=orclguid=AC198CF0E72711DEBF9CCF0B93FB22A1,cn=Permissions,cn=JAASPolicy,
cn=systempolicy,cn=webcenter,cn=JPSContext,cn=jpsroot_webcenter_IR14_prod, 
guid=AC198CF0E72711DEBF9CCF0B93FB22A1]
[jaznGranteeDn=orclguid=822505e036f711deaf24db7d80b2d07c,cn=grantees,cn=jaaspolicy
,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_
prod}[jaznGranteeDn=orclguid=ac171bf0e72711debf9ccf0b93fb22a1,cn=grantees,cn=jaas
policy,cn=systempolicy,cn=webcenter,cn=jpscontext,cn=jpsroot_webcenter_ir14_prod}

These messages are harmless and can be safely ignored.

2.2.8.2 Harmless Warning Message in Log File When Patching Multiple Products to the Same Version

In a scenario where you have a product that is already patched to version 11g Release 1 (11.1.1.3.0) in a Middleware home, and then you attempt to patch a second product to the same version in the same Middleware home, a warning message similar to the following will appear in the installtimestamp.out file:

Attempting to install 1 patches
Mar 3, 2010 1:00:07 PM [THREAD: Thread-1]
com.bea.cie.paf.internal.attach.PatchManagerImpl install
WARNING: Warning:  Patch already installed: PBY8
 
Patch installation success
Patch installation success
Success..
[SOARootService.getRootActions] autoPortsDetect =null
[SOARootService.getRootActions] privilegedPorts =null

This warning message can be safely ignored.

2.2.8.3 Error When Accessing the Oracle Portal Home Page

If you are upgrading to Oracle Portal 11g Release 1 (11.1.1.6.) from any previous release, the following error message is displayed in the browser when accessing the Oracle Portal home page:

XML Parsing Error: syntax error
Location: http://exampleserver.exampledomain:port/portal/pls/portal/dev_portal.home
Line Number 1, Column 1:An error occurred while processing the request. Try refreshing your browser. If the problem persists contact the site administrator
î

This occurs because the Web Cache invalidation password stored in Web Cache and the password stored in the Portal repository are not the same.

To resolve this issue:

1. Reset the Oracle Web Cache invalidator password in the Administration repository:

   1. Log in to Enterprise Manager in the domain where Web Cache is running:

      http://administration_server_host:administration_server_port/em
      

   2. From the navigation section on the left, open "Web Tier" then click on the Web Cache instance name.

   3. Find the drop-down menu on the right-hand side of the page under the Web Cache instance name, then select Administration > Password from the menu.

   4. Specify a new invalidation password.

   5. Restart Oracle Web Cache.

2. Reset the Oracle Web Cache invalidator password in the Oracle Portal repository:

   1. Log in to Enterprise Manager in the domain where Oracle Portal is running:

      http://administration_server_host:administration_server_port/em
      

   2. From the navigation section on the left, open "Portal" then click on the Oracle Portal Managed Server name.

   3. Find the drop-down menu on the right-hand side of the page under the Oracle Portal instance name, then select Settings > Wire Configuration from the menu.

   4. Specify a new invalidation password - the same password you specified in the Administration repository.

      Note:

      the "Invalidation User" user name should be same as the user name used on the Oracle Web Cache side.

   5. Click Apply.

      There is a known issue at this point - refer to "Resolving JDBC Errors in Oracle Reports and Oracle Portal" in the Oracle Fusion Middleware Patching Guide for more information.

   6. Delete the Oracle Portal File Cache in the ORACLE_INSTANCE/portal/cache directory.

   7. Restart Oracle Web Cache and the Oracle Portal Managed Server.

2.2.8.4 Applications Generate javax.xml.bind.JAXBException Runtime Errors After Installing 11g Release 1 (11.1.1.4.0) Patch Set

If any of the applications you deployed on Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or 11g Release 1 (11.1.1.3.0) include EclipseLink-JAXB classes that have no-arg constructors missing, then after you install 11g Release 1 (11.1.1.4.0), the application might generate the following exceptions during runtime:

javax.xml.bind.JAXBException

To avoid this error:

1. Modify the classes and add default no-arg constructors where necessary.

2. Compile and redeploy your project to the newly patched Oracle Fusion Middleware 11g Release 1 (11.1.1.4.0) domain.

Below is an example of a typical no-arg constructor:

public class PriceQuote implements Serializable
{
   // Make sure you have constructor with no arguments
   public PriceQuote() }
   }
}

2.3.1.1 SOAINFRA Schema Contains Invalid Objects in 11g Release 1 (11.1.1.6.0)

When the 11g Release 1 (11.1.1.6.0) version of the prefix_SOAINFRA schema is created either by running RCU or the Patch Set Assistant, there are still some invalid objects that exist within the SOA schema.

To work around this issue, compile the prefix_SOAINFRA schema. For example, if the SOA schema user on your system is DEV_SOAINFRA:

exec dbms_utility.compile_schema('DEV_SOAINFRA')

If you choose not to run this command to make the objects valid, the objects will also become valid once they are accessed during runtime.

2.3.1.2 Harmless Exception Seen for Oracle SOA Suite with WebSphere Application Server

When running Oracle SOA Suite on IBM WebSphere application server, the following exception is seen after logging in to Fusion Middleware Control, expanding Application Deployments on the left side and then clicking on any of the applications under it:

[date_and_time] 0000003f OHWHelpProvid E   unable to create global
configuration
[date_and_time] 00000044 OHWHelpProvid E   critical error in OHW
configuration
 
oracle.help.web.config.parser.ConfigParseException: error finding
configuration file at:
        at oracle.help.web.config.parser.OHWParser._openConnection(Unknown
Source)
        at oracle.help.web.config.parser.OHWParser.getGlobalConfiguration(Unknown Source)
        at oracle.help.web.rich.helpProvider.OHWHelpProvider.getHelpTopic(Unknown Source)
.
.
.

This exception is harmless and can be safely ignored.

2.3.2.1 Oracle Internet Directory Server Does Not Listen on SSL Port

If the machine on which Oracle Internet Directory is installed is not configured as a dual stack (IPv4/IPv6) host and the Oracle Internet Directory server is configured to listen on privileged ports, then the Oracle Internet Directory server does not listen on SSL ports.

To work around this issue, do one of the following:

• Enable IPv6 on the machine.

• If pure IPv4/IPv6 addresses are needed, add host=ipv4_ip_address or host=ipv6_ip_address for oidmon parameters in the INSTANCE_HOME/config/OPMN/opmn/opmn.xml file. For example:

  <data id="start-cmdline-opts" value="connect=$DB_CONNECT_STR opmnuid=true
     host=ipv4_or_ipv6_ip_address start"/>
  <data id="stop-cmdline-opts" value="connect=$DB_CONNECT_STR opmnuid=true
     host=ipv4_or_ipv6_ip_address stop"/>
  

2.3.2.2 Metrics for Oracle Identity Management Components may not be Correctly Displayed in Enterprise Manager

When Oracle Identity Management servers are configured on IPv4/IPv6 dual-stack hosts in 11g Release 1 (11.1.1.7.0), the following problems may occur in Enterprise Manager:

• Metrics for Oracle Identity Management components may not be displayed correctly.

• Links to Oracle Directory Services Manager (ODSM) may not work.

To work around this issue, add an alias for the IPv6 address in the /etc/hosts file on your system:

IPv6_host_address host.domain host

For example:

fdc4:82c2:9c80:d47a::3:58 examplehost.exampledomain.com examplehost

2.3.2.3 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 nodemanager.properties 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.

2.3.2.4 Configuring Oracle Internet Directory 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 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;/
   

3. Change the following line:

   ,object_owner => 'ODS'
   

   to:

   ,object_owner => '%'
   

2.3.2.5 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 ( # )

INST-07037: Administrator Password field value contains one or more
invalid characters or the value is not in proper format.

2.3.2.6 Harmless 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:11.1.1.1.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.

2.3.3.1 Log Messages Appearing on Console During Oracle Identity Manager Schema Creation

During the creation of the Oracle Identity Manager (OIM) schema, some log messages will appear in the RCU console window. These log messages are specific to Quartz, which is used by Oracle Identity Manager, and can be safely ignored.

If there are any errors encountered during the loading of this Quartz-specific data, the errors will be written to the RCU log files. Refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information about the RCU log files.

2.3.4.1 Starting the Configuration Wizard From a New Window

When you start the Configuration Wizard from a terminal window, make sure that it is a new terminal window to ensure that there are no environment variables set to incorrect locations from a previous configuration or installation session.

2.3.4.2 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.3.5.1 Increasing the Tablespace Size for the MDS Schema

On Oracle databases, a default tablespace size of 1024MB is created for the MDS schema. If you need to increase the size of this tablespace, do the following:

1. Log in to the Database Control page. For example:

   https://db_host:db_port/em/
   

2. Select the Server tab.

3. In the "Storage" section, select Datafiles.

4. Select the row of the datafile corresponding to the schema you want to edit, then click Edit. In the case of the MDS schema, the datafile name should be prefix_mds.dbf.

5. On the "Edit Datafile" page, increase the size of the tablespace.

2.3.5.2 Schemas Are Not Visible After Upgrade of Oracle Identity Management

After upgrading Oracle Identity Management from Release 10g (10.1.4.3) 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.3.5.3 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.3.6.1 Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd

Oracle SOA Suite, Oracle WebCenter Portal, and Application Developer all contain the pack.sh and unpack.sh scripts in their respective ORACLE_HOME/common/bin directories.

The pack.sh script is 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.sh script is used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote system.

Both pack.sh and unpack.sh will fail if any installed products are missing from the system where you are running these scripts.

2.3.6.2 Running unpack.sh or unpack.cmd on a Different Host

If you are running the unpack.sh 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 = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

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

Host 1:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/SOA_Home

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

Host 1:
MW_HOME = /user/home/Middleware
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

@ Host 2:
MW_HOME = /user/home/MWHome
ORACLE_HOME =/user/home/Middleware/Oracle_SOA1

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.3.6.3 Starting Managed Servers on Remote System After Packing and Unpacking Domain

After you unpack a domain on a remote system using the unpack command, complete the following steps:

1. Start Node Manager on the remote system. This action creates a nodemanager.properties file on your system in the MW_HOME/wlserver_10.3/common/nodemanager directory.

2. Stop Node Manager.

3. Open the nodemanager.properties file in a text editor and set the StartScriptEnabled property to true.

4. Start the Node Manager on the remote system before starting the Managed Server on the remote system through the Oracle WebLogic Administration Console.

2.3.7.1 Extend Domain and Expand Cluster Scenarios with Remote Systems

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

2.3.7.2 Unable to Extend an Existing Domain by Selecting Only Oracle Directory Integration Platform Without Cluster

Selecting only Oracle Directory Integration Platform without cluster in a session followed by creating cluster and extending domain on the same system fails.

In this domain configuration scenario, ensure that you install and configure Oracle Directory Services Manager on the same system where you extending the domain to configure Oracle Directory Integration Platform.

2.3.7.3 Expand Cluster Requires Changes to the emd.properties 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/emd.properties file contains the values shown below:

EMD_URL=http://localhost.localdomain:port/emd/main

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:

EMD_URL=http://examplehost.exampledomain.com:5160/emd/main

2.6.2.1 Deinstalling Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11g Release 1 WebGates for Oracle Access Manager

You should always use the instructions provided in this section for removing the Oracle HTTP Server, Oracle Traffic Director, and Oracle iPlanet 11.1.1.7.0 WebGates for Oracle Access Manager. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this section will ensure that the software is properly removed.

To deinstall the WebGate agent, do the following:

1. Go to the MW_HOME/oracle_common/oui/bin directory.

2. Run the following command:

   On UNIX: ./runInstaller -deinstall

   On Windows: setup.exe -deinstall -jreLoc JRE_LOCATION

   Ensure that you specify the absolute path to your JRE_LOCATION; relative paths are not supported.

After the deinstaller starts, the Welcome screen is displayed. Proceed with the deinstallation by referring to Section 2.6.2.1.1 for deinstalling 11g Release 1 WebGate agents for Oracle Access Manager.

cd /home/Oracle/Middleware
rm -rf oracle_common