RSA Identity Governance and Lifecycle error when using the IBM DB2 driver: "Unable to load database driver"
Originally Published: 2016-11-10
Article Number
Applies To
RSA Product/Service Type: Enterprise Software
RSA Version/Condition: 7.0.0, 7.0.1
Issue
11/07/2016 09:30:35.984 INFO (ApplyChangesRegularThread-4347)
[com.aveksa.client.datacollector.framework.DataCollectorManager]
DCM147: Booted Data Collector -1
11/07/2016 09:30:36.013 ERROR (ApplyChangesRegularThread-4347)
[com.aveksa.collector.accountdata.DBGenericAccountReader]
Unable to load database driver: com.ibm.db2.jdbc.net.DB2Driver
FAILED method=initDriver
11/07/2016 09:30:36.013 ERROR (ApplyChangesRegularThread-4347)
[com.aveksa.collector.accountdata.DBGenericAccountReader]
Details : java.lang.ClassNotFoundException: com.ibm.db2.jdbc.net.DB2Driver
FAILED method=initDriverCause
Resolution
Follow the same instructions in the RSA Identity Governance and Lifecycle - IBM DB2 Collector Datasheet for installation of the db2jcc_license_cu.jar file.
Contact IBM for more information on the licensing requirements for the DB2 driver.
Related Articles
Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201… 288Number of Views On database startup for RSA Identity Governance and Lifecycle the following error is seen: CRS-2501: Resource 'ora.avdb.d… 508Number of Views RSA Governance & Lifecycle Database DB2 Connector Datasheet 30Number of Views RSA Identity Management and Governance Appliance Updater 65Number of Views No SQL Strategy found for SQL statement: Execute CreateAccount when using a Generic Database AFX connector in RSA Identity… 49Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) RSA announces the availability of the RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server How to troubleshoot Oracle database ORA-04030 errors in RSA Identity Governance & Lifecycle RSA Authentication Manager Upgrade Process Microsoft SQL Server Collectors can no longer connect to the SQL Server database after upgrade to Microsoft SQL Server 201…
Don't see what you're looking for?