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 WebSphere Application Server.
JDBC class path not defined exception
If you are using a database or property extension repository for which the JDBC class path variable is not defined, you might encounter the following exception when you start WebSphere Application Server.
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
You 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.
Using 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 WebSphere Application Server startup an exception might be thrown.