1. Creating Schemas with the Repository Creation Utility
  2. Troubleshooting Repository Creation Utility

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.

Parent topic: Troubleshooting Repository Creation Utility

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

Parent topic: Troubleshooting Repository Creation Utility

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

Parent topic: Troubleshooting Repository Creation Utility

SOAINFRA Schema Creation Fails on a Hardened Database

Use this workaround if the RCU schemas for SOAINFRA does not load successfully on an Oracle hardened database.

In case of an Oracle hardened database, when the public grants are revoked for the PL/SQL packages, the schema creation for SOAINFRA fails with the following error:

Received Non-Ignorable Error: ORA-04063: package body "XDB.DBMS_CSX_INT" has errors

Grant the following permission to the user and run the Repository Creation Utility (RCU) again to create the schemas for SOAINFRA.

GRANT EXECUTE ON DBMS_LOB TO XDB;

Parent topic: Troubleshooting Repository Creation Utility

Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database

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

  • See Issues Pertaining to Product Installation and Configuration with Autonomous Database in the Release Notes for Oracle Fusion Middleware Infrastructure for issues related to installation and configuration for Oracle Fusion Middleware products on an Autonomous Transaction Processing database.

  • In the Database Connection Details screen, when you select the database user role as Normal, the following warning is displayed:

    Sysdba or dba privileges are required to load schema

    You can click Ignore and continue with the schema creation.

  • If you are creating schemas on an Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database, 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.

    Note:

    If you are creating schemas on an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, in the Map Tablespaces screen, you must override the default and temporary tablespaces. See Map Tablespaces.

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

    You can click Ignore and continue with the schema creation.

    Example warning messages:

    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
    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
    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

    where, /home/opc/idm and /home/opc/jrf are the ORACLE HOME locations.

  • During Oracle Internet Directory schema creation, when the schemas are loading, the warning ORA-28007: the password cannot be reused is displayed in the Summary screen.

    You can click Ignore and continue with the schema creation.

  • During SOAINFRA schema creation, for Oracle Identity Management, the warning ORA-24010: QUEUE DEV24_SOAINFRA.IP_IN_QUEUE does not exist is displayed in the RCU logs. This warning does not have any functional impact and can be ignored.

  • During schema creation of Oracle Enterprise Scheduler and Oracle Managed File Transfer SOA products, in the Summary screen, the following 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, the warning "ORA-01031: insufficient privileges" is displayed.

    For ATP-D, you can apply the patch 31443286 and restart the schema creation., and for ATP-S, you can apply the patch 33351665 and restart the schema creation.

Parent topic: Troubleshooting Repository Creation Utility

Known Limitation for Oracle WebCenter Sites ATP-S Migration

For Oracle WebCenter Sites, you cannot install and configure FirstSiteII sample site, and therefore, you cannot create new promotion assets, after you migrate an on-premises database to an Oracle Autonomous Transaction Processing (ATP-S) database.

As there is no workaround available, you must exclude FirstSiteII during the installation.

Parent topic: Troubleshooting Repository Creation Utility

Troubleshooting Database Configuration Error for Microsoft SQL Server

When running Repository Creation Utility (RCU) for Oracle Business Intelligence or Oracle Analytics Server on a Microsoft SQL Server database, an SQL SERVER RCU error can occur due to incorrect database configuration.

Perform the following steps to resolve the SQL SERVER RCU error:
  1. Launch SQL Server Management Studio, use SQL Server Authentication and log in as the schema owner (default "sa").
  2. Create a new database.

    Note:

    You can also modify an existing repository database.
  3. Set the collation to a case sensitive collation as follows:
    SQL_Latin1_General_CP1_CS_AS
    For more information about how to check case-sensitivity in SQL Server, see How to Check Case-Sensitivity in SQL Server.
  4. Right-click on the database name.
  5. Select New Query from the pop-up menu.
  6. In the Query window, run the following commands on the database to ensure all RCU database requirements are complete:
    
ALTER DATABASE database_name SET allow_snapshot_isolation ON
ALTER DATABASE database_name SET SINGLE_USER WITH ROLLBACK IMMEDIATE
ALTER DATABASE database_name SET read_committed_snapshot ON
ALTER DATABASE database_name SET MULTI_USER
ALTER DATABASE database_name SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT
  7. Run the Repository Creation Utility.
  8. Verify the process is complete.

Parent topic: Troubleshooting Repository Creation Utility

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.

Parent topic: Troubleshooting Repository Creation Utility