Re: NLS_DATE_FORMAT not working on PC

From: <alistair.thomson_at_sphinxcst.co.uk>
Date: Thu, 06 Jan 2000 16:49:38 GMT
Message-ID: <852h2r$26t$1@nnrp1.deja.com>

Yep the client settings override the server settings! Try adding the nls entry into the registry on the client and all should be well.

In article <851qu7$i16$1_at_nnrp1.deja.com>, mbraund_at_my-deja.com wrote:
> I have an Oracle V7 database with nls_date_format parameter set
to 'DD-
> MON-RR'.
>
> When accessing the database through the Solaris SQL*Plus application
> this behaves as expected :
>
> 01-DEC-99 is stored as 01-DEC-1999
> 01-JAN-00 is stored as 01-JAN-2000
>
> When accessing the same database with the same userid through the PC
> SQL*Plus client through SQL Net I get the following :
>
> 01-DEC-99 is stored as 01-DEC-2099
> 01-JAN-00 is stored as 01-JAN-2000
>
> Selecting from nls_session_parameters reveals NLS_DATE_FORMAT = 'DD-
MON-
> YY' while selecting from nls_instance_parameters reveals
> NLS_DATE_FORMAT = 'DD-MON-RR'
>
> Doing an explicit ALTER SESSION to set the nls_date_format yields the
> correct results.
>
> Why is the PC access not working by default ? Is the database
parameter
> being overridden ?
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Thu Jan 06 2000 - 10:49:38 CST