NetIQ recommends that you cluster the database in a production environment to provide fault tolerance for the information Identity Governance stores on the database. Database clustering is a feature of each respective database server. We do not officially test with any clustered database configuration since clustering is independent of the functionality of Identity Governance. In our code, we use a combination of Hibernate and Liquibase; as a result, the database server and its configuration are transparent to us.
In summary, we support clustered database servers within the following constraints:
Our installers are not designed to install the products into a database cluster. We require database administrators to install into a specific instance of the database and then modify the JDBC URL information accordingly. You might need to adjust other utilities as well.
We have not performed any official tests with any clustered database servers.
You might have to disable some features or aspects of the clustered database server. For example, Transactional Replication must be disabled on certain tables due to a constraint violation when trying to insert a duplicate key.
We do not provide assistance on the installation, configuration, or optimization of the clustered database server, and we do not assist in installing our products into a clustered database server.
You must reproduce issues or analyze the behavior of the components in a non-clustered environment to help isolate potential cluster setup issues from issues within our products.
NetIQ exerts its best effort to resolve any issues that might arise with the use of our products in a clustered database environment. Troubleshooting methods in a complex environment often require cooperative work to resolve issues. NetIQ provides the expertise to analyze, plan, and troubleshoot NetIQ products. You must provide the expertise to analyze, plan, and troubleshoot any 3rd party products such as the database server, database clustering, and so forth.