11-22-2013 08:28 AM
I recently installed Oracle Linux 6.3 for my DB server purpose. I would like to know if I can register the Oracle Linux with RHN OR should I register with ULN ?
Please let me know.
11-25-2013 01:23 AM
You can only register with RHN if you have paid RedHat for a support subscription (sometimes called "license" although that is not actually the right term).
If you have already paid Oracle for an ULN subscription, you should probably use that so you won't waste the money you've already paid.
Oracle apparently allows you to access the latest updates for free; but staying with a defined patch level (which is often required in enterprise environments) requires a paid ULN subscription.
Registering with RHN would cause your system to receive RedHat updates, causing your system to gradually "morph" from Oracle Linux to RedHat Linux as packages get replaced by updates.
11-25-2013 08:13 AM
I dont think we have a subscription for ULN yet, we are in the process of setting up RHN and hence wanted to know if Oracle Linux can be hooked to RHN.
What is the recommended approach, is it fine to have a Oracle linux host to be hooked to RHN in a Enterprise environment and what would be the side effects if any , especially the server being planned to connect to RHN is going to be a Oracle Database server.
11-29-2013 12:41 AM
I had a RedHat consultant visit us this week, so I asked him about this.
Oracle offers an easy way to register RHEL servers to their ULN, in order to migrate them from RHEL to OEL.
However, RedHat does not currently offer a similar way to register OEL servers to RHN: they apparently consider Oracle still a minor player in the Enterprise Linux field.
So, it looks like you cannot register an OEL server to RHN, at least without first manually replacing the appropriate ULN registration tools with their RedHat counterparts. And even if you could do that, it would eventually cause the server to transform from OEL to RHEL, as OEL packages get replaced with RHEL ones. You would be effectively the first tester of a new unsupported migration strategy. Not recommended for production servers.
Since OEL and RHEL are still very closely related and OEL even guarantees compatibility with the corresponding version of RHEL, there are good chances that it would technically work fine. But the problem is support.
If your Oracle Database licenses specify that the database must be installed on a supported OEL server, then turning the server into a RHEL (or a RHEL/OEL hybrid) would clearly be an unsupported configuration. If you needed support from Oracle, they would be entirely within their rights to say only "Please reproduce your issue with a supported platform, then we'll look into it." Even if the database is supported on RHEL too, you might have problems with the database support, as such a hybrid system is neither a pure RHEL nor a pure OEL, but something different and uncertified.
Since the Oracle Database licences can be the most expensive component of your set-up, and support for production databases is usually a critical requirement, I would recommend registering your OEL-based database servers to ULN and maintaining them as standard OEL servers. Having the database and underlying OS come from the same vendor (Oracle) also means that two vendors won't be able to blame each other if there is a problem.