java.lang.UnsatisfiedLinkError: no ocijdbc9 in java.library.path

Jamie McIlroy
Oct 27, 2006

--

So I’m trying to configure a servlet running on Tomcat to connect to IBM’s DB2 Content Management system (via II4C). I can get it to run under WebSphere using Rational Application Developer but seeing as I want to buy a MacBook Pro for my development, I figure I need to start using a more vanilla toolset. Martin Fowler’s Ravine post served as part of the inspiration. I actually believe it’s a good idea to build J2EE apps using a variety of tools…proves the openstandardiness of my work. The fact that I’m calling a client app from a server (II4C is a windows installed app) disproves that a little but whatever…the next stage will be abstracting that beastie behind some enterprise service layer and that’s that

The error comes from the driver’s need for the presence of ocijdbc9 in the container’s library path. Yeah, I know the use of Oracle’s thin driver eliminates the need to this coupling but in this case, I’m working with someone else’s project…they’re using this driver.

So add <<oraclehomedirectory>>/bin to the container’s Libary path and you’re back in the game…

This entry was posted in II4C, Lessons Learned. Bookmark the permalink.

Originally published at http://jamiemcilroy.wordpress.com on October 27, 2006.

--

--

Jamie McIlroy

Husband and Father. Wilderness First-Aid Certified. Terrible at tying knots. I play Squash. I like things that Trade. Leafs fan. FRC and Scouts Canada