Installing ODI 126.96.36.199.0 on Windows 7 64bit
I’m going to try ODI again. Current ODI version is 188.8.131.52.0. Now, it has come under Oracle Fusion Middleware domain. A major difference from 10g.
My environment for ODI installation is a Intel Core i5 machine with 8 GB memory. It’s running on Windows 7 Professional 64 bit.
ODI is 11g is supported on my system according to the System Certification matrix; https://www.oracle.com/technetwork/middleware/data-integrator/odi-11gr1certmatrix-163773.xls
I got the installation media downloaded from; https://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html?ssSourceSiteId=ocomen
Since I’m running a 64 bit OS, required installation files are;
According to the new Middleware Architecture, now we have to create a database schemas to store a repository before starting the actual ODI installation. To create database schemas Oracle provides RCU; Repository Creation Utility.
RCU installation is available at the same URL mentioned above.
A pretty structured Installation Guide is available at; https://docs.oracle.com/cd/E23943_01/core.1111/e16453/overview.htm#CEGJJIFH
So there are 2 parts of my installation.
- Repository creation
- ODI installation
The repository is created in a RDBMS. So having access to a running database is a prerequisite.
To start with the repository creation, ofm_rcu_win_184.108.40.206.0_disk1_1of1.zip is extracted.
When extracted, within bin directory, rcu.bat can be found.
rcu.bat is executed;
Welcome screen appears and “Next >” is clicked.
We can use RCU to create or drop repositories. We want to create one here.Next
We define where we want the repository to be created. I’ve got an Oracle 11g DB on my machine. So we can use that.
I prefer to use SYS account in scenarios like this as it can avoid a lot of issues caused by bugs .Next
RCU checks the DB for requirements for creating the repository. And here, it complains that the DB hasn’t been created with character set it supposed to be for repository creation.
My DB was not created solely for the ODI installation So I cannot do much about it now. Hope we can ignore this error.
Other than the character set issue, my DB is ready for the repository creation.
We have to select which repositories to be created. Since RCU is a common tool that supports many products, we has to select what we want; Oracle Data Integrator in out case.
I’d leave the default prefix as it is. I’m building a development environment anyway.Next
Prerequisites are checked in another level.
Passwords for the repository schemas are defined. We have only one schema here. So the it doesn’t matter the option selection here.Next
Some ODI internal parameter settings; I’d accept the default value except the passwords.Next
The tablespaces where the schemas are created are defined. Even though we can change the tablespaces through “Manage Tablespaces”, I’m going to work with the default tablespaces RCU suggests.Next
Of course the tablespaces RCU suggested were not on my DB. They should be created fresh.
New tablespaces are created.
All set to launch the repository creation.
Repository creation is going on. It won’t take much time.
It’s done. No errors
RCU has created a tablespace of 200MB out of which 15.6 MB has been used for the repository.
Repository creation is completed. Now, ODI installation can be started.
Also, according to the Certification Matrix, I should have Oracle JDK 1.7.0+ 64bit installed on Windows 7 64 bit. So I had to download the JDK and install since I had only JRE before starting ODI installation.
Now the system is ready for the installation; ODI installation files should be extracted.
When both the files are extracted; setup.exe in Disk1 is executed. In my case, I needed to execute it with “Run as administrator” as the account I had logged in with is not in the Administrators group.
When setup.exe is executed, an error is fired;
“ERROR: Provided the JDK/JRE location while launching the installer. Invoke the setup.exe with -jreLoc parameter(s)”
According to the error message, it seems to be the setup.exe cannot find the JDK installation.
So I called the installer as instructed in the error message; from the command prompt (started with “Run as administrator")
setup.exe -jreLoc “C:\Program Files\Java\jdk1.7.0_09”
Nothing happened. Prompt was just returned.
In the JDK path, there is a space. This could be the issue here.
So I tried the path eliminating the space.
setup.exe -jreLoc “C:\Progra~1\Java\jdk1.7.0_09”
Same :(. Just returned to the prompt.
Another way; without the double-quotes;
setup.exe -jreLoc C:\Progra~1\Java\jdk1.7.0_09
Now something is happening.
ODI installer was launched
It’s a regular “Welcome” screen.Next
I’d skip the software updates for the moment.Next
Selecting what’s needed to be installed. The machine I’m installing on is my development environment as well as the data locations (sources and targets). So I’d select both “Developer Installation” and “Standalone Installation”.Next
My system is through with installation prerequisites check.Next
I usually keep big installation away from C: drive. I changed installation directory to E: drive.Next
Better to let the installer do as much as work. So I select to “Configure Repositories”.Next
Connection detailed to the repository created by RCU is provided.Next
Supervisor password is provided as defined during setting ODI parameters.Next
I’d need a work repository as I have to do my developments here.Next
I defined my agent as “ODIAgent1” with the port 60000.Next
I’m skipping security updates for the moment.Next
I’m sure about it.
Almost there. Better to save the configuration details for future reference.
installation goes on. Hope it’ll complete without errors. Hardly have that comfort.
So far so good…
Installation completes. And configuration process is started automatically. Configurations also has been completed successfully.Next
Installation completed. Better to save configurations details also.
Now I have an ODI environment with a Master Repository and a Work Repository named WORKREP ready for development. Both repositories were created in a single database schema.
Leave a Comments