Re: ORA-12705 when connecting with 10gR2 JDBC driver

From: Laurenz Albe <invite_at_spam.to.invalid>
Date: 04 Nov 2005 08:42:43 GMT
Message-ID: <1131093761.736143@proxy.dienste.wien.at>

Thomas Kellerer <WVIJEVPANEHT_at_spammotel.com> wrote:

>>>In the meantime I found a workaround, but I'm still not sure what's 
>>>going on. I was setting the system property user.language to en upon 
>>>starting the Java application (to get english "system" dialogs, 
>>>otherwise Swing will honor the language of the OS, which would yield in 
>>>a bi-lingual application). When I remove the -Duser.language=en from the 
>>>command line starting the application, things are working.

>

>> Did you check for NLS_ settings in the environment or registry?

> Yes, they are correct (working fine with SQL*Plus)
>

>> Do you use Instant Client Lite or the NLS-enabled Instant Client?

> No.
>

>> Does it make a difference if you have orai18n.jar in your CLASSPATH?

> Tried that as well, no difference. The only thing to get it working is
> to leave out -Duser.language
>
> I also tried to "synchronize" the NLS_LANG registry setting with
> -Duser.language=en (i.e. setting NLS_LANG to ENGLISH ...) but that
> didn't help as well.

Actually, I found that NLS_ variables should be ignored by Instant Client, so sorry for suggesting to check that. (http://www.oracle.com/technology/tech/oci/instantclient/ic-faq.html#A4432)

What I would do in yur place is to turn on client tracing and try again:

TRACE_DIRECTORY_CLIENT= C:\some\directory TRACE_LEVEL_CLIENT= SUPPORT in sqlnet.ora in your instant client directory.

The generated trace file is rather long, but usually it gives you a clue what is going on and why things are failing.

Yours,
Laurenz Albe Received on Fri Nov 04 2005 - 02:42:43 CST