OBIEE 11g installation – Part2

OBIEE 11g installation – Part2
Getting back to the OBIEE 11g install, what we’ve got so far is a clean Win 2003 server virtual machine with both installation zip files downloaded and uncompressed.  We have a 10g database with a new OBIEE_RPD schema waiting for the RCU to generate a repository, and we have the RCU tool itself downloaded and uncompressed.
I found rcu.bat in the ‘\ofm_rcu_win32_11.1.1.3.3_disk1_1of1\rcuHome\BIN’ folder.  I looked at the file.  It is a batch file wrapper for a Java app.  I tried running it but it failed right away with path not found.  Looking at the error I’m guessing that it does not agree with spaces in the folder path.  I’ve been storing the OBIEE installers in a folder called c:\download\software\OBIEE 11g\… which I have now renamed to c:\download\software\OBIEE_11g\… This did the trick, I launched the batch file and it immediately disappeared (I should have added a pause at the end of the file to see what the console did).  A few moments later, a Repository Creation Java app appeared.

I should probably take this time to point out that I already had the Java JDK (jdk1.6.0_07) installed.  However prior to continuing I will take a break and install the Oracle 10g Client on the Vmware Win 2003 server as well since I will need it to connect to the repository generated by the RCU.
My new OBIEE 11g virtual machine can now connect to my 10g database (tested via tnsping).  I’m now going to move ahead with the RCU tool.  Re-running rcu.bat, I selected the create option, and typed in the connection details for my OBIEE_RPD user.  I clicked next and received an error message stating that I was connecting to an unsupported database version.  Now, my 10g database is 10.2.0.1.0, and according to the error popup, the minimum db version is 10.2.0.4.0.  I ignored the error.
On the next screen, I left DEV as the default prefix, and selected Business Intelligence but did not select the top line option Oracle AS Repository Components.

Since this is a demo build, on the next screen I selected ‘user same password for all other schemas’ and re-used the same password I had specified for OBIEE_RPD (I have far too many demo systems on my laptop to keep track of different passwords).
I found a small glitch on the next screen – the field sizes can’t be extended to show the full text strings.  In the tablespace selection, I picked existing tablespaces on my 10g instance (you can use the dropdowns for this).  There is a ‘manage tablespaces’ button which allows you to add tablespaces as required.

I clicked create but immediately got an error of insufficient rights.  Rather than to modify OBIEE_RPD, I went back and used the sys (SYSDBA) user for the RCU process.  Incidentally, the first screen dictates using a user with DBA or SYSDBA privileges, which does not extend to simply assigning a DBA role to a user.
I did get an error stating that a name was already used when creating table qrtz_job_details.  I ignored this error, as it was likely caused by the previous install attempt.  The rest of the repository creation process completed without further issues.
According to the install documentation, this is the point where we can run the OBIEE 11g installer.  The process has taken about 4 hours up until now with a few lessons learned.  The up front prerequisites took some time, but the rcu tool itself executed fairly quickly.