2 Install and Configure

This chapter describes issues that are related to Oracle Fusion Middleware product installation and configuration.

The following topics are covered in this chapter:

Issues Related to Product Installation

This section contains the following topics:

Checking for Available Software Patches and Product Information

Before you install any Oracle Fusion Middleware product, it is good practice to review the product information available on My Oracle Support:

http://support.oracle.com/

When you register for My Oracle Support, you have easy access to important information about available patches and other important Oracle Fusion Middleware product information.

Note:

For example, you can access the following generic install jar file names and quickstart jar file names:
  • fmw_12.2.1.4.0_idm.jar

  • fmw_12.2.1.4.0_idmquickstart.jar

  • fmw_12.2.1.4.0_idmquickstart2.jar

Downloading and Applying Required Patches

After you install Oracle Fusion Middleware 12c (12.2.1.4.0), there might be cases where additional patches are required to address specific known issues.

Patches for Oracle Fusion Middleware 12c are available from My Oracle Support:

http://support.oracle.com

To download a patch:

  1. Log in to My Oracle Support.

  2. Click the Patches & Updates tab.

  3. In the Patch Search area, select Patch Name or Number.

  4. Enter the patch number.

  5. Click Search. The Patch Search Results page appears.

  6. Download and install the patch.

Updated Database Client Software Patch Identification Numbers

The Oracle Fusion Middleware 12c (12.2.1.4.0) installation includes an update to the database client software that includes the database patch set 12.1.0.2.190716.

When you execute the command opatch lsinventory, the patch identification number for this update appears as 29494060 on Linux/Unix and 30220086 on Microsoft Windows.

Mnemonics for Buttons are Not Read Using JAWS 2019

For UA and Install screens, in JAWS 2019, short cut keys (mnemonics) to carry out some functions are not echoed while typing.

For example, in JAWS 2019, you cannot hear "ALT+N" shortcut key to activate the Next button.

As a workaround, you can use JAWS 2018 to carry out these functions.

Issues Related to Product Configuration

This section contains the following topic:

A Partition with Japanese Name Cannot Be Created from Fusion Middleware Control

A partition with a Japanese name cannot be created by using Fusion Middleware Control.

As a workaround, you can either use Fusion Middleware Control to create a partition that uses an English name or use the WebLogic Server Administration Console to create a partition with a Japanese name.

Issues Related to Product Installation and Configuration Documentation

This section contains the following topics:

Registering Node Manager as a Windows Service

To register Node Manager as a Windows Service serving either one of the following:

  • A standalone OHS domain

  • A domain with a collocated ODI agent

Do the following after you have created the domain:

  1. Set the JAVA_OPTIONS environment variable so that it points to the proper Oracle home and Domain home directories.
    set JAVA_OPTIONS=-Dohs.product.home=ORACLE_HOME -Dweblogic.RootDirectory=DOMAIN_HOME
    

    For example:

    set JAVA_OPTIONS=-Dohs.product.home=C:\Oracle\product\OHS\OracleHome -Dweblogic.RootDirectory=C:\Oracle\config\domains\OHSDomain
    
  2. Go to the Domain home directory and run the following command:
    installNodeMgrSvc.cmd

Additional Domain Configuration

Use the configuration wizard to update the newly created domain.

  1. Restart the configuration wizard by issuing the command: IGD_ORACLE_HOME/oracle_common/common/bin/config.sh

    The configuration screen is displayed.

  2. In the Configuration Type screen, select Update an existing domain.
  3. In the Domain Location field, specify the Domain home directory (IGD_ASERVER_HOME).
  4. Click Next.
  5. On the Templates screen, select Update Domain Using Custom Template.
  6. In the Template location field, specify: IGD_ORACLE_HOME/soa/common/templates/wls/oracle.soa.classic.domain_template.jar
  7. Click Next.
  8. On the Gridlink Oracle RAC Component Schema Page, click Next.
  9. On the JDBC Component Test Schema Test screen, click Next.
  10. On the Advanced Configuration screen, click Next.
  11. On the Configuration summary screen, click Next.
  12. Once the domain is extended, click Next on the Configuration Progress screen.
  13. Click Finish on the End of Configuration screen.

Compatibility of Oracle Business Intelligence with Oracle Fusion Middleware

You must install Oracle Business Intelligence 12c (12.2.1.4.0) with Oracle Fusion Middleware 12.2.1.3.0.

You cannot install Oracle Business Intelligence 12.2.1.4.0 in the same Oracle home directory as Oracle Fusion Middleware 12.2.1.4.0.

Product Installation and Configuration on Autonomous Transaction Processing-Dedicated Database

This section includes the following topics:

ATP-D Support for Fusion Middleware Products

ATP-D database is not supported for Oracle Data Integrator and Oracle Enterprise Data Quality products.

SYS DBA Privileges Warning After Applying Patches

Bug Number: 31690699

After applying the patches 23732643 and 23726506 on Oracle Home, when you start the RCU on ATP-D database, you receive the SYS DBA privileges warning on the Database Connection Details screen. You must click Ignore and continue with the schema creation. For more information, see Troubleshooting Tips for Schema Creation on Autonomous Transaction Processing-Dedicated Database

UCM Server Logs

The error messages in the UCM_server logs are:

  • general exception:

    java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges.

  • data exception:

    Caused by: Error : 1450, Position : 0, Sql = CREATE TABLE Subscription

  • data exception:

    Caused by: Error : 942, Position : 48, Sql = CREATE INDEX dRTLastModified_RunTFB30128Ata ON RunTimeConfigData (dRTLastModified)

  • data exception:

    Caused by: Error : 1450, Position : 0, Sql = CREATE TABLE RunTimeConfigData

Note:

The errors in the server logs are due to warnings that are displayed in RCU content server schema creation on ATP-D database.

Documentation Errata

There are no known issues at this time.