An administrator upgrades the IBM DB2 JDBC driver. The test connection operation fails. On checking the System.Out log the administrator finds that the JVM is still using the old JDBC driver.
What could be the possible reason for the failure?
Haha, yeah, I can just imagine the administrator trying to upgrade the driver and accidentally deleting all the JARs. That would be a real face-palm moment!
Hmm, good point. I was leaning more towards option B - the driver upgrade failed. Maybe there was an issue with the installation or the new driver wasn't compatible with the system.
But I'm not sure about that. Option D also seems plausible - if the DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable was not set correctly, that could also lead to the old driver being used.
I agree. My first thought was option C - multiple drivers in the provider classpath. That could definitely cause the JVM to use the old driver instead of the new one.
Hmm, this question seems to be testing our understanding of JDBC driver management. I think the key here is that the JVM is still using the old driver, even after the administrator upgraded it.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Deja
5 months agoShaniqua
5 months agoEmelda
5 months agoGeorgeanna
5 months agoJimmie
6 months agoMozell
6 months agoJaclyn
6 months agoCristal
7 months agoLauran
6 months agoMiss
6 months agoIzetta
7 months agoKirk
7 months agoLilli
7 months agoMabelle
7 months agoKara
7 months ago