Oracle® Fusion Middleware Release Notes 11g Release 1 (11.1.1) for HP-UX PA-RISC (64-Bit) E14775-21 |
|
![]() Previous |
![]() Next |
This chapter describes issues associated with Oracle Fusion Middleware installation, patching, and configuration. It includes the following topics:
This section describes installation issue and workarounds. It includes the following topics:
Section 2.1.1, "Installing Oracle SOA Suite on a Dual Stack Host with IPv4"
Section 2.1.2, "Installing Oracle SOA Suite Release 11.1.1.3.0 in a Turkish Environment"
Section 2.1.3, "Installing Oracle Service Registry in the Same Domain as Oracle SOA Suite"
Section 2.1.7, "Problems Installing in Thai and Turkish Locales"
Section 2.1.9, "Setting the nls_length_semantics Parameter in your Database"
Section 2.1.10, "Proper Deinstallation for Reinstallation in the Event of a Failed Installation"
Section 2.1.11, "Running irca.sh or irca.bat Against an Oracle 10g Database"
Section 2.1.12, "Installing the SOAINFRA Schema with DBA Permissions"
Section 2.1.13, "Deinstallation Does Not Remove WebLogic Domains"
Section 2.1.15, "Response File is Missing the MIDDLEWARE_HOME Entry"
Section 2.1.16, "Ignore Error Message CheckPatchApplicableOnCurrentPlatform Failed"
Section 2.1.20, "Starting Managed Servers on Remote Machines After Packing and Unpacking Domain"
Section 2.1.22, "WebLogic Administration Server Fails to Start Due to Memory Issues"
Section 2.1.23, "Installation Fails on 64-bit Operating Systems with 32-bit JDKs"
Section 2.1.24, "Do Not Install Patch 9824531 During the Setup of OIM and OAM Integration"
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.
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.
When installing Oracle Service Registry 11g in the same Weblogic Domain as Oracle SOA Suite 11g Release 11.1.1.2.0 or Release 11.1.1.3.0, you may see the following error message on the WebLogic Server console when Oracle Service Registry is starting up:
java.lang.LinkageError: loader constraint violation in interface itable initialization:....
To work around this issue:
Make sure Oracle Service Registry is installed on a different Managed Server from Oracle SOA Suite.
Download patch 9499508 and follow the instructions in the README file included with the patch:
Go to My Oracle Support.
http://support.oracle.com
Click on the Patches & Updates tab.
In the Patch Search area, search for patch 9499508.
Download the patch.
Edit the setDomainEnv.sh
file and, for Oracle Service Registry Server, remove fabric.jar
from classpath:
if [ "${SERVER_NAME}" != "osr_server1" ] ; then POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" else POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" fi
When installing Oracle Service Registry 11g in the same Weblogic Domain as Oracle SOA Suite 11g Release 11.1.1.3.0, you may see the following error message when accessing the Oracle Service Registry console:
ClassCastException java.lang.ClassCastException:org.systinet.uddi.client.serialization.UDDIFaultSerializer
To work around this error, edit the setDomainEnv.sh
file and remove oracle.soa.fabric.jar
from the classpath when running the Oracle Service Registry Managed Server. To do this:
Make a backup of the MW_HOME
/user_projects/domains/
soa_domain_name
/bin/setDomainEnv.sh
file.
Edit the setDomainEnv.sh
file and replace the following line:
POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}"
with the following:
if [ "${SERVER_NAME}" != "<your_osr_server_name>" ] ; then POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" else POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" fi
Restart the Oracle Service Registry Managed Server.
If you have multiple Oracle Service Registry Managed Servers in the domain, each Managed Server must be added to the condition. For example, if you have two Oracle Service Registry Managed Servers named WLS_OSR1
and WLS_OSR2
:
case "$SERVER_NAME" in . 'WLS_OSR1') . echo "Setting WLS_OSR1 CLASSPATH..." POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" exit;; . 'WLS_OSR2') . echo "Setting WLS_OSR2 CLASSPATH..." POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" exit;; . *) . echo "Setting default SOA CLASSPATH..." POST_CLASSPATH="${SOA_ORACLE_HOME}/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar ${CLASSPATHSEP}${SOA_ORACLE_HOME}/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar ${CLASSPATHSEP}${POST_CLASSPATH}" exit;; . esac
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
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.
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:
http://download.oracle.com/docs/cd/E10316_01/owc.htm
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:
Open the stellent_dir
/custom/Folders_g/folders_environment.cfg
(on UNIX) or stellent_dir
\custom\Folders_g\folders_environment.cfg
(on Windows) file.
Verify that the CollectionReadOnlyMarkedFolders
value is set to true
:
CollectionReadOnlyMarkedFolders=true
Restart the Content Server if you changed the folders_environment.cfg
file.
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.
Oracle Fusion Middleware only supports schemas in a byte-mode database. The nls_length_semantics
initialization parameter on the database where the schemas reside must be set to BYTE
; setting this parameter to CHAR
is not supported.
To check the values of this parameter using SQL*Plus, you can use the show parameters
command:
prompt> sqlplus "sys/password as sysdba"SQL> show parameters nls_length_semantics
Replace password
with the actual password for the SYS user.
Alternatively, you can check the values by querying the V$PARAMETER
view:
prompt> sqlplus "sys/password as sysdba"SQL> select name,value from v$parameter;
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 ORACLE_HOME
/oui/bin
directory.
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 DOMAIN_HOME
/servers
directory:
This procedure will enable you to reinstall the software to the same location, using the same managed server names.
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 java.lang.UnsupportedClassVersionError
error.
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;
Replace 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 install
time_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.
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:
MIDDLEWARE_HOME=/home/Oracle/Middleware
On applying OPatch during Web Tier installation, the following error messages are seen in OraInventory log file:
Prerequisite check "CheckPatchApplicableOnCurrentPlatform" failed. OPatch failed with error code 74
This error occurs as HP-UX PA-RISC and HP-UX Itanium patches are available in the same folder, and the OPatch executes all the patches in that folder to overcome a bug that returns the platform name.
The workaround is to ignore the error messages.
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 on UNIX operating systems. On Windows operating systems, 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.
You may see some benign error messages in installation log files, such as the following, after you patch an Oracle Identity Management 11.1.1.2.0 installation to 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 /scratch/aime1/Oracle/Middleware/oracle_ps2/install/root.log': Operation not permitted
/bin/chmod: changing permissions of /scratch/aime1/Oracle/Middleware/oracle_ps2/bin/nmb': Operation not permitted
/bin/chmod: changing permissions of /scratch/aime1/Oracle/Middleware/oracle_ps2/bin/nmhs': Operation not permitted
/bin/chmod: changing permissions of /scratch/aime1/Oracle/Middleware/oracle_ps2/bin/nmo': Operation not permitted
inventoryLocation: /scratch/aime1/oraInventory
Mode:init
Such messages can be ignored.
Selecting only Oracle Directory Integration Platform without cluster in a session followed by creating cluster and extending domain on the same machine fails.
In this domain configuration scenario, ensure that you install and configure Oracle Directory Services Manager on the same machine where you extending the domain to configure Oracle Directory Integration Platform.
After you unpack a domain on a remote machine using the unpack
command, complete the following steps:
Start Node Manager on the remote machine. This action creates a nodemanager.properties file on your machine in the <MW_HOME>/wlserver_10.3/common/nodemanager/
directory (on UNIX). On Windows, this file is created in the <MW_HOME>\wlserver_10.3\common\nodemanager\
the directory.
Stop Node Manager.
Open the nodemanager.properties file in a text editor and set the StartScriptEnabled
property to true
.
Start the Node Manager on the remote machine before starting the Managed Server on the remote machine through the Oracle WebLogic Administration Console.
When extending a 11.1.1.3.0 (patched) domain on a remote machine, you may see a Null Pointer exception message, such as the following, in the Managed Server log files after installation:
0000IW5hUxgDc_Y5HrDCif1Bm1sl000000,0] [APP: DMS Application#11.1.1.1.0] initialization error[[java.lang.NullPointerException at java.io.File.<init>(File.java:222) at oracle.dms.impl.util.AdmlLocator.<init>(AdmlLocator.java:59) at oracle.dms.app.DmsSpy.init(DmsSpy.java:86) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
To work around this issue, do the following:
Stop the instance running on the second machine.
Stop the Managed Server on the second machine.
Stop the instance running on the first machine.
Stop Managed Servers on the first machine.
Stop the Administration Server on the first machine.
Start the instance, the Administration Server, and then Managed Servers on the first machine manually from the command line.
Start the instance and then Managed Servers on the second machine manually from the command line.
For information about starting and stopping Oracle Fusion Middleware, see the "Starting and Stopping Oracle Fusion Middleware" chapter in the Oracle Fusion Middleware Administrator's Guide.
On Windows 32-bit operating systems, the WebLogic Administration Server may fail to start, as it cannot allocate sufficient memory despite the availability of free memory.
As a workaround, complete the following steps:
Open the setSOADomainEnv.cmd
file, located in your <Domain_Home>\bin
directory, in a text editor.
Update the PORT_MEM_ARGS
entry as follows:
set PORT_MEM_ARGS=-Xms512m -Xmx1024m
Save the file and close.
To work around this issue:
Append -jreLoc
and the 32-bit JDK path to the install command.
In UNIX/Linux environments:
INSTALL_PATH/runInstaller -jreLoc 32BIT_JAVA_HOME
In Windows environments:
INSTALL_PATH\setup.exe -jreLoc 32BIT_JAVA_HOME
In the Oracle Fusion Middleware Installation Guide for Oracle Identity Management, Step 10 in the section titled "Setting Up Integration Between OIM and OAM Using the Domain Agent" instructs users about installing Patch 9824531.
Do not install this patch.
Note that you must download and install the following patches instead of Patch 9824531:
Patch 9674375
Patch 9817469
Patch 9882205
You can download these patches from My Oracle Support.
This section describes patching issues and their workarounds. It includes the following topics:
Section 2.2.1, "Deploying WebCenterWorklistDetailApp.ear for WebCenter Spaces Workflows"
Section 2.2.3, "Some WebCenter Applications Show Old Version Number"
Section 2.2.4, ""Patch Already Installed" Warning Mesage in Log File"
Section 2.2.7, "Updating Oracle WebCenter Wiki and Blog Server Files"
Section 2.2.8, "OID AND DIP Resource Usage Graph Has No Data"
Section 2.2.10, "Redeploy System Components to Ensure Proper Deinstallation"
Section 2.2.11, "Manual Steps for Migrating Oracle UMS and Oracle MDS"
Section 2.2.13, "Setting Execute Permissions for emctl When Migrating System Components"
After running the Oracle Fusion Middleware 11.1.1.3.0 Patch Set Installer, you must redeploy WebCenterWorklistDetailApp.ear
. This file is located at the following path in your Oracle SOA Suite 11.1.1.2.0 installation path: SOA_ORACLE_HOME
/webcenter/applications/WebCenterWorklistDetailApp.ear
.
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:
Login to the Administration Console.
In the "Connection Pools" tab, add the following property in the "Properties" section for the mds-owsm
and mds-soa
data sources:
ReportDateTimeTypes=false
After applying the patch for Oracle WebCenter, some applications still show the version number from previous releases.
There is no work around for this issue.
In a scenario where you have a product that is already patched to version 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 install
timestamp
.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.
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:
Connect to your databsae as the SOA schema user.
Drop the BPM_CUBE_ROLE_FK1
constraint by executing the following:
ALTER TABLE BPM_CUBE_ROLE DROP CONSTRAINT BPM_CUBE_ROLE_FK1;
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;
Restart the Oracle SOA Managed Server.
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:
Connect to your databsae as the SOA schema user.
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;
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;
Restart the Oracle SOA Managed Server.
After applying the Oracle Fusion Middleware 11.1.1.3.0 patch set, to work with Oracle WebCenter Wiki and Blog Server, you must copy the updated wiki and blog files to the applications
directory where all applications created in your WebCenter domain reside.
To copy updated wiki and blog files:
Back up your wiki configuration file, application_config.script
located at:
MW_HOME
/user_projects/applications/domain_name
/owc_wiki/WEB-INF/classes/application_config.script
Where, domain_name
refers to your WebCenter domain.
Copy files from Oracle WebCenter Wiki and Blog Server's deployment directory in ORACLE_HOME
to the DOMAIN_HOME
directory of Oracle WebCenter. That is:
Copy files from: ORACLE_HOME
/wikiserver/owc_wiki
Copy files to: MW_HOME
/user_projects/applications/
domain_name
For example, you can use the following command:
cp -rORACLE_HOME
/wikiserver/owc_wikiMW_HOME
/user_projects/applications/domain_name
/.
In Enterprise Manager, the resource usage graphs about memory and CPU display zero values for OID and DIP.
To work around this issue, perform the following steps:
Download and apply the one-off patch for Bug 9592163.
Stop and start emagent
using the following command:
$INSTANCE_HOME
/bin/opmnctl (stop)startproc process-type=EMAGENT
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.
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 in "Redeploying System Components for Extend Domain Scenarios" in the Oracle Fusion Middleware Patching Guide.
If you do not redeploy your system components, you will encounter problems when you attempt to remove them.
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.
When you are using the Patch Assistant migration scripts to migrate Oracle Identity Federation from Release 11.1.1.1.0 to Release 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.
When you migrate any Release 11.1.1.1.0 system component to Release 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.
This section describes configuration issues and their workarounds. It includes the following topics:
Section 2.3.1, "Extend Domain and Expand Cluster Scenarios with Remote Machines"
Section 2.3.2, "Specify Security Updates Screen Does Not Appear in the Configuration Wizard"
Section 2.3.3, "Log Messages Appearing on Console During Oracle Identity Management Schema Creation"
Section 2.3.4, "Configuring Oracle Identity Management When WebLogic Node Manager is Running"
Section 2.3.6, "Password Requirements for Oracle Internet Directory Administrator"
Section 2.3.7, "Changing the Listen Address of a Managed Server"
Section 2.3.8, "Expand Cluster Requires Changes to the emd.properties File"
Section 2.3.9, "Domain Extension Overwrites JDBC Data Source Name"
Section 2.3.10, "Schemas Are Not Visible After Upgrade of Oracle Identity Management"
Section 2.3.12, "Error Message When Configuring Oracle Identity Federation"
Section 2.3.13, "Ensure There Are No Missing Products When Using unpack.sh or unpack.cmd"
Section 2.3.14, "Running unpack.sh or unpack.cmd on a Different Host"
Section 2.3.15, "Rerouting to Original URL After SSO Authentication in Firefox and Safari Browsers"
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 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.
During the creation of the Oracle Identity Management (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 Management, and can be safely ignored.
If there are any errors encoutered 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 informaiton about the RCU log files.
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:
Set the 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).
In the ORACLE_HOME
/ldap/datasecurity/dbv_oid_command_rules.sql
(on UNIX operating systems) or ORACLE_HOME
\ldap\datasecurity\dbv_oid_command_rules.sql
(on Windows operating systems) file, find the following code:
/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'
to:
,object_owner => '%'
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. |
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 INSTANCE_HOME
/EMAGENT/EMAGENT/sysman/config/emd.properties
(on UNIX) or INSTANCE_HOME
\EMAGENT\EMAGENT\sysman\config\emd.properties
(on Windows) 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://myhost.mydomain.mycompany.com:5160/emd/main
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 (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.
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: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.
Oracle SOA Suite, Oracle WebCenter, and Application Developer all contain the pack.sh
and unpack.sh
(on UNIX systems) or pack.cmd
and unpack.cmd
(on Window systems) commands in their respective ORACLE_HOME
/common/bin
(on UNIX systems) or ORACLE_HOME
\common\bin
(on Windows systems) directories.
The pack.sh
and pack.cmd
scripts are used to create a template archive (.jar
) file that contains a snapshot of either an entire domain or a subset of a domain. The unpack.sh
and unpack.cmd
scripts are used to create a full domain or a subset of a domain used for a Managed Server domain directory on a remote machine.
The unpack.sh
and unpack.cmd
commands will fail if any installed products are missing from the machine where you are running the unpack.sh
or unpack.cmd
command.
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 = /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
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 and Safari browsers when the initial request comes from Oracle HTTP Server.
The work arounds are to either use the Internet Explorer browser, or manually modify the INSTANCE_HOME
/config/OHS/instance_name/httpd.conf
file and change the ServerName
entry to include the port number. For example:
ServerName myhost.mydomain.com
should be changed to:
ServerName myhost.mydomain.com:port
Replace 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.
Cloning is successfully done on HP-UX PA-RISC (64-Bit) and HP-UX Itanium platforms. However, the installation logs show the chmod:invalid option
message.
Workaround
Ignore the message because cloning completes successfully.
This section describes documentation errata. It includes the following topics:
Section 2.5.1, "Error in the Oracle Web Tier Installation Guides"
Section 2.5.2, "Missing Installer Startup Instructions for a 32-bit JDK on a 64-bit Platform"
Section 2.5.3, "Missing Information in the Oracle Web Tier Installation Guides"
Section 2.5.4, "Missing Post-Installation Steps in the Oracle WebCenter Installation Guide"
Section 2.5.5, "Updating OIM Configuration to Use Oracle HTTP Server 10g WebGate"
In the Oracle Fusion Middleware Installation Guide for Oracle Web Tier and Oracle Fusion Middleware Quick Installation Guide for Oracle Web Tier, there is an error in the section "Installing 32-bit Oracle Web Tier on a 64-bit Operating System".
In Step 2c, The following is incorrect:
#!/bin/sh exec /usr/bin/gcc.orig -m32 -static-libgcc -B/usr/lib/gcc/i586-suse-linux/2.95.3/ $*
There is a space missing after -B
. The correct text is:
#!/bin/sh exec /usr/bin/gcc.orig -m32 -static-libgcc -B /usr/lib/gcc/i586-suse-linux/2.95.3/ $*
The following information is missing from the installer startup instructions in the quick installation guides for Oracle SOA Suite and Oracle WebCenter:
If you are installing your product on a 64-bit UNIX or Windows operating system with a 32-bit JDK, you must specify the JRE_LOCATION
using the -jreLoc
option from the command line. The option to provide your JRE_LOCATION
at the prompt is not supported in such cases, and the installer will not start.
This section contains documentation errata in the Oracle Web Tier installation guides. The following topics are covered:
Section 2.5.3.1, "Starting Node Manager When Registering Oracle Web Tier with a WebLogic Domain"
Section 2.5.3.2, "Using Oracle Enterprise Manager for GUI-Based Administration"
The following information is missing from the Oracle Fusion Middleware Installation Guide for Oracle Web Tier:
If you are registering your Oracle Web Tier instance with an existing WebLogic Domain, you must start Node Manager as described below:
On UNIX operating systems, run the ORACLE_HOME
/common/bin/setNMProps.sh
script.
On Windows operating systems, run the ORACLE_HOME
\common\bin\setNMProps.cmd
script.
This script appends the required properties to the nodemanager.properties
file. These properties can also be appended manually, or provided as command-line arguments.
Note: TheStartScriptEnabled=true property is required for Managed Servers to receive proper classpath and command arguments. |
On UNIX operating systems, start Node Manager by running the MWHome
/wlserver_10.3/server/bin/startNodeManager.sh
script.
On Windows operating systems, start Node Manager by running the MWHome
\wlserver_10.3\server\bin\startNodeManager.cmd
script.
For more information about Node Manager, refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
The following information is missing from the Oracle Fusion Middleware Installation Guide for Oracle Web Tier:
Oracle Web Tier can be installed and configured in two ways:
Stand-alone.
Oracle Web Tier is configured without a WebLogic Domain and administered from the command line.
Using Oracle Enterprise Manager Fusion Middleware Control.
This approach requires Oracle Web Tier to be associated with a Weblogic Domain.
Follow the instructions below to associate Oracle Web Tier with a WebLogic Domain:
Create a WebLogic Domain.
Oracle Web Tier requires an existing WebLogic Domain; you cannot create a WebLogic Domain during the Oracle Web Tier installation.
Read "Before you Begin" in Oracle Fusion Middleware Installation Planning Guide for information about whether or not you need a database and database schemas, and also for information about installing Oracle WebLogic Server.
After you have installed Oracle WebLogic Server, install (do not configure) any Oracle Fusion Middleware product.
Installation of an Oracle Fusion Middleware product creates the Oracle Common home directory (MW_HOME
/oracle_common
on UNIX operating systems, or MW_HOME
\oracle_common
on Windows operating systems). This directory contains the domain templates for Enterprise Manager and Java Required Files (JRF).
Run the Configuration Wizard from the Oracle Common home directory (config.sh
on UNIX operating systems or config.cmd
on Windows operating systems).
On the Select Domain Source screen, select the Oracle Enterprise Manager and Oracle JRF templates associated with the oracle_common
directory. The Oracle JRF template is selected automatically when the Oracle Enterprise Manager template is selected.
Install Oracle Web Tier as described in Oracle Fusion Middleware Installation Guide for Oracle Web Tier.
On the Configure Components screen, select Associate Selected Components with WebLogic Domain.
On the Specify WebLogic Domain screen, provide the credentials to the WebLogic Domain you just created.
After the installation is complete, start the Administration Server in the domain, and then verify that the Oracle Web Tier components are listed by accessing the following URL:
http://host:port/em
The following information about how to start Managed Servers from the Administration Console is missing from the Oracle Fusion Middleware Installation Guide for Oracle WebCenter:
In order to start a managed server from the Administration Console, you must first create a machine, then associate the managed server with that machine:
Login to the Administration Console.
Navigate to Environment > Machines.
Click New.
Enter a machine name (for example, Machine-WC
).
In the Administration Console, navigate to Environment > Servers and select the managed server for which you want to associate this machine (Machine-WC
). Use the drop-down list to associate the managed server with the machine.
Note: This procedure only works if the managed servers are shut down. If the managed servers are up and running, then no values will appear in the drop-down list. |
After this procedure, the managed server will start successfully and be accessible.
Step 4 in the Section 22.8 "Optional: Updating Oracle Identity Manager Configuration" in the chapter "Migrating from Domain Agent to Oracle HTTP Server 10g Webgate for OAM" requires you to update the OIM Configuration when the OAM URL or agent profile changes. This section is in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management.
To update Oracle Identity Manager configuration, complete the following steps:
Export the oim-config.xml
file from metadata by running <IDM_Home>/server/bin/weblogicExportMetadata.sh
(on UNIX), and export the file - /db/oim-config.xml
. On Windows operating systems, you can use the weblogicExportMetadata.bat file located in the same directory.
Update the file to use Oracle HTTP Server 10g Webgate by updating following element under the <ssoConfig>
tag:
<webgateType>javaWebgate</webgateType>
to <webgateType>ohsWebgate10g</webgateType>
Import oim-config.xml
back to metadata by running <IDM_Home>/server/bin/weblogicImportMetadata.sh
on UNIX. On Windows, use the weblogicImportMetadata.bat
located in the same directory.
Log in to Oracle Enterprise Manager using your WebLogic Server administrator credentials.
Click Identity and access > oim > oim(version). Right-click and select System MBean Browser. The System MBean Browser page is displayed.
Under Application Defined MBeans, select oracle.iam
> Server:oim_server1
> Application: oim
> XMLConfig
> config
.
Replace the front-end URL with the URL of Oracle HTTP Server. This should be the same Oracle HTTP Server that was used before installing Oracle HTTP Server 10g Webgate for Oracle Access Manager. Complete the following steps:
Under XMLConfig
MBean, move to XMLConfig.DiscoveryConfig
.
Update OimFrontEndURL with the URL of Oracle HTTP Server.
Click Apply.
Restart the OIM server.
Steps to perform logout configuration after updating the OIM Server Configuration are missing from the Oracle Fusion Middleware Installation Guide for Oracle Identity Management.
You must perform logout configuration after updating the OIM Server configuration, as described in the Section 22.6 "Updating OIM Server Configuration" in the chapter "Migrating from Domain Agent to Oracle HTTP Server 10g Webgate for OAM".
Note: Ensure that you have set up integration between Oracle Identity Manager and Oracle Access Manager, as described in the topic "Integration Between OIM and OAM" in the Oracle Fusion Middleware Installation Guide for Oracle Identity Management. |
After updating OIM Server configuration, you must perform logout configuration as follows:
Copy the logout.html
file from the <IDM_HOME>/oam/server/oamsso
directory to the <10gWebgateInstallation>/access/oamsso
directory.
Edit the SERVER_LOGOUTURL
variable in the logout.html
file to point to the host and port of the Oracle Access Manager Server. Follow the instructions in the logout.html
file.
If the http.conf
file of the web server includes the following entries, remove the entries from the http.conf
file:
<LocationMatch "/oamsso/*"> Satisfy any </LocationMatch>