DB2 does not have the equivalent of RAC clustering for scalability (of course RAC doesn't scale very well for OLTP because of the distributed lock manager, but that is another issue). In DB2 clustering for reliability is done with HADR, which is superior to RAC, since RAC has a single point of failure on the shared disk sub-system (and usually the network).
One thing to keep in mind is that you only need to license DB2 for 100 PVU's on the HADR standby server (which is the equivalent of 1 dual core CPU), regardless of how many CPU's are on the machine.
Xkoto is a 3rd party tool that provides clustering for reliability and scalability, but it only provides scalability on Select statements. Inserts, Updates, and Deletes are single threaded, whereas Selects can be distributed out to any available server in the gridscale cluster (you usually need a minimum of 3 servers for high availability/scalability and a minimum of 2 if scalability is the only concern and you have maintenance window). Xkoto is somewhat complicated, and reports are that it is not completely bug-free, but it does work well if you have OLTP and need scalability of a mostly read-only database, and you don't have a data warehouse (in which case DB2 DPF would be a better choice).