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 end is what I would wonder about. Oracle's default
is "database"; if you leave the "database/instance name" field blank,
that's what you'll get.
I also recommend turning on connector debugging, in properties.xml, by adding:
<property name="org.apache.manifoldcf.connectors" value="DEBUG"/>
... and restarting ManifoldCF. Try viewing the connection in the UI;
you should see the connect string logged, as well as possibly a more
detailed response.
Thanks,
Karl
On Mon, Feb 27, 2012 at 11:12 AM, Matthew Parker
<mpar...@apogeeintegration.com> wrote:
> 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 <daddy...@gmail.com> 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
>> <mpar...@apogeeintegration.com> wrote:
>> > type: JDBC
>> > Authority: None
>> > Database Type: ORACLE
>> > Database and Host: 21:16:18:145:1521
>> > Instance/Database: main
>> > User Name: XXXX
>> > Password: XXXXX
>> >
>> >
>> > On Sun, Feb 26, 2012 at 2:48 PM, Karl Wright <daddy...@gmail.com> wrote:
>> >>
>> >> 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, Matthew Parker
>> >> <mpar...@apogeeintegration.com> wrote:
>> >> > 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. Listener refused the connection with the
>> >> > following
>> >> > error.
>> >> >
>> >> > ORA-12514. TNS:Listener does not currently know of service requested
>> >> > in
>> >> > connect descriptor.
>> >> >
>> >> > This might be more of an ORACLE issue than Manifold issue, but I was
>> >> > wondering whether
>> >> > you've encountered the same thing during testing?
>> >> >
>> >> > Regards,
>> >> >
>> >> > Matt
>> >> >
>> >> > On Fri, Jan 20, 2012 at 10:28 AM, Matthew Parker
>> >> > <mpar...@apogeeintegration.com> wrote:
>> >> >>
>> >> >> Thanks Karl.
>> >> >>
>> >> >> On Thu, Jan 19, 2012 at 9:44 PM, Karl Wright <daddy...@gmail.com>
>> >> >> 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 the system classloader, so that's what I was
>> >> >>> forced to insure.
>> >> >>>
>> >> >>> Thanks,
>> >> >>> Karl
>> >> >>>
>> >> >>>
>> >> >>> On Thu, Jan 19, 2012 at 3:33 PM, Karl Wright <daddy...@gmail.com>
>> >> >>> wrote:
>> >> >>> > The ticket for this problem is CONNECTORS-390.
>> >> >>> >
>> >> >>> > Karl
>> >> >>> >
>> >> >>> > On Thu, Jan 19, 2012 at 3:05 PM, Matthew Parker
>> >> >>> > <mpar...@apogeeintegration.com> wrote:
>> >> >>> >> Many thanks. I'll give that a try.
>> >> >>> >>
>> >> >>> >> On Thu, Jan 19, 2012 at 3:01 PM, Karl Wright
>> >> >>> >> <daddy...@gmail.com>
>> >> >>> >> 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'll
>> >> >>> >>> create a ticket for.
>> >> >>> >>>
>> >> >>> >>> A temporary fix, which is slightly involved, requires you to
>> >> >>> >>> put
>> >> >>> >>> the
>> >> >>> >>> ojdbc6.jar in the example/lib area, as you already tried, but
>> >> >>> >>> in
>> >> >>> >>> addition you will need to explicitly include the jar in your
>> >> >>> >>> classpath. Normally the start.jar's manifest describes all the
>> >> >>> >>> jars
>> >> >>> >>> in the initial classpath. I thought it was possible to also
>> >> >>> >>> include
>> >> >>> >>> additional classpath info through the normal --classpath
>> >> >>> >>> mechanism,
>> >> >>> >>> but that doesn't seem to work, so you may be stuck with
>> >> >>> >>> modifying
>> >> >>> >>> the
>> >> >>> >>> root build.xml file to add the jar to the manifest.
>> >> >>> >>>
>> >> >>> >>> I'm going to experiment a bit and see if I can come up with
>> >> >>> >>> something
>> >> >>> >>> quickly.
>> >> >>> >>>
>> >> >>> >>> Karl
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> On Thu, Jan 19, 2012 at 2:48 PM, Karl Wright
>> >> >>> >>> <daddy...@gmail.com>
>> >> >>> >>> 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
>> >> >>> >>> > <mpar...@apogeeintegration.com> 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, 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 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
>> >> >>> >>> >>> <daddy...@gmail.com>
>> >> >>> >>> >>> wrote:
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> 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 try the following:
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> jar -tf ojdbc6.jar | grep "oracle/jdbc/OracleDriver"
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> ... assuming you are using Linux?
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> If the driver class IS found, then the other possibility
>> >> >>> >>> >>>> is
>> >> >>> >>> >>>> that
>> >> >>> >>> >>>> the
>> >> >>> >>> >>>> jar is compiled against a later version of Java than the
>> >> >>> >>> >>>> one
>> >> >>> >>> >>>> you
>> >> >>> >>> >>>> are
>> >> >>> >>> >>>> using to run MCF.
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> Please let me know what you find.
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> Karl
>> >> >>> >>> >>>>
>> >> >>> >>> >>>> On Thu, Jan 19, 2012 at 1:43 PM, Matthew Parker
>> >> >>> >>> >>>> <mpar...@apogeeintegration.com> wrote:
>> >> >>> >>> >>>> > 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 instruction file to use the
>> >> >>> >>> >>>> > ORACLE
>> >> >>> >>> >>>> > driver.
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > I ran "ant build" from the main directory, and restarted
>> >> >>> >>> >>>> > the
>> >> >>> >>> >>>> > example in
>> >> >>> >>> >>>> > dist/example using Jetty.
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > When I setup a connector, MCF throws an exception
>> >> >>> >>> >>>> > stating
>> >> >>> >>> >>>> > that
>> >> >>> >>> >>>> > it
>> >> >>> >>> >>>> > cannot
>> >> >>> >>> >>>> > find oracle.jdbc.OracleDriver class.
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > Looking in the connector-lib directory, the oracle jar
>> >> >>> >>> >>>> > is
>> >> >>> >>> >>>> > there.
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > I also tried placing the ojdbc6.jar in the
>> >> >>> >>> >>>> > dist/example/lib
>> >> >>> >>> >>>> > directory,
>> >> >>> >>> >>>> > but
>> >> >>> >>> >>>> > that didn't fix the problem either.
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > Can anyone point me in the right direction?
>> >> >>> >>> >>>> >
>> >> >>> >>> >>>> > TIA
>> >> >>> >>> >>>> >
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------
>> >> > This e-mail and any files transmitted with it may be proprietary.
>> >> > Please
>> >> > note that any views or opinions presented in this e-mail are solely
>> >> > those of
>> >> > the author and do not necessarily represent those of Apogee
>> >> > Integration.
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Regards,
>> >
>> > Matt Parker (CTR)
>> > Senior Software Architect
>> > Apogee Integration, LLC
>> > 5180 Parkstone Drive, Suite #160
>> > Chantilly, Virginia 20151
>> > 703.272.4797 (site)
>> > 703.474.1918 (cell)
>> > www.apogeeintegration.com
>> >
>> > ------------------------------
>> > This e-mail and any files transmitted with it may be proprietary.
>> > Please
>> > note that any views or opinions presented in this e-mail are solely
>> > those of
>> > the author and do not necessarily represent those of Apogee Integration.
>> >
>
>
>
>
> --
> Regards,
>
> Matt Parker (CTR)
> Senior Software Architect
> Apogee Integration, LLC
> 5180 Parkstone Drive, Suite #160
> Chantilly, Virginia 20151
> 703.272.4797 (site)
> 703.474.1918 (cell)
> www.apogeeintegration.com
>
> ------------------------------
> This e-mail and any files transmitted with it may be proprietary. Please
> note that any views or opinions presented in this e-mail are solely those of
> the author and do not necessarily represent those of Apogee Integration.
>
