3 Replies Latest reply on Jun 5, 2014 7:04 AM by 1007321

Cman doesn't like Jdbc thin driver connect strings, does it ?

1007321 Jun 4, 2014 3:08 PM

Hello,

I'm using Oracle Connection Mgr 11.2 to filter my clients access to databases.

I've configured and allowed a PC to connect to a certain database, and when

using SQL*Plus or Toad from this client, going thru cman, it works fine.

But now the same guy has installed SQL Developer and it seems *impossible*

to perform connections thru my cman server, they get systematically rejected

with

ORA-12529, TNS:connect request rejected based on current filtering rules

whether I try to go thru the TNS option connection (which does work with

sqlplus...) or thru Advanced => and then setting "jdbc:oracle:thin@<complete TNS block>" !

(using the 'Basic' option seems not possible as it only enables to specify hostname, port and SID...)

Has anybody ever encountered this issue before ? How come SQL Developer gets rejected

even when you use the TNS option, that otherwise works fine with sqlplus/Toad ?

And is there a way to have a Jdbc thin connect string go thru a cman configuration ?

Thanks a lot in advance for any hint...

Regards,

Seb

1. Re: Cman doesn't like Jdbc thin driver connect strings, does it ?

Gary Graham-Oracle Jun 4, 2014 5:03 PM (in response to 1007321)

Not a familiar subject for me, but I ran across a note in the JDBC Developer's Guide and Reference, Advanced Topics, about setting AUTHENTICATION_LEVEL=0 in the cman_profile entry of the cman.ora file for when JDBC Thin is in use. Not sure if using old 10g doc is valid here, but I suppose checking it out couldn't hurt:
23 Advanced Topics

Alternately, since this user has an Oracle client installed on the PC and used SQL*Plus, you might try the OCI/Thick JDBC driver. Enable OCI/Thick via...

Tools > Preferences > Datatbase > Advanced > Use OCI/Thick check box

Also, for SQL Developer 4.0.x, the Advanced preferences includes this to point to a specific Oracle client install...

Use Oracle Client check box

Configure...

Hope this helps,
Gary
SQL Developer Team

Message was edited by: Gary Graham
Like Show 0 Likes(0)

Actions
2. Re: Cman doesn't like Jdbc thin driver connect strings, does it ?

rp0428 Jun 4, 2014 8:41 PM (in response to Gary Graham-Oracle)

I ran across a note in the JDBC Developer's Guide and Reference, Advanced Topics, about setting AUTHENTICATION_LEVEL=0 in the cman_profile entry of the cman.ora file for when JDBC Thin is in use. Not sure if using old 10g doc is valid here, but I suppose checking it out couldn't hurt:
The current doc has the same topic
http://docs.oracle.com/cd/E16655_01/java.121/e17657/jdbcthin.htm#sthref279

Interestingly this is another one of those occasions when Oracle seems to have removed useful, if not vital, information,. The new docs after 10g make no mention of the need for level 0 although the example code still shows it.
Like Show 0 Likes(0)

Actions
3. Re: Cman doesn't like Jdbc thin driver connect strings, does it ?

1007321 Jun 5, 2014 7:04 AM (in response to 1007321)

Beautiful. Thanks a lot. I only replaced "thin" with "oci" in the connect string, now my connections are not rejected any longer.
Seb
Like Show 0 Likes(0)

Actions

Go to original post