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.
• 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.
• RCU Fails to Connect with ORA-604 ORA-1882 Error Codes
  Error codes ORA-604 and ORA-1882.
• 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.
• 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).

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

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;

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.