Jdbc insert fails with 01722: invalid number but sqlplus doesn't

Question

I am experiencing a 01722: invalid number on a remote system in Canada. Initially, I couldn't insert '0.0' into a number field, but after changing the ...Oracle/HOME0 ... registry value from ENGLISH_CANADA.WE8MSWIN1252 to AMERICAN_AMERICA.WE8MSWIN1252 and recycling the App Server (Oracle client) I was able to insert '0.0' into a number field.
But my java app using JDBC had the same error "ORA-01722: invalid number" occurring for the same table and attribute -- only this time -- when I attempted to manually insert the same insert '0.0' into a number field -- it worked via SQLPlus.
The NLS_Lang is set to AMERICAN_AMERICA.WE8MSWIN1252.
I confirmed that the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage\ACP value is 1252.
Assuming a theory that maybe it is a setting on the DB Server, I tried reproducing this problem locally in my lab configuration by setting the NLS_Lang registry value to ENGLISH_CANADA.WE8MSWIN1252. I used the same jdbc test app to issue the insert....but it worked.
--- Any advice on what other configuration changes could influence the number data type or whether it is possibly a DB Server setting instead of client -- would be greatly appreciated.

Answer 1

JDBC does not care about NLS_LANG. It takes the Java default locale, maps it to Oracle language/territory pair and sends to the server.
Just try this:
Statement stmt = conn.createStatement();
stmt.execute( "ALTER SESSION SET NLS_NUMERIC_CHARACTERS='.,'" );
or bind numeric datatypes.
-- Sergiusz