Express (Distributed operating systems), v8.0 > Secure applications and their environment > Authenticate users > Select a registry or repository > Manage realms in a federated repository > Virtual member manager > Troubleshoot and Support > Support issues and limitations
Database issues and limitations
This section contains issues and limitations related to databases.
- IdMgrDBSetup exception
When running the commands related to IdMgrDBSetup to configure virtual member manager repositories, such as Entry Mapping and Property Extension, you might encounter a SOAPException.- JDBC driver not found during startup
If you are using a database or property extension repository, the problem described here might occur when you start WAS.- Oracle Transaction Exception
When virtual member manager is reinstalled, the Oracle XA transaction log is not cleaned up correctly.- setupIdMgrDBTables command fails
The setupIdMgrDBTables command might fail because the WebSphere variable DB2_JDBC_DRIVER_PATH is set incorrectly.- The setupIdMgrDBTables command fails for the Microsoft SQL Server
We must update the table space in the database schema before you can issue the setupIdMgrDBTables command for the Microsoft SQL Server.- User management supports a single DB2 database
The user management component supports only one database in each database repository.- Use a database as the default repository fails
When a database repository is setup as one of the repositories and is used for login during the WAS startup an exception might be thrown.
Parent topic: Support issues and limitations