Re: NLS params difference

I know what you mean and this is all true unless you bounce your database after issuing: "alter system set nls_length_semantics='CHAR' scope=both;" I restarted this DB many times after that. I changed it manually in init.ora file... I created spfile from this pfile, bounced it again and it still shows the different values. Not really sure why.... And even more, if the 'show param bla" gives me the value for current session, then nls_database_parameters should have prefenrences... But all my tables, that had VARCHAR2(9) now have VARCHAR2(9 CHAR).. That leads me to think that I am good and the sematics is CHAR, but I still have doubts..

Thanks,
M

[oracle_at_tds dbs]$ cat initprod8.ora | grep nls_length* *.nls_length_semantics='CHAR'

On Wed, Jul 22, 2009 at 3:12 PM, Maxim Demenko <mdemenko_at_gmail.com> wrote:

> Maria Gurenich schrieb:
>
> Please, define "normal" ;-)
> The difference in the parameter can be easily explained - whether it meets
> you expectation - it is up to you...
> nls_database_parameters shows values for different nls settings which were
> valid for the session at the timepoint of database creation ( either default
> values or set explicitly in the session).
> Show parameter give you values valid for current session, which can be
> easily changed ( for example per logon trigger), so values can differ.
>
> Best regards
>
> Maxim
>
> Hi people.
>> Please, tell me what am I missing here? Did I forget something? I am not
>> sure I am following, why it is:
>>
>> 14:40:48 db_manager_at_prod8> select * from NLS_DATABASE_PARAMETERS where
>> parameter='NLS_LENGTH_SEMANTICS';
>>
>> PARAMETER VALUE
>> ------------------------------
>> ---------------------------------------------------------------------------------------
>> *NLS_LENGTH_SEMANTICS BYTE*
>>
>> Elapsed: 00:00:00.01
>> 14:41:34 db_manager_at_prod8> show parameter NLS_LENGTH_SEMANTICS
>>
>> NAME TYPE VALUE
>> ------------------------------------ -----------
>> ------------------------------
>> *nls_length_semantics string CHAR*
>>
>> Oracle 10.2.0.4, NLS_NCHAR_CHARACTERSET=AL16UTF16
>>
>> Is this normal?
>>
>> Thanks,
>> M
>>
>
>
> --
> Why make things difficult, when it is possible to make them cryptic
> and totally illogical, with just a little bit more effort?
>
> Aksel Peter Jørgensen
>
>

--
http://www.freelists.org/webpage/oracle-l