The 126.96.36.199 patchset changed all the rules. Several new functionalities were added to the patchsets. Several functionalities have been added to RACOne. Unfortunately they didn't make it to the manuals. Some of them I discovered only recently. If you have been using RACOne, or considering it, you will be delighted to know these.
(1) Bye Bye Patch - In 188.8.131.52 RACOne was supported; but you had to apply a patch - 9004119 . Well, it was confusing at the best. A favorite interview question on RACOne fo rmany way this patch. It's gone; 184.108.40.206 already has the patch.
(2) OMotion - remember the OMotion tool used for relocating the database instance? It was probably modeled after the functionality of VMotion in VMWare; hence the namesake. However, it was completely redundant. The clusterware has the functionality anyway; and RACOne has the clusterware; so I never understood the need for OMotion.
In 220.127.116.11, it's gone. To relocate database instance from one server to another, you simply issue srvctl relocate command.
$ srvctl relocate database -d DBNAME -n
(3) Creation - no need to create the RACOne using raconeinit script. DBCA can create it. Oracle Installer can install RACOne as well.
(4) Status - Earlier you had to use raconestatus command to know the status of the RACOne database. This is no longer needed. You can use srvctl status or crsctl status commands.
(5) Upgrades - upgrading RACOne? DB Ugrade Assistant is aware of RACOne as well.
(6) Conversion - Converting a database to RACOne? SRVCTL comes to rescue:
$ srvctl convert database -d ....
(7) Data Guard will work on RACOne as well.