D Troubleshooting Repository Creation Utility

Review this information to help you understand and troubleshoot any errors or issues that you encounter while you run the RCU.

General Troubleshooting Tips

Use these tips to help troubleshoot any errors that you encounter during installation.

  • See Install and Configure in the Release Notes for Oracle Fusion Middleware Infrastructure for the latest updates and issues related to Oracle Fusion Middleware product installation and configuration.

  • Verify that your computer meets the requirements as 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 for your release and platform, as specified 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 most side of the graphical interface to return to that screen.

  • If an error occurred while running RCU:

    1. Note the error and review the installation log files (see RCU Log Files).

    2. Correct the issue that caused the error. Depending on the type of error, you may either continue with your RCU operation, or you are forced to restart RCU.

    3. Continue or restart RCU to complete your desired operation.

RCU Log Files

When you run RCU to create or drop your schemas, the main RCU log file is written to the /tmp/RCUdate_timestamp_random_number/logs directory on UNIX operating systems or C:\Users\user_name\AppData\Local\Temp\RCUdate_timestamp_random_number\logs directory on Windows operating systems, by default.

For example, on a UNIX operating system:

/tmp/RCU2014-01-02_03-00_412547075/logs/rcu.log

Accessing RCU Log Files on Windows

On Windows operating systems, the AppData folder might be hidden. To be able to navigate to the RCU log files on Windows, ensure that the AppData folder is visible:

  1. From the Start menu, select Control Panel, then Appearance and Personalization, and then Folder Options.

    The Folder Options window appears.

  2. Select the View tab.

  3. Under Advanced settings, ensure that Show hidden files, folders, and drives is selected and click OK.

RCU Component Log Files

In addition to the general log file, each component writes a log file of its own. All component log files are also written to the same directory as the rcu.log file.

Table D-1 lists the component log file names in alphabetical order by log file name.

Table D-1 RCU Component Log File Names

Component Log File Name

Analytics

activities.log

Business Intelligence Platform

biplatform.log

Oracle WebCenter Enterprise Capture

capture.log

Oracle WebCenter Content Server — Complete

content.log

Oracle WebCenter Content Server — Search Only

contentsearch.log

Discussions

discussions.log

EDQ Config Repository

edq_conf.log

EDQ Results Repository

edq_res.log

Oracle Enterprise Scheduler

ess.log

Audit Services

iau.log

Audit Services Append

iau_append.log

Audit Services Viewer

iau_viewer.log

Metadata Services

mds.log

Managed File Transfer

mft.log

Master and Work Repository

odi.log

Monitor Server

oggmon.log

Oracle GoldenGate Studio Repository

oggstudio.log

Oracle Platform Security Services

opss.log

Portlet Producers

portlet.log

SOA Infrastructure

soainfra.log

Common Infrastructure Services

stb.log

User Messaging Service

ucsums.log

Veridata Repository

veridata.log

WebCenter Sites

wcsites.log

WebCenter Sites — Visitor Services

wcsitesvs.log

Portal and Services

webcenter.log

WebLogic Services

wls.log

RCU Fails to Connect with ORA-604 ORA-1882 Error Codes

Error codes ORA-604 and ORA-1882.

RCU fails to connect database with the following errors:

  • ORA-604: error occurred at recursive SQL level 1

  • ORA-1882: timezone region not found

Setting RCU_JAVA_OPTIONS before Invoking RCU

Set the below property and invoke RCU:

RCU_JAVA_OPTIONS -Doracle.jdbc.timezoneAsRegion=false

Troubleshooting Tips for Schema Creation on Autonomous Transaction Processing-Dedicated Database

Use these tips to troubleshoot any errors you encounter during schema creation on Autonomous Transaction Processing-Dedicated (ATP-D) database.

  • See Product Installation and Configuration with ATP-D Database in the Release Notes for Oracle Fusion Middleware Infrastructure for issues related to Oracle Fusion product installation and configuration on ATP-D database.

  • In the Database Connection Details screen, when you select the database user role as Normal, a warning "Sysdba or dba privileges are required to load schema" is displayed.

    You can click Ignore and continue with the schema creation.

  • In the Map Tablespaces screen, if you receive any tablespace creation error due to insufficient privileges or exceeding of maximum number of DB_FILES, you can override the default and temporary tablespaces for the selected components by selecting existing tablespaces from the drop-down list in the Default Tablespace column and Temp Tablespace column.

    For example, to override the default and temporary tablespaces, you can select DATA from the drop-down list in the Default Tablespace column, and TEMP from the drop-down list in the Temp Tablespace column.

  • During Oracle WebCenter Content schema creation, warnings are displayed in the Summary screen.

    You can click Ignore and continue with the schema creation.

    For example, you can see the following warnings:
    • ORA-01031: insufficient privileges
      File:/home/opc/idm/oracle_common/../wcccontent/common/sql/content/sql/oracle/contentserverrole.sql
      Statement: GRANT SELECT  ON CTXSYS.DR$PENDING TO contentserver_role

      In the example, /home/opc/idm is the ORACLE HOME location.

    • ORA-01450: maximum key length (6398) exceeded
      File:/home/opc/jrf/oracle_common/../wcccontent/common/sql/content/sql/oracle/contentserverrole.sql
      Statement: CREATE TABLE RunTimeConfigData

      In the example, /home/opc/jrf is the ORACLE HOME location.

    • ORA-01450: maximum key length (6398) exceeded
      File:/home/opc/jrf/oracle_common/../wcccontent/common/sql/content/sql/oracle/intradoc.sql
      STATEMENT Create table Subscription

      In the example, /home/opc/jrf is the ORACLE HOME location.

  • During schema creation of Oracle Enterprise Scheduler and Oracle Managed File Transfer SOA products, in the Summary screen, a warning "ORA-01031: insufficient privileges" is displayed and the schema creation fails.

    Add the “create any job” privilege to the “ADMIN” user, and restart the schema creation.

  • During schema creation of Oracle Enterprise Scheduler and Oracle Managed File Transfer SOA products, even after adding the create any job” privilege, in the Summary screen, a warning "ORA-01031: insufficient privileges" is displayed.

    You can apply the patch 31443286 and restart the schema creation.

Need More Help?

If this guide does not solve the problem that you encountered, try looking for a solution on My Oracle Support (formerly Oracle MetaLink).

https://support.oracle.com/

If you are unable to find a solution for your problem, open a service request.