jdbc connections

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

jdbc connections

French, Shelane
Any one familiar with using JDBC connections will Lasso?

I am setting up a new VM running Lasso 8.6.3 on Linux RHEL 6.5. We are migrating from Linux RHEL 5 with Lasso 8.5.6. I copied the JDBC drivers I had. I set up all the settings the same. I can see the Oracle schema, but when I go to look at the databases, it says the database is unavailable.

I'm seeing errors like this in the JDBCLog.txt file:

[11/17/15 10:22:25] Action exec time: 1494 msec
[11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
[11/17/15 10:22:29] Action exec time: 0 msec
[11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
[11/17/15 10:22:29] Catalog:  null
[11/17/15 10:22:29] Action exec time: 2 msec
[11/17/15 10:22:29] > Executing TAG_PROPERTY_INFO...
[11/17/15 10:22:29] Action exec time: 0 msec
[11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
[11/17/15 10:22:29] Action exec time: 0 msec
[11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
[11/17/15 10:22:29] Action exec time: 0 msec
[11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
[11/17/15 10:22:29] Catalog:  null


I am also considering trying to get the instant client installed and set up to use the "native connector" for Oracle.

Anyone with ideas?


[cid:5AFC2063-C3A4-4D91-8A0C-12C6F16568EC]
Shelane French
Workforce Enablement
Livermore Information Technology


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: jdbc connections

Mason Miller
Are the credentials in the database IP based?

Mason

> On Nov 17, 2015, at 1:52 PM, French, Shelane <[hidden email]> wrote:
>
> Any one familiar with using JDBC connections will Lasso?
>
> I am setting up a new VM running Lasso 8.6.3 on Linux RHEL 6.5. We are migrating from Linux RHEL 5 with Lasso 8.5.6. I copied the JDBC drivers I had. I set up all the settings the same. I can see the Oracle schema, but when I go to look at the databases, it says the database is unavailable.
>
> I'm seeing errors like this in the JDBCLog.txt file:
>
> [11/17/15 10:22:25] Action exec time: 1494 msec
> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
> [11/17/15 10:22:29] Action exec time: 0 msec
> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
> [11/17/15 10:22:29] Catalog:  null
> [11/17/15 10:22:29] Action exec time: 2 msec
> [11/17/15 10:22:29] > Executing TAG_PROPERTY_INFO...
> [11/17/15 10:22:29] Action exec time: 0 msec
> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
> [11/17/15 10:22:29] Action exec time: 0 msec
> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
> [11/17/15 10:22:29] Action exec time: 0 msec
> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
> [11/17/15 10:22:29] Catalog:  null
>
>
> I am also considering trying to get the instant client installed and set up to use the "native connector" for Oracle.
>
> Anyone with ideas?
>
>
> [cid:5AFC2063-C3A4-4D91-8A0C-12C6F16568EC]
> Shelane French
> Workforce Enablement
> Livermore Information Technology
>
> #############################################################
>
> This message is sent to you because you are subscribed to
>  the mailing list Lasso [hidden email]
> Official list archives available at http://www.lassotalk.com
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>



#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: jdbc connections

French, Shelane
I've been told it is not IP restricted.



Here are differences we are seeing in the logs between the server that's
working and the one that's not.


broken: oracle.jdbc.driver.OracleDriver properties: separator=
quote_char=         terminator=         use_schema=false
use_catalogs=false         can_convert=false

working: oracle.jdbc.OracleDriver properties:        separator=.
quote_char="         terminator=         use_schema=true
use_catalogs=false         can_convert=false


The use_schema setting is different. I'm not sure where that is set. I
don't see these settings in Lasso Admin.



On 11/17/15, 11:15 AM, "[hidden email] on behalf of
Mason Miller" <[hidden email] on behalf of
[hidden email]> wrote:

>Are the credentials in the database IP based?
>
>Mason
>
>> On Nov 17, 2015, at 1:52 PM, French, Shelane <[hidden email]> wrote:
>>
>> Any one familiar with using JDBC connections will Lasso?
>>
>> I am setting up a new VM running Lasso 8.6.3 on Linux RHEL 6.5. We are
>>migrating from Linux RHEL 5 with Lasso 8.5.6. I copied the JDBC drivers
>>I had. I set up all the settings the same. I can see the Oracle schema,
>>but when I go to look at the databases, it says the database is
>>unavailable.
>>
>> I'm seeing errors like this in the JDBCLog.txt file:
>>
>> [11/17/15 10:22:25] Action exec time: 1494 msec
>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>> [11/17/15 10:22:29] Action exec time: 0 msec
>> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
>> [11/17/15 10:22:29] Catalog:  null
>> [11/17/15 10:22:29] Action exec time: 2 msec
>> [11/17/15 10:22:29] > Executing TAG_PROPERTY_INFO...
>> [11/17/15 10:22:29] Action exec time: 0 msec
>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>> [11/17/15 10:22:29] Action exec time: 0 msec
>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>> [11/17/15 10:22:29] Action exec time: 0 msec
>> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
>> [11/17/15 10:22:29] Catalog:  null
>>
>>
>> I am also considering trying to get the instant client installed and
>>set up to use the "native connector" for Oracle.
>>
>> Anyone with ideas?
>>
>>
>> [cid:5AFC2063-C3A4-4D91-8A0C-12C6F16568EC]
>> Shelane French
>> Workforce Enablement
>> Livermore Information Technology
>>
>> #############################################################
>>
>> This message is sent to you because you are subscribed to
>>  the mailing list Lasso [hidden email]
>> Official list archives available at http://www.lassotalk.com
>> To unsubscribe, E-mail to: <[hidden email]>
>> Send administrative queries to  <[hidden email]>
>
>
>
>#############################################################
>
>This message is sent to you because you are subscribed to
>  the mailing list Lasso [hidden email]
>Official list archives available at http://www.lassotalk.com
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: jdbc connections

French, Shelane
The infrastructure team updated the driver to an ojdbc6.jar file and we
are able to connect again.



Shelane French
Workforce Enablement
Livermore Information Technology




On 11/17/15, 11:59 AM, "[hidden email] on behalf of
French, Shelane" <[hidden email] on behalf of
[hidden email]> wrote:

>I've been told it is not IP restricted.
>
>
>
>Here are differences we are seeing in the logs between the server that's
>working and the one that's not.
>
>
>broken: oracle.jdbc.driver.OracleDriver properties: separator=
>quote_char=         terminator=         use_schema=false
>use_catalogs=false         can_convert=false
>
>working: oracle.jdbc.OracleDriver properties:        separator=.
>quote_char="         terminator=         use_schema=true
>use_catalogs=false         can_convert=false
>
>
>The use_schema setting is different. I'm not sure where that is set. I
>don't see these settings in Lasso Admin.
>
>
>
>On 11/17/15, 11:15 AM, "[hidden email] on behalf of
>Mason Miller" <[hidden email] on behalf of
>[hidden email]> wrote:
>
>>Are the credentials in the database IP based?
>>
>>Mason
>>
>>> On Nov 17, 2015, at 1:52 PM, French, Shelane <[hidden email]> wrote:
>>>
>>> Any one familiar with using JDBC connections will Lasso?
>>>
>>> I am setting up a new VM running Lasso 8.6.3 on Linux RHEL 6.5. We are
>>>migrating from Linux RHEL 5 with Lasso 8.5.6. I copied the JDBC drivers
>>>I had. I set up all the settings the same. I can see the Oracle schema,
>>>but when I go to look at the databases, it says the database is
>>>unavailable.
>>>
>>> I'm seeing errors like this in the JDBCLog.txt file:
>>>
>>> [11/17/15 10:22:25] Action exec time: 1494 msec
>>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>>> [11/17/15 10:22:29] Action exec time: 0 msec
>>> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
>>> [11/17/15 10:22:29] Catalog:  null
>>> [11/17/15 10:22:29] Action exec time: 2 msec
>>> [11/17/15 10:22:29] > Executing TAG_PROPERTY_INFO...
>>> [11/17/15 10:22:29] Action exec time: 0 msec
>>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>>> [11/17/15 10:22:29] Action exec time: 0 msec
>>> [11/17/15 10:22:29] > Executing TAG_DRIVER_INFO...
>>> [11/17/15 10:22:29] Action exec time: 0 msec
>>> [11/17/15 10:22:29] > Executing ACTION_DB_NAMES:
>>> [11/17/15 10:22:29] Catalog:  null
>>>
>>>
>>> I am also considering trying to get the instant client installed and
>>>set up to use the "native connector" for Oracle.
>>>
>>> Anyone with ideas?
>>>
>>>
>>> [cid:5AFC2063-C3A4-4D91-8A0C-12C6F16568EC]
>>> Shelane French
>>> Workforce Enablement
>>> Livermore Information Technology
>>>
>>> #############################################################
>>>
>>> This message is sent to you because you are subscribed to
>>>  the mailing list Lasso [hidden email]
>>> Official list archives available at http://www.lassotalk.com
>>> To unsubscribe, E-mail to: <[hidden email]>
>>> Send administrative queries to  <[hidden email]>
>>
>>
>>
>>#############################################################
>>
>>This message is sent to you because you are subscribed to
>>  the mailing list Lasso [hidden email]
>>Official list archives available at http://www.lassotalk.com
>>To unsubscribe, E-mail to: <[hidden email]>
>>Send administrative queries to  <[hidden email]>
>
>
>#############################################################
>
>This message is sent to you because you are subscribed to
>  the mailing list Lasso [hidden email]
>Official list archives available at http://www.lassotalk.com
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>


#############################################################

This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>