Note that there are some explanatory texts on larger screens.

plurals
  1. PO"Unable to locate JAR/zip" error for JDBC connections [BIRT Eclipse, Windows 7, Oracle 11g]
    primarykey
    data
    text
    <p>As an FYI, I'm new to this entire stack, so I might be making a basic error.</p> <p>I'm attempting to explore BIRT reporting for a Maximo system that was recently upgraded.</p> <p>To do so, I installed the following: </p> <ul> <li>Java 6 &amp; Java 7 JDKs</li> <li>BIRT version of Eclipse (Eclipse + BIRT plugins built in).</li> <li>Some Oracle 11gR2 client options (a custom install) <ul> <li>SQL*Plus</li> <li>JDBC/ODBC drivers</li> <li>Thin Client</li> </ul></li> </ul> <p>I take the following steps:</p> <ul> <li>Open Eclipse</li> <li>Create a new Reporting Project</li> <li>Add a Data Source</li> <li>Select "JDBC Data Source" (also tried "JDBC Database Connection for Query Builder")</li> <li>Select the "Oracle" connection profile type and click next.</li> </ul> <p>At this point, I see that the drivers list is empty. This strikes me as odd, but I figure maybe I have to define the driver definition. So I take the following steps:</p> <ul> <li>Click "Define driver definition"</li> <li>In the Name/Type tab, select "Oracle Thin Driver", system version 11</li> </ul> <p>At this point, I see an error message: <strong>Unable to locate JAR/zip in file system as specified by the driver definition: ojdbc14.jar</strong>. It seems that ojdbc14.jar doesn't even exist on my system that I can find.</p> <p>I have tried adding other jdbc jar files that I can find in the oracle client directory (i.e. from Oracle_Base\product\11.2.0\client_1\jdbc\lib) but nothing seems to resolve the issue.</p> <p>Help?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload