Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: ORA-12705 when connecting with 10gR2 JDBC driver

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

From: Thomas Kellerer <WVIJEVPANEHT_at_spammotel.com>
Date: Thu, 03 Nov 2005 12:25:13 +0100
Message-ID: <3suacqFq7k90U1@individual.net>


On 03.11.2005 12:05 Laurenz Albe wrote:

> Thomas Kellerer <WVIJEVPANEHT_at_spammotel.com> wrote:
> 

>>when I try to connect to an Oracle 9.2 database using the Oracle 10g R1
>>JDBC thin driver, everything is working fine, but when I use the Oracle
>>10g R2 (thin) driver I get the following error:
>>
>>ORA-00604: error occurred at recursive SQL level 1
>>ORA-12705: invalid or unknown NLS parameter value specified
>>
>>Any ideas why the connection does not work with the R2 driver?
>>
>>I do have an Oracle 9.2 client installed on my computer (WinXP), but the
>>thin driver should not use any of the Oracle client software (or
>>registry settings), right?
> 
> 
> I am not certain about the registry settings, but environment variables
> will definitly be honoured by Instant Client.

The thin client theoretically does not require *any* client installation. So I'm a bit confused why it should use environment settings at all.

> - Are there any environment variables whose name begin with NLS_ ?
> - Are any such registry entries set?
> 
> If that is not the problem, please tell us at what point exactly you
> encounter the problem. When you connect to the database?
> Which JDBC statement causes the error message?

It's upon connecting to the database, basically

DriverManager.getConnection() is throwing this error.

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.

Regards
Thomas Received on Thu Nov 03 2005 - 05:25:13 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US