Follow Us on Twitter

Running Oracle Repository Creation Utility on 64-bit Ubuntu

by Mike Heeren on November 14, 2014 · 3 comments

Today I needed the Oracle Repository Creation Utility (RCU) on a 64-bit Ubuntu VM. However, if you search the Oracle website, you can only find a 32-bit version of the RCU. I decided to download the 32-bit version instead.

We start the process of running the RCU by unzipping the downloaded file.  Navigate to the folder where the downloaded file is placed and execute the following command:

Running Oracle Repository Creation Utility on 64-bit Ubuntu.

The files will be unzipped in a new directory called “rcuHome”. Navigate to the “bin” folder in this directory:

cd rcuHome/bin/

You should be able to start RCU by executing the following statement:


However, when I executed this statement, the following error message was shown:

./rcu: 276: 
./rcu: /home/username/directory/rcuHome/jdk/jre/bin/java: not found

This error can be fixed by editing the “rcu” file we just tried to execute. I did this using gedit:

sudo gedit rcu

Search for the following line in the file:


Edit this line, so the JRE_DIR variable is pointing to the directory where your JRE is installed. For me the line could be changed in the following. However, this requires that the JAVA_HOME environment variable is set.


Save the “rcu” file and try to execute the file again. This can be achieved using the following command:


This time, the RCU was started correctly. In the “Database Connection Details” screen of the RCU the next problem occurred. For some reason, I was not able to select the role of the database user:


Leaving the “Role” field blank an selecting “Next” resulted in the following error message:


I decided to set the database user role in the “Username” field. This can be achieved by adding “as <rolename>” after the username as shown in the image below.


After this, I was able to complete the RCU wizard.

Good luck!

Running Oracle Repository Creation Utility on 64-bit Ubuntu, 5.0 out of 5 based on 2 ratings
VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)

{ 3 comments… read them below or add one }

Patrick Sinke December 10, 2014 at 9:23 pm

There are more than a few occasions where logging in “as sysdba” can be a hassle. Incidentally, I encountered the same problem yesterday with logging in to SQL*Plus from a remote location (without a TNSNAMES.ORA). Compliments for fixing it here!


roberthoot February 6, 2015 at 6:18 am

Do you have a spam issue on this blog; I also am a blogger, and I was curious about your situation; many of us have created some nice practices and we are looking to swap solutions with other folks, please shoot me an e-mail if interested.great work.


torrentinfotech August 9, 2019 at 12:52 pm

useful information


Leave a Comment


Previous post:

Next post:

About Whitehorses
Company profile

Whitehorses website

Home page

Follow us
Blog post RSS
Comment RSS