Hi,
there is Sybase Cluster Edition that works similar to Oracle RAC.
In addition there are a lot of Vendor applications out there that have built in ha-facilities and can run / should run in a concurrent resource group - not for availability - but for load balancing reasons. And here the cluster facilities are not used for the applications themselves but for the infrastructure that points to the application. If one node goes down, the service IP just starts pointing to the other node - the application - though down on the previous node - remains available. Great solution for any kind of application that doesnt produce volatile data at all.
We have several clusters where Websphere and MQ are running active on both nodes - serving different functions - and again failover to the other node when required - serving different clients, different applications - and yes we want different instances of the same application being up on one node if the other node dies.
We have as well lots of sybase databases in a hacmp setup that have the same content but serve different purposes. Sybase replication server replicates the content of database 1 into database 2. As long as both nodes are up, database 1 is used for trading, database 2 for reporting - when one of the nodes dies, it fails over to the other node - replication remains running - and you still can use both databases for these different purposes - nothing in the listeners, pointer files or anything has to change because the IP of the application doesn't change ... and additional resources are just added via dlpar scripts if required - so nothing is starving ...
Possibilities are countless and so are the benefits of having live-live clusters
Kind regards
zxmaus