This appendix describes solutions to common problems that you might encounter when running Repository Creation Utility (RCU).
It contains the following sections:
If you encounter an error during installation:
Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network the Oracle Fusion Middleware Documentation page.
Select the documentation library for your specific product release to view the release notes.
Verify that your computer meets the requirements specified in the Oracle Fusion Middleware System Requirements and Specifications document.
Select the document that is applicable for your release.
Verify that your environment meets the certification requirements as specified in the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document, which can be found on the Oracle Fusion Middleware Supported System Configurations page.
Make sure that your database is up and running.
If you entered incorrect information on one of the screens, use the navigation pane on the left hand side of the graphical interface to return to that screen.
If an error occurred while running RCU:
Note the error and review the RCU log files (see Section C.2, "RCU Log Files").
Correct the issue that caused the error. Depending on the type of error, you may either continue with your RCU operation, or be forced to restart RCU.
Continue or restart RCU to complete your desired operation.
Make notes about the solution procedures you perform, symptoms you see, and data you collect while troubleshooting. If you cannot resolve the problem using the information in this appendix and you must log a service request, the notes you make will expedite the process of solving the problem.
After performing any of the solution procedures, immediately retry the failed task that led you to this troubleshooting information. If the task still fails when you retry it, perform a different solution procedure and then try the failed task again. Repeat this process until you resolve the problem.
The main RCU log file is written to the RCU_HOME
/rcu/log/logdir.
date_timestamp
/rcu.log
(on UNIX operating systems) or RCU_HOME
\rcu\log\logdir.
date_timestamp
\rcu.log
(on Windows operating systems) file. For example, on a UNIX operating system:
RCU_HOME/rcu/log/logdir.2010-01-02_03-00/rcu.log
In addition to this general log file, each component writes a log file of its own. All component log files are also written to the RCU_HOME
/rcu/log/logdir.
date_timestamp
(on UNIX operating systems) or RCU_HOME
\rcu\log\logdir.
date_timestamp
(on Windows operating systems) directory.
Table C-1 lists the component log file names in alphabetical order by log file name.
Table C-1 RCU Component Log File Names
Component | Log File Name |
---|---|
Activity Graph and Analytics |
|
Authorization Policy Manager |
|
Business Activity Monitoring |
|
Business Intelligence Platform |
|
Oracle WebCenter Content Server 11g - Complete |
|
Oracle WebCenter Content Server 11g - Search |
|
Oracle Content Server 10g |
|
Discoverer |
|
Oracle Discussions Crawler |
|
Oracle Discussions |
|
Registry |
|
Audit Services |
|
Audit Services for OES |
|
Oracle Imaging and Process Management |
|
Oracle Information Rights Management |
|
Metadata Services |
|
Oracle Access Manager |
|
Oracle Adaptive Access Manager |
|
Oracle Adaptive Access Manager (Partition Support) |
|
Master and Work Repository |
|
Oracle Internet Directory |
|
Oracle Identity Federation |
|
Oracle Identity Manager |
|
Enterprise Scheduler Service |
|
SIP Infrastructure Location Service |
|
User Messaging Service |
|
SIP Infrastructure Subscriber Data Service |
|
Presence |
|
Portal |
|
Portlet Producers |
|
SOA Infrastructure |
|
Social Schema |
|
Social View Schema |
|
Social CEF Schema |
|
Oracle WebCenter Content: Records |
|
Spaces and Services |
|
In situations where you need to find which schemas are already installed in your database, there are two methods for accomplishing this.
You can run RCU (Section 2.4, "Starting RCU") and select Drop on the Create Repository screen. After specifying your database credentials, you will be able to see the schemas available for your drop operation, which are the schemas installed on the database.
You can also connect to and query the database using the following SQL command:
SELECT OWNER, VERSION, STATUS FROM SCHEMA_VERSION_REGISTRY;
During an Oracle Fusion Middleware installation, the Repository Creation Utility (RCU) performs checks against global and component-specific prerequisites to ensure that minimum requirements are met in the database prior to schema creation. If a prerequisite is not met, then RCU might issue a warning and allow you to continue, or will notify you with an error that a prerequisite must be met before the operation can continue. The following scenarios describe error and warning messages you might encounter during RCU prerequisite checking and what to do to resolve these issues.
During an Oracle Privileged Account Manager installation, RCU performs a prerequisite check to ensure that Transparent Data Encryption (TDE) has been enabled in the database for Oracle Privileged Account Manager.
Symptom: If Transparent Data Encryption has not been enabled in the database for Oracle Privileged Account Manager, then RCU issues the following warning:
Warning: Transparent Data Encryption (TDE) is not enabled in Database. Use of TDE is recommended. Action: Enable TDE in database. Follow Oracle Database Advanced Administrator's Guide to enable TDE in database.
Cause: This warning message was introduced in Oracle Identity and Access Management 11g Release 2 (11.1.2.3.0). If you continue with the installation without enabling TDE, then Oracle Privileged Account Manager will be installed in a less secure setup. For production deployments, Oracle recommends that you enable TDE on an Oracle Privileged Account Manager database because Oracle Privileged Account Manager relies on TDE for at-rest protection of sensitive information (such as passwords and other security-related data).
Solution: It is recommended that you stop RCU and enable TDE in the database before continuing.
For information about enabling TDE for Oracle Privileged Account Manager, refer to one of the following procedures, depending on the Oracle Database version you are using:
To enable TDE in Oracle Database Release 11.2, refer to the "Enabling Transparent Data Encryption" topic in the Oracle Database Advanced Security Administrator's Guide.
To enable TDE in Oracle Database Release 12.1, refer to the "Configuring Transparent Data Encryption" topic in the Oracle Database Advanced Security Guide.
OR
You can ignore the RCU warning and configure Oracle Privileged Account Manager to run without a TDE enabled database. However, this is not recommended because the sensitive information stored by Oracle Privileged Account Manager will not be secured at rest
Note:
For more information about Transparent Data Encryption, see"Securing Stored Data Using Transparent Data Encryption" in Oracle Database Advanced Security Administrator's Guide.
RCU performs a prerequisite check on Oracle databases to ensure that specific database initialization parameters are set high enough for the database to run properly and efficiently.
Symptom: If a database parameter is not set to the minimum required value, then RCU notifies you with an error, such as the following:
RCU-6107: DB Init Param Prerequisite failure for: OPEN_CURSORS. Current value is 300. It should be greater than or equal to 800.
Cause: This error occurs because RCU detects that a database initialization parameter has not been set high enough and does not meet the minimum component requirement for the components you are installing.
It is important to set database parameters before an installation as some components within a product have different requirements. The required parameters must meet the minimum component requirements before you can continue. For more information about these requirements, see the "RCU Requirements for Oracle Databases" section in the Oracle Fusion Middleware System Requirements and Specifications document.
Solution: Make sure the database parameters that are required for your installation meet the minimum component requirements. For information on how to set the values of database parameters, see the "Changing Initialization Parameter Values" topic in the Oracle Database Administrator's Guide.
For more information about basic initialization parameters, see
"Specifying Initialization Parameters" in Oracle Database Administrator's Guide
"Initialization Parameters" in Oracle Database Performance Tuning Guide
If this appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support (formerly OracleMetaLink) to help resolve Oracle Fusion Middleware problems:
https://support.oracle.com/
My Oracle Support contains several useful troubleshooting resources, such as:
Knowledge base articles
Community forums and discussions
Patches and upgrades
Certification Information
If you are unable to find a solution for your problem, open a service request.