2 Install and Configure
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
- Downloading and Applying Required Patches
Parent topic: Install and Configure
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:
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:
-
fmw_12.2.1.4.0_idm.jar
-
fmw_12.2.1.4.0_idmquickstart.jar
-
fmw_12.2.1.4.0_idmquickstart2.jar
Parent topic: Issues Related to Product Installation
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:
To download a patch:
-
Log in to My Oracle Support.
-
Click the Patches & Updates tab.
-
In the Patch Search area, select Patch Name or Number.
-
Enter the patch number.
-
Click Search. The Patch Search Results page appears.
-
Download and install the patch.
Parent topic: Issues Related to Product Installation
Issues Related to Product Configuration
This section contains the following topic:
Parent topic: Install and Configure
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.
Parent topic: Issues Related to Product Configuration
Issues Related to Product Installation and Configuration Documentation
This section contains the following topics:
- Registering Node Manager as a Windows Service
- Compatibility of Oracle Business Intelligence with Oracle Fusion Middleware
Parent topic: Install and Configure
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:
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.
Issues Related to Product Installation and Configuration on an Autonomous Database
The following sections cover the known issues and workarounds, and the limitations, related to product installation and configuration for Oracle Fusion Middleware products using an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)):
Note:
For the prerequisites to create schemas using Repository Creation Utility (RCU) on an Autonomous Transaction Processing database, see Prerequisites for Schema Creation on an Autonomous Transaction Processing Database in Creating Schemas with the Repository Creation Utility.
- Set the tns_admin before starting the configuration wizard as described in Starting the Configuration Wizard.
- Modify the wallet settings and update the classpath before you start the servers and the instance as described in Prerequisites for an Oracle Autonomous Transaction Processing-Shared (ATP-S) database and Starting Servers and Processes.
- Known Issues and Workarounds Related to Product Installation and Configuration on an Autonomous Transaction Processing Database
- Limitations Related to Product Installation and Configuration on an Autonomous Database
Parent topic: Install and Configure
Known Issues and Workarounds Related to Product Installation and Configuration on an Autonomous Transaction Processing Database
This section describes the issues and workarounds related to product installation and configuration for Oracle Fusion Middleware products using an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)).
Table 2-1 lists the general issues and workarounds you encounter in the RCU screens, when creating schemas for Oracle Fusion Middleware products using an Autonomous database.
Table 2-1 General Issues and Workarounds
Issue | Workaround |
---|---|
In the Database Connection
Details screen, when you select the database user
role as Normal, the warning |
Click Ignore and continue with the schema creation. |
In the Map Tablespaces screen, you may receive tablespace creation error due to insufficient privileges or exceeding of maximum number of DB_FILES |
For an ATP-D database, you must override the default and temporary tablespaces by selecting DATA from the drop-down list in the Default Tablespace column, and TEMP from the drop-down list in the Temp Tablespace column. For an ATP-S database, you must override the default and temporary tablespaces. See Map Tablespaces in Creating Schemas with the Repository Creation Utility. |
Table 2-2 lists the issues and workarounds that are applicable for specific Oracle Fusion Middleware products using an Autonomous database.
Table 2-2 Issues and Workarounds for Specific Oracle Fusion Middleware Products
Product | Issue | Workaround |
---|---|---|
Oracle SOA Infrastructure |
During SOAINFRA schema creation, for Oracle Identity
Management, the warning |
You can ignore the warning and proceed with the schema creation. |
Oracle Enterprise Scheduler (ESS) and Oracle Managed File Transfer (MFT) |
During schema creation, in the Summary screen,
the warning |
Add the create any job privilege to the
|
Oracle Enterprise Scheduler (ESS) and Oracle Managed File Transfer (MFT) |
During schema creation, even after adding the create any
job privilege, in the Summary
screen, the warning |
For ATP-D, apply patch 31443286 and restart the schema creation, and for ATP-S, apply patch 33351665 and restart the schema creation. |
Oracle WebCenter Content (WCC) |
During schema creation, warnings are displayed in the Summary screen. Example warning messages:
where, |
Click Ignore and continue with the schema creation. |
Oracle WebCenter Content (WCC) |
Error messages are displayed in the UCM server logs. The error messages in the UCM_server logs are:
|
|
Oracle WebCenter Sites (WCS) |
You cannot install and configure FirstSiteII sample site, and therefore, you cannot create new promotion assets, for Oracle WebCenter Sites using ATP-S. Note: This issue is applicable only for WebCenter Content using an ATP-S database. |
You must exclude FirstSiteII during the installation. |
Oracle Forms |
Forms Builder throws an Note: This issue is applicable only for Oracle Forms using an ATP-S database. |
This error can be ignored. However, as a result of this condition, Remote Dependency Mode is set to "TIMESTAMP". |
Oracle Forms |
Forms Application Deployment Service (FADS) fails to deploy
applications that contain SQL scripts when attempting to connect to
ATP-D and ATP-S. The error Note:The deployment of SQL scripts is not supported on IBM AIX. |
Apply patch 32645990. |
Oracle Internet Directory (OID) |
During schema creation using RCU, when the OID schema is loading, the
warning |
Click Ignore and continue with the schema creation. |
Oracle Internet Directory (OID) |
After you configure the domain, when you start the Administration Server for Collocated Oracle Internet Directory, error messages are displayed during the Administration Server startup. Note: This issue is applicable only for Oracle Internet Directory using an ATP-S database. For more information, see Starting Servers and Processes for Collocated Oracle Internet Directory in Installing and Configuring Oracle Internet Directory. |
This message does not have any functional impact and can be ignored. |
Oracle Internet Directory (OID) |
After you configure the domain, when you start the Administration Server for Collocated Oracle Internet Directory, a benign error message may be displayed in the Administration Server logs. For more information, see Starting Servers and Processes for Collocated Oracle Internet Directory in Installing and Configuring Oracle Internet Directory. |
This message does not have any functional impact and can be ignored. |
Oracle Access Management (OAM) |
After you configure the domain, when you start the Administration Server, a benign error message may be displayed in the Administration Server logs. For more information, see Starting the Servers in Installing and Configuring the Oracle Access Management Software . |
This error message does not have any functional impact and can be ignored. |
Oracle Identity Manager (OIM) |
After you configure the domain, when you start the Administration
Server and access the Sysadmin Console
( For more information, see Starting the Servers in Installing and Configuring the Oracle Identity Governance Software |
Restart the servers, Administration Server, Oracle SOA Server, and
Oracle Identity Manager (OIM) Server from the terminal after
unsetting classpath using the command: Note:You must restart the servers in the following order:
|
Limitations Related to Product Installation and Configuration on an Autonomous Database
This section describes the limitations related to product installation and configuration for Oracle Fusion Middleware products using an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)).
The limitations associated with Oracle Fusion Middleware products using an Autonomous Transaction database:
- You must create schemas as a Normal user, and though, you do not have full SYS or SYSDBA privileges on the database, you must select System Load and Product Load on the Create Repository screen of RCU.
- You can run RCU in silent mode only for Oracle GoldenGate and not for other Oracle Fusion Middleware products.
- The schema password must be minimum 12 characters, and must contain at least one uppercase, one lower case, and one number.
- You can specify the connection credentials in RCU using the Connection String format only. See Connection Credentials for an Autonomous Transaction Processing Database in Creating Schemas with the Repository Creation Utility.
- When you configure the domain to specify details about the database and database schema, in the Database Configuration Type screen, you must select the RCU Data option only. You cannot manually fill in parameters for your schema using the Manual Configuration option.
- When you configure the domain for JDBC component schema settings,
in the JDBC Component Schema screen, specify the
connection credentials using the Connection URL String
option only.
For Oracle Internet Directory, see the connect sting format in Specifying JDBC Component Schema Information in Installing and Configuring Oracle Internet Directory and for other products, see the connection string format in Specifying JDBC Component Schema Information in Installing and Configuring Oracle Identity and Access Management.
- When you specify the connection credentials to connect to the
database, for an Oracle Autonomous Transaction Processing-Shared
(ATP-S)) database, you must use only one of the database service names,
<databasename>_tpurgent
or<databasename>_tp
, specified intnsnames.ora
. See Connection Credentials for an Autonomous Transaction Processing Database in Creating Schemas with the Repository Creation Utility.Note:
This connection information is not applicable for an ATP-D database. - Some Forms features normally available in an on-premise database are not available in Autonomous Transaction Processing (ATP) or may be partially exposed with limitations because of ATP's enhanced security features. Because of these limitations, Forms features like Advanced Queuing integration and Database Idle System Events are not supported. See Oracle Forms Issues and Workarounds in Release Notes for Oracle Forms.
- The product installation and configuration for Oracle Fusion Middleware products using an Autonomous Transaction Processing database is certified only on Linux.