The connect URL it will use given those parameters is the following:
String dburl = "jdbc:" + providerName + "//" + host + "/" +
database + ((instanceName==null)?"":";instance="+instanceName);
Or, filled in with your parameters:
jdbc:oracle:thin:@//21.16.18.145:1521/main
The "main" at the e
Sorry. I used the wrong character. It is configured for 21.16.18.145:1521
On Mon, Feb 27, 2012 at 10:27 AM, Karl Wright wrote:
> So if the "Database and Host" field really is "21:16:18:145:1521", try
> "21.16.18.145:1521" instead. ;-)
>
> Karl
>
> On Mon, Feb 27, 2012 at 9:22 AM, Matthew Parker
So if the "Database and Host" field really is "21:16:18:145:1521", try
"21.16.18.145:1521" instead. ;-)
Karl
On Mon, Feb 27, 2012 at 9:22 AM, Matthew Parker
wrote:
> type: JDBC
> Authority: None
> Database Type: ORACLE
> Database and Host: 21:16:18:145:1521
> Instance/Database: main
> User Name:
type: JDBC
Authority: None
Database Type: ORACLE
Database and Host: 21:16:18:145:1521
Instance/Database: main
User Name:
Password: X
On Sun, Feb 26, 2012 at 2:48 PM, Karl Wright wrote:
> I haven't seen this one. I'd love to know what the "connect
> descriptor" it refers to is.
>
> Can
I haven't seen this one. I'd love to know what the "connect
descriptor" it refers to is.
Can you tell me what the parameters all look like for the JDBC
connection you are setting up? Are you specifying, for instance, the
port as part of the server name?
Karl
On Sat, Feb 25, 2012 at 1:22 PM, Ma
Karl,
That fixed the driver issue. I just updated my start.jar file by hand for
now.
The problem I have now is connecting to ORACLE. I can do it through
NetBeans on my machine, but
I cannot connect through ManfoldCF with the same settings. I get the
following error:
Error getting connection. Lis
Thanks Karl.
On Thu, Jan 19, 2012 at 9:44 PM, Karl Wright wrote:
> The problem has been fixed on trunk. Basically, the instructions
> changed as did some of the build files. It turned out to be extremely
> challenging to get JDBC drivers to run when they were loaded by
> anything other than th
The problem has been fixed on trunk. Basically, the instructions
changed as did some of the build files. It turned out to be extremely
challenging to get JDBC drivers to run when they were loaded by
anything other than the system classloader, so that's what I was
forced to insure.
Thanks,
Karl
The ticket for this problem is CONNECTORS-390.
Karl
On Thu, Jan 19, 2012 at 3:05 PM, Matthew Parker
wrote:
> Many thanks. I'll give that a try.
>
> On Thu, Jan 19, 2012 at 3:01 PM, Karl Wright wrote:
>>
>> The problem is that the JDBC driver is using a pool driver that is in
>> common with the
Many thanks. I'll give that a try.
On Thu, Jan 19, 2012 at 3:01 PM, Karl Wright wrote:
> The problem is that the JDBC driver is using a pool driver that is in
> common with the core of ManifoldCF. So the connector-lib path, which
> only the connectors know about, won't do. That's a bug which I
The problem is that the JDBC driver is using a pool driver that is in
common with the core of ManifoldCF. So the connector-lib path, which
only the connectors know about, won't do. That's a bug which I'll
create a ticket for.
A temporary fix, which is slightly involved, requires you to put the
o
Thanks for your help.
On Thu, Jan 19, 2012 at 2:48 PM, Karl Wright wrote:
> I was able to reproduce the problem. I'll get back to you when I
> figure out what the issue is.
> Karl
>
> On Thu, Jan 19, 2012 at 2:47 PM, Matthew Parker
> wrote:
> > I've used the jar file in NetBeans to connect to
I was able to reproduce the problem. I'll get back to you when I
figure out what the issue is.
Karl
On Thu, Jan 19, 2012 at 2:47 PM, Matthew Parker
wrote:
> I've used the jar file in NetBeans to connect to the database without any
> issue.
>
> Seems more like a class loader issue.
>
>
> On Thu,
I've used the jar file in NetBeans to connect to the database without any
issue.
Seems more like a class loader issue.
On Thu, Jan 19, 2012 at 2:41 PM, Matthew Parker <
mpar...@apogeeintegration.com> wrote:
> I have the latest release from the Apache Manifold site (i.e.
> 0.3-incubating).
>
> I
I have the latest release from the Apache Manifold site (i.e.
0.3-incubating).
I checked the driver jar file with winzip, and the driver name is still the
same (oracle.jdbc.OracleDriver).
I'm running java 1.6.0_18-b7 on Windows XP SP 3.
On Thu, Jan 19, 2012 at 2:27 PM, Karl Wright wrote:
> MCF
MCF's Oracle support was written against earlier versions of the
Oracle driver. It is possible that they have changed the driver
class. If the driver winds up in the dist/connector-lib directory
(I'm assuming you are using trunk or 0.4-incubating), then it should
be accessible.
Could you please
I downloaded MCF and started playing with the default setup under Jetty and
Derby. It starts up without any issue.
I would like to connect to our ORACLE database and import data into SOLR.
I placed the ojdbc6.jar file in the connectors/jdbc/jdbc-drivers directory
as stated in the README instructi
17 matches
Mail list logo
