He's right and he's wrong at the same time.
Oracle calculates its licensing cost based on cores but then discounts that number depending on its calculation of the 'power' of the processor architecture. In the case of x86/x86_64, the discount is 50% meaning that two cores counts as one processor for licensing purposes. This of course means that a license for a quad-core CPU will cost you just as much as two dual-core CPUs.
As for charging you according to the amount of RAM in a server, that's just rubbish. We've just upgraded to 256GB per server in our main RAC and the licensing cost is no different than when we first rolled it out with 32GB in each node.
Try Optimize Google instead. It's a far more actively maintained fork.
One here and another here. Both are for older versions (3&4) of RHEL but the same principles apply.
As someone who works with Oracle RAC and RHEL regularly, I'd recommend skipping the shared physical disk completely and using NFS instead. You could (and we do in testing) run the NFS server virtualised as well.
Or even better, Safekeep which uses rdiff-backup but adds easy per-server configurations without writing scripts, LVM snapshots, database dumps and SSH key configuration.
If A = B and B = C, then A = C, except where void or prohibited by law. -- Roy Santoro