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.
setupIdMgrDBTables command fails
The setupIdMgrDBTables command might fail because the WebSphere variable DB2_JDBC_DRIVER_PATH is set incorrectly.
Oracle Transaction Exception
When virtual member manager is reinstalled, the Oracle XA transaction log is not cleaned up correctly.
Searching with datetime fails
If you perform a search using datetime and receive an InvalidAttributeVaule exception, it might be caused by a datetime format that is not valid in xpath.
Relative distinguished name translation limitation
When two or more LDAP servers are used and the relative distinguished name (RDN) attributes for a particular type of Member are not the same, only one of the RDNs can be used as the virtual member manager RDN.
Added escape character in unique name
If the user ID contains a special character (namely, "#", "," , "+", """, "\", "", "<", ">" or ";"), the unique name that is generated has an escape sequence consisting of a backslash (\) preceding the special character.
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.