Tuesday, August 07, 2012

Oracle Data Integrator failed Checking operating system certification

Oracle Data Integrator is a comprehensive data integration platform that covers all data integration requirements: from high-volume, high-performance batch loads, to event-driven, trickle-feed integration processes, to SOA-enabled data services. Oracle Data Integrator can be used to communicate between Oracle databases and the Hadoop platform. When working on big-data projects ODI can help you to quickly develop and deploy map reduce solutions within your enterprise landscape.

ODI can be installed on several platforms including Oracle Linux. One of the issues with installing on Oracle Linux is that the latest version of Oracle Linux is currently not supported and will result in an error during installation. The installer will state (in my case Oracle Linux 6.3) the following:

Checking operating system certification
Expected result: One of enterprise-5.4, enterprise-4, enterprise-5, redhat-5.4, redhat-4, redhat-5, SuSE-10, SuSE-11
Actual Result: redhat-6.3

Meaning the Oracle Data Integrator is not certified currently on Oracle Linux 6.3 and secondly the Oracle Universal Installer is identifying the operating system as a redhat-6.3 distribution.

You can resolve this by adding Oracle Linux (redhat) as a certified system to the file used to check what is certified. In the past you could do so by adding a line to the file $basedir/Disk1/install/linux/oraparm.ini . However, in the newer versions of the Oracle Universal Installer a new way of working has been introduced and you have to edit a different file.

You will have to edit the XML file where the prerequisites are stored. You can find this file at $basedir/Disk1/stage/prereq/linux/refhost.xml in the refhost.xml file you will find a couple of configurations which are allowed. I have added the below lines to the file to make Oracle Linux 6.3 a valid configuration.

After changing the XML file and saving it you can restart the installer and you will see that the check is now completed without any issue. I have noticed some differences in different machines where sometimes it is needed to restart the installer and sometimes you can just do a retry. To be on the safe side it is good practice to start the installer again.

No comments: