NLS_TIMESTAMP / NLS_Language

Hi
Am running 11g R1 & 11g R2 and I would like to set the default NLS_TIMESTAMP precision to be 8 digits instead of 6. Had a look around and am now confused as to how to go about this - seems that the default is tied to the language??
Can anybody point me in the right direction?
Steve

From Note 340512.1:
8) What is SYSTIMESTAMP ?
You could say that SYSTIMESTAMP is "sysdate with time zone information added".
SYSTIMESTAMP is the timestamp on the server machine itself and is obtained on Unix platforms by calling " GetTimeOfDay " and on Windows by calling "GetSystemTime" to get the servers local time.
This means that SYSTIMESTAMP, just like SYSDATE depends on Unix platforms on the UNIX time configuration (= Unix TZ variable) for the Unix session when the database and listener where started.
The precision is platform dependant, on most Unix platforms it's microseconds (10-6) on Windows this is Milliseconds (10-3). The output is defined by NLS_TIMESTAMP_TZ_FORMAT in NLS_SESSION_PARAMETERS.
So you can't increase the precision beyond was is given by the platform you are running on ....

Similar Messages

Date(mysql) - date(oracle 8i), java.lang.OutOfMemory

PLATFORM AND O/S VERSION: RedHat Linux 7.2, Kernel 2.4.9-21smp, Oracle 8.1.7.4
MIGRATION WORKBENCH VERSION: 9.2.0.1.2 (Windows 2000, ServicePack 2)
THIRD-PARTY DATABASE AND VERSION BEING MIGRATED: MySQL 3.23.41
Hi there,
I urgently need to migrate a mysql (3.23.41) database (7.1 GB) into Oracle 8i (8-1-7-4),
but faced a lot of problems during migration.(capturing went well):
1. ORA-01843: not a valid month
2. java.lang.OutOfMemoryError
For error no. 1:
Here comes a description of a suspicious source table(mysql), which has a 'datetime' (column: 'created')
in it:
mysql> desc analysisprocess;
-----------------------------------------------------------------------------------+
| Field | Type | Null | Key | Default | Extra |
-----------------------------------------------------------------------------------+
| analysisId | int(10) unsigned | | PRI | NULL | auto_increment |
| created | datetime | | | 0000-00-00 00:00:00 | |
| logic_name | varchar(40) | | | | |
| db | varchar(120) | YES | MUL | NULL | |
| db_version | varchar(40) | YES | | NULL | |
| db_file | varchar(120) | YES | | NULL | |
| program | varchar(80) | YES | | NULL | |
| program_version | varchar(40) | YES | | NULL | |
| program_file | varchar(80) | YES | | NULL | |
| parameters | varchar(80) | YES | | NULL | |
| module | varchar(80) | YES | | NULL | |
| module_version | varchar(40) | YES | | NULL | |
| gff_source | varchar(40) | YES | MUL | NULL | |
| gff_feature | varchar(40) | YES | MUL | NULL | |
-----------------------------------------------------------------------------------+
14 rows in set (0.00 sec)
I tried to map the 'date' datatype from mysql into the date datatype in oracle, but always
got the ora-01843 error.- How can I EXACTLY set 'NLS_DATE_FORMAT'/'NLS_DATE_LANGUAGE' to fit?
Or is there any other solution? (NLS_LANGUAGE is being initialized as 'AMERICAN')
For error no. 2:
I tried using Java 1.3.1 (which comes with omwb) and java 1.4.0_02.
RAM(on notebook running OMWB ): 256 MB; javaw -mx1024m.
Virtual Memory on machine running OMWB: 1024 MB.
Unfortunately, there was now success. What else can I do?
Is there any possibility to have a look at the generated sql (inserts etc.)
during migration?
Your help is highly appreciated. Thanks for your effort in advance.
Best Regards,
Dan
P.S.: I also tried to use Oracle 9i with 'date' to 'timestamp' mapping, but also got 'ora-01843'
error and additionaly:
'Failed to create default for Table :HOMO_SAPIENS_CORE_8_30.ANALYSISPROCESS; ORA-00907: missing right parenthesis'

Hi Dan,
For Error 1:
This is unusual behaviour. I will raise a bug against the product to have it investigated further but I have not encountered this before. To workaround
the problem, you can firstly migrate the database schema (without the data) by choosing the 'No' radio button in 'Step 3 of 4: Migrate Table data' in the
Migration Wizard. When the schema has successfully been migrated you can create SQL*Loader scripts for the table(s) you want to
migrate data for by select the table name in the Oracle Model UI in the Migration Workbench and choosing Object-Generate SQL*Loader Scripts from
the menu bar. To find out more about the offline data loading facility in the Migration Workbench please refer to the MySQL plugin reference guide.Note that
in the 'sql_load_script.bat' (which is one of the files generated by the Object-Generate SQL*Loader Scripts menu command, you can set your specific
requirements for NLS_DATE_FORMAT, NLS_TIMESTAMP, NLS_LANGUAGE etc.I think this will get you over the problem you are encountering at the
moment.
For Error 2:
Could you provide me with the error.log file that exists in your OMWB\Log directory please ? This may contain extra information about the cause of this
problem. Your virtual memory size etc. should be more than adequate. Also, is this problem happening at a particular point in the migration that you can
identify - e.g. on a particular table ? If so, perhaps you could provide me with the datails of the column types of this table, the number of rows of data
it contains etc. In the meantime, the solution to error 1 may actually be a workaround fot this problem too.
If you need any additional information on the above points, please don't hesitate to contact me.
Tom.

Oracle DB Adapter throwing NLS_LANGUAGE' by invoking SP in BPEL Process

Hi,
While i am invoking a Store procedure, the DB Adapter in BPEL process reslting throwing following below error in
<fault>
<bpelFault>
<faultType>0</faultType>
<bindingFault>
<part name="summary">
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'ESOAAdd_DBWraper' failed due to: Stored procedure invocation error. Error while trying to prepare and execute the BPEL_ESOAADD_DBWRAPER.XXEMC_INT_PKG$AR_TRX_PRC API. An error occurred while preparing and executing the BPEL_ESOAADD_DBWRAPER.XXEMC_INT_PKG$AR_TRX_PRC API. Cause: java.sql.SQLException: ORA-20001: Oracle error -20001: ORA-20001: Oracle error -2074: ORA-02074: cannot SET NLS in a distributed transaction has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set_nls. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 245 ORA-06512: at "APPS.FND_GLOBAL", line 1426 ORA-06512: at "APPS.FND_GLOBAL", line 1684 ORA-06512: at "APPS.FND_GLOBAL", line 2309 ORA-06512: at "APPS.FND_GLOBAL", line 2447 ORA-06512: at "APPS.FND_GLOBAL", line 2385 ORA-06512: at "APPS.XXEMC_INT_PKG", line 22 ORA-06512: at "APPS.BPEL_ESOAADD_DBWRAPER", line 620 ORA-06512: at line 1 Check to ensure that the API is defined in the database and that the parameters match the signature of the API. This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-20001" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>ORA-20001: Oracle error -20001: ORA-20001: Oracle error -2074: ORA-02074: cannot SET NLS in a distributed transaction has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set_nls. ORA-06512: at "APPS.APP_EXCEPTION", line 72 ORA-06512: at "APPS.FND_GLOBAL", line 245 ORA-06512: at "APPS.FND_GLOBAL", line 1426 ORA-06512: at "APPS.FND_GLOBAL", line 1684 ORA-06512: at "APPS.FND_GLOBAL", line 2309 ORA-06512: at "APPS.FND_GLOBAL", line 2447 ORA-06512: at "APPS.FND_GLOBAL", line 2385 ORA-06512: at "APPS.XXEMC_INT_PKG", line 22 ORA-06512: at "APPS.BPEL_ESOAADD_DBWRAPER", line 620 ORA-06512: at line 1 </detail>
</part>
<part name="code">
<code>20001</code>
</part>
</bindingFault>
</bpelFault>
</fault>
Can any one gude me to over come from this error.
Thanks,
Srikanth

I believe you are invoking a Standard Seeded API in Oracle EBS. Please use the Oracle Apps Adapter instead of the Database Adapter.
Also, before the API call, make sure you invoke the SET_CLIENT_INFO procedure under the package DBMS_APPLICATION_INFO. While invoking this set client info procedure, you need to pass an input of 0 (zero) . Confirm the same with your EBS Experts in the team.
Also, now when calling the Standard API, you need to pass the credentials in the invoke activity header properties.
look at this link for my suggestions on the same
Re: Error while Uploading PO's into Oracle
Let me know...
Hope this helps,
N

Problems with nls_language

Hi, people!
When I change the NLS_LANGUAGE registry key from US7ASCII to WE8ISO8859P1 Discoverer shows 2 folders with the same name, (one is uppercase and the other is lowercase). The folders' contents are different from each other.
Any ideas?
Thank you!
Fausto

434135.1 How To Find Language (NLS) and Character Information For Oracle Business Intelligence Discoverer 10g (10.1.2)
Sami Malik
[email protected]

ORA-12514 after I Changed NLS_LANGUAGE and cant get into DB

Hello all, I just installed Oracle 10g XE on my Windows XP PC.
I ran this command:
ALTER SYSTEM SET NLS_LANGUAGE = 'AMERICAN_AMERICA.IW8PC1507' SCOPE=SPFILE;
and since then I cant connect to my DB, all i'm getting is:
ORA-12514: TNS:listener does not currently know of service requested in connectdescriptor
I tried to do everything the Oracle 10g libraries says, but they all reffer to the Net Services Administrator's Guide and more stuff that are not supported in the XE.
I cant even see the connect page of the Oracle XE Management!!
please try to help me if you can.

'AMERICAN_AMERICA.IW8PC1507' is an invalid value for NLS_LANGUAGE.
So it is a bug that ALTER SYSTEM doesn't catch the invalid value.
It looks like your database doesn't startup after it is shutdown as you specified SCOPE=SPFILE.
You need to re-create the spfile
create spfile='C:\oraclexe\app\oracle\product\10.2.0\server\dbs/spfileXE.ora' FROM pfile='C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora';
What did you intend to do by executing the alter system command?
Makoto

Problem with NLS_LANGUAGE

I am working on workflow process. I have a problem . I created a workflow process using the Oracle Worflow Builder.
When I try to save it at server I cann't do that because I get the following Error Message :
220: Unable to set NLS_LANGUAGE.
210: Oracle Error: ORA-00942: table or view does not exist. SQL text: SELECT NLS_LANGUAGE FROM WF_LANGUAGES WHERE :l IN (NLS_LANGUAGE, CODE)
I have set the NLS_LANGUAGE='American' and in the registry NLS_LANG=AMERICAN_AMERICA
Please if somebody have any idea about this problem, mail to me [email protected]
Thanks !!!
Marma Teresa Chang

inside the registry there is more than 1 key "NLS_LANG", that belongs to the corresponding ORA_HOME.
Try to find them all and change them to "AMERICAN_AMERICA.WE8ISO8859P1".
hope this helps
Ralf

Nls_language

Hi friends
I was install the oracle database 10g in win2000 server.
By default, the nls_language configurarion is AMERICAN.
I change this parameter throught database control (c:\oracle\product\10.2.0\db_1\bin\spfileorcl10g.ora) to BRAZILIAN PORTUGUESE.
After shutdown and inicialization, i'm connect with system user.
The "show parameters" statement to display nls_language = BRAZILIAN PORTUGUESE, but a "select * from nls_session_parameter" display the nls_language equal to AMERICAN. Why?

Yes.
You may also find the following FAQ on NLS_Lang very useful.
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm#_Toc110410553

Nls_language Please Help

how do i set nls_language to utf8 so it would be initialized when db is started? when i try putting it into init<SID?>.ora i get an error that says: ORA-12700: invalid NLS parameter value (nls_language)
i try doing this init.ora file:
nls_language = utf8
what am i doing wrong?
alex

Hi Hussein,
Thanks a lot. Would follow as suggested.
Now we are struck with issue when performing the following activity,
ACTIVITY:
========
Run Maintain Multi-lingual Tables (AD Administration Main Menu > Maintain Applications Database Entities Menu) using adadmin.
ISSUE:
======
FAILED: file INVNLINS.sql on worker 2 for product inv username INV.
FROM THE LOG : adwork002.log
Start time for file is: Fri Jun 21 2013 15:40:35
sqlplus -s APPS/***** @/opt/gfsd/gfsdappl/inv/11.5.0/sql/INVNLINS.sql
PL/SQL procedure successfully completed.
MESG
LANGUAGE = AMERICAN
PACKAGE= INV_ITEM_PVT
SQLERRM= ORA-01555: snapshot too old: rollback segment number 13 with name "_SYS
SMU13$" too small
select to_date('ERROR')
ERROR at line 1:
ORA-01858: a non-numeric character was found where a numeric was expected
Time when worker failed: Fri Jun 21 2013 23:52:39
QUESTION:
==========
Should we fix this issue before applying synchronization patches?
{OR}
can we proceed with the synchronization patches keeping this issue aside?
Thanks for your help,
Regards,
Rajasekaran.

NLS_Language issue

Hi All,
I have a query which returns 3 rows when run with NLS_Language set to English in SQL Developer, if I change it to American, the query returns 2 rows. Is it possible to apply NLS Language at row level, if so could this row have been altered by a client application with a different NLS_Language setting, I can't how these records could be different, they are coming from an EBS R12 table in an Oracle DB v11.2
Thanks Ed

Hi,
Do you realy expect to get a good answer if you do not post anything like:
Oracle version
sample data
source code of the query you talk about
Regards,
Peter

Nls_language to be set for english stop words to work,10gR2 on Linux

Hi,
When we search a phrase using contains and if the phrase has a stop word in it then the stop word is identified by Oracle depending upon the session language.
When I set the nls_language for the session to AMERICAN, stop word is not being detected and when I set the language to 'ENGLISH', it is being detected.
Is this because the english being refered in the Full Text corresponds to 'ENGLISH' and not 'AMERICAN'.
I guess it should refer to both american and english also.
It would be nice if anyone can clarify this ASAP.
Thanks a lot in advance.

This is what I am trying to do while creating the index,
begin
execute immediate 'drop table text_search';
exception
when others then
null;
end;
create table text_search (content clob, lang varchar2(3) );
insert into text_search values ('Sun rises in the east','eng');
insert into text_search values ('Sun cet evening','fre');
commit;
begin
ctx_ddl.drop_preference('global_lexer');
exception
when others then
null;
end;
begin
ctx_ddl.drop_preference('english_lexer');
exception
when others then
null;
end;
begin
ctx_ddl.drop_preference('french_lexer');
exception
when others then
null;
end;
begin
ctx_ddl.drop_preference('german_lexer');
exception
when others then
null;
end;
begin
ctx_ddl.create_preference('english_lexer','basic_lexer');
ctx_ddl.create_preference('french_lexer','basic_lexer');
ctx_ddl.create_preference('german_lexer','basic_lexer');
ctx_ddl.set_attribute('german_lexer','composite','german');
ctx_ddl.set_attribute('german_lexer','mixed_case','yes');
ctx_ddl.set_attribute('german_lexer','alternate_spelling','german');
end;
begin
ctx_ddl.create_preference('global_lexer', 'multi_lexer');
ctx_ddl.add_sub_lexer('global_lexer','english','english_lexer','eng');
ctx_ddl.add_sub_lexer('global_lexer','french','french_lexer','fre');
ctx_ddl.add_sub_lexer('global_lexer','german','german_lexer','ger');
ctx_ddl.add_sub_lexer('global_lexer','default','english_lexer');
end;
begin
ctx_ddl.drop_preference('mywordlist');
exception
when others then
null;
end;
begin
ctx_ddl.create_preference('mywordlist', 'BASIC_WORDLIST');
ctx_ddl.set_attribute('mywordlist','STEMMER','ENGLISH');
end;
begin
ctx_ddl.drop_stoplist('multistop');
exception
when others then
null;
end;
begin
ctx_ddl.create_stoplist('multistop', 'MULTI_STOPLIST');
ctx_ddl.add_stopword('multistop', 'cet','french');
ctx_ddl.add_stopword('multistop', 'the','english');
ctx_ddl.add_stopword('multistop', 'for','english');
ctx_ddl.add_stopword('multistop', 'all','english');
ctx_ddl.add_stopword('multistop', 'in','english');
end;
begin
execute immediate 'drop index my_text_search_idx';
exception
when others then
null;
end;
CREATE INDEX my_text_search_idx ON text_search(content)
INDEXTYPE IS CTXSYS.CONTEXT
parameters ('datastore ctxsys.direct_datastore filter ctxsys.null_filter lexer global_lexer wordlist mywordlist language column lang stoplist multistop');
while searching:
NLS_LANGUAGE For the session is 'AMERICAN'.
I run the query,
select * from text_search where contains(content,'$"Sun rises in the east"') >0;
gives no result.
I change the session language as below and the query gives the result.
alter session set nls_language = 'english' ;
Same is happening when I tried for different languages.
Please note that we need to maintain a custom stop list containing stop words for multiple languages.

Doubt about nls_language

I don't understand the following situation (I don't undrestand very well how nls_lang parameters work):
I have an 8.1.7. release database on a linux platfrom, these are the language parameters of both the db an the only instance:
CSR>select * from nls_database_parameters;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS ,.
NLS_CHARACTERSET WE8ISO8859P15
CSR>select * from nls_instance_parameters;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
And my problem is the following: I have changed my session parameters in order to being able of writing and reading Spanish characters (I've been told that NLS_CHARACTERSET = WE8ISO8859P15) supports them.
After doing that things are different in my client windows sqlplus than in my linux server sqlplus, so if I do the following, this is what I get:
CLIENT'S WINDOWS SQLPLUS:
CSR>select * from nls_session_parameters;
PARAMETER VALUE
NLS_LANGUAGE SPANISH
NLS_TERRITORY SPAIN
CSR>update ir_ct_sms set ds_sms_v='marketing de campaña navideña' where co_sms_n=44;
1 fila actualizada.
CSR>commit;
Validación terminada.
CSR>select ds_sms_v from ir_ct_sms where co_sms_n=44;
DS_SMS_V
marketing de campaña navideña
SERVER'S LINUX SQLPLUS:
CSR>select * from nls_session_parameters;
PARAMETER VALUE
NLS_LANGUAGE SPANISH
NLS_TERRITORY SPAIN
CSR>update ir_ct_sms set ds_sms_v='marketing de campaña navideña' where co_sms_n=44;
1 fila actualizada.
CSR>commit;
Validacion terminada.
CSR>select ds_sms_v from ir_ct_sms where co_sms_n=44;
DS_SMS_V
marketing de campa?a navide?a
I don't understand why I can write the character 'ñ' but I can't read it on the server.
Can someone tell my what the problem is about ?

If the NLS_LANG of the client is different than the character set of the database, Oracle has to perform a character set transform. In this case, however, since both ISO-8859-1 and ISO-8859-15 define the tilde-n character, it shouldn't cause a problem.
It is entirely possible, however, that telnet clients may understand the ISO-8859-15 character set and may not support the ISO-8859-1 character set. Setting NLS_LANG to ISO-8859-15 may well be a requirement for your telnet applications, but it is not an Oracle requirement. I'm sure there are telnet applications out there that support ISO-8859-1.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

ORA-20001: Oracle error -20001: ORA-20001: Oracle error -14552: ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set

ORA-20001: Oracle error -20001: ORA-20001: Oracle error -14552: ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML has been detected in fnd_global.set_nls.set_parameter('NLS_LANGUAGE','AMERICAN'). has been detected in fnd_global.set_nls.
this error generates everytime when i run a apex application
i did call the package in session state with dbms_session.set_nls('NLS_LANGUAGE','AMERICAN'); but still it shows the error in the report any solution please

Hi Amrit
Can you put the FND_GLOBAL calls in a pre map trigger/process rather than as part of the map?
Cheers
David

DB의 nls_language,nls_territory 값

Unix 환경 변수 : NLS_LANG=KOREAN_KOREA.KO16KSC5601 로 셋업되어 있는데, 데이터베이스의 lanuage와 territory는
AMERICAN, AMERICA 로 되어 있습니다.
CHARACTER SET 만 한글이 들어갈 수 있게 셋업되어 있으면 해당 값은 크게 의미가 없나요?
그리고 show parameter 시 나오는 값과 nls_database_parameters 에서 조회되는 값이 다른데 같게 맞춰줘야 하는지, 그렇다면 어떻게 해야 하는지 알려주세요~
show parameter 시
-. nls_language : AMERICAN
-. nls_territory : AMERICA
select * from nls_database_parameters;
-. nls_lanuage : KOREAN
-. nls_territory : KOREA
-. nls_characterset : AL32UTF8
입니다.
글 수정: user10795508

SQL> select * from nls_instance_parameters;
PARAMETER VALUE
NLS_LANGUAGE GERMAN
NLS_TERRITORY GERMANY
Sorry :-)
Now i found an interesting metalink-doc (ID 241047.1), which says:
"You really need to do a "create database", if you use the DBCA and use a "seed" database (= included datafiles in page 2) then the NLS_DATABASE_PARAMETERS will be AMERICAN AMERICA seen this is actually a clone operation of a existing database (who is using AMERICAN AMERICA), not a real "create database". Seen NLS_INSTANCE_PARAMTERS take precedence this is not a problem at all and simply irrelvant."
What does this mean? How can i avoid to clone a database and really do a new "create database" over the dbca gui?
Edited by: user1435412 on 12.08.2009 05:21

220: Unable to set NLS_LANGUAGE. Oracle Workflow Builder

Hi All,
When i am trying to login to OWF Builder its throwing error:
220: Unable to set NLS_LANGUAGE.
210: Oracle Error: ORA-00942: table or view does not exist
. SQL text: SELECT NLS_LANGUAGE FROM WF_LANGUAGES WHERE :l IN (NLS_LANGUAGE, CODE)I already referred:
Problem with NLS_LANGUAGE
*MOS tech note : 220:Unable To Set NLS_LANGUAGE Error In Workflow Builder [ID 728330.1]*
and other related threads.
All values in registry are correct as per DB NLS settings
Here the strange thing is i am able to login with apps account its not giving this error and when i am trying to login with another custom db account its throwing error.
I even granted select, insert, update privilege on WF_LANGUAGES view to custom db user still same issue.
Any pointers on this issue is really appreciated.
Many thanks in advance.
regards,
X A H E E R

Hi helios,
Many thanks for your input.
Did you check note Error While Connecting To Database Using The Workflow Builder [ID 577905.1]? After you follow note 220:Unable To Set NLS_LANGUAGE Error In Workflow Builder [ID 728330.1] did you restart machine?yes, i restarted my PC and the tech note provides the same solution from tech note *577905.1* as i updated in my earlier post.
If its the problem of NLS_LANG then it should not allow me login with apps also right??
But i can login with apps without any issues.
thanks,
X A H E E R

NLS_LANGUAGE - Canadian French

Hi,
does someone know what is the problem or status concerning the acceptance of "Canadian French" in ORACLE 9i Release 2 (9.2).
We were using 9.0.1 database and a simple command like:
alter session set nls_language='canadian french';
was working fine but since we migrate to 9.2 (9.2.0.3 and now 9.2.0.4) CANADIAN FRENCH always give us errors like:
ORA-12705: invalid or unknown NLS parameter value specified
Is there any patch to apply either on 9.2.0.3 or 9.2.0.4 ?
Any help would be appreciated
Sylvain

The bug is fixed in the upcoming 10g release. I have requested a backport. It will be part of 9.205. I don't know when this patch will be made available.

NLS_TIMESTAMP / NLS_Language

Similar Messages

Maybe you are looking for