This action is only required if you use an external database system, such as Microsoft SQL Server or Oracle, and you update from an ARIS version that uses an outdated JDBC driver. This can result in runnables that will remain in the STARTING state. The listed runnables use JDBC drivers and can be affected: adsadmin, umcadmin, copernicus, octopus, abs, hds, apg, ecp, dashboarding, and arcm.
If you had enhanced a JDBC driver in your former ARIS installation using an ACC connand, such as:
enhanceall abs_l with commonsClasspath path "<JDBC Driver name with version>jar"
this JDBC driver file was copied to the <ARIS installation directory>\server\bin\work\work_abs_l\base\lib.
If you add the latest file to update your JDBC driver with the enhance ACC command, both driver files, the obsolete file and the latest file are present. As a result, runnables will not start correctly because the JDBC driver to be used cannot be determined.
If abs and copernicus runnables remain in the STARTING state, delete obsolete JDBC driver files from the <ARIS installation directory>\server\bin\work\work_abs_l\base\lib.