Nls Error Detected Oracle

Library mySQL Code Library PHP Code Library JavaScript Code Library Oracle Terms & Definitions Oracle Error Codes PSOUG Community Blogs Oracle Jobs Board PSOUG Forum Oracle User Group Directory Free Oracle Magazines Online Learning Center PSOUG Presentations Advanced Code Search News and Events Sponsors Page Submit Code Contact Us Oracle Error: ORA-01890 Error Description: NLS error detected Error Cause: An NLS error was detected. Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support. There haven't been any comments added for this error yet. You may add one if you like. Add a comment Name: Email: URL: Chars left:1000 (1000 max) (No HTML, but newlines will be preserved) Home : Code Library : Sponsors : Privacy : Terms of Use : Contact Us 206 users online © 2009 psoug.org PSOUG LOGIN Username: Password: Forgot your password?

Tue, 11 November 2003 23:57 Aescoline S Messages: 2Registered: November 2003 Junior Member ORA-01890: NLS error detected > > We are pick up the business date from our > application table and appending the timestamp. > > select to_date(to_char(bsns_dt,'DD-MON-YYYY') > ||' '||to_char(sysdate,hh24:mi'),'DD-MON-YYYY hh24:mi') from appln_table > > This select statement works fine at times > and at times it is throwing error 01890. > The error is not consistent. > This does not happen in our http://psoug.org/oraerror/ORA-01890.htm SIT environment. > But is happening in UAT environment. Basically two > different machine with the same configuration. > Please let us know how we can resolve this problem. Report message to a moderator Re: ORA-01890: NLS error detected [message #27920 is a reply to message #27914] Wed, 12 November 2003 04:08 ramana http://www.orafaq.com/forum/t/9913/ Messages: 51Registered: December 2000 Member > select to_date(to_char(bsns_dt,'DD-MON-YYYY') > ||' '||to_char(sysdate,hh24:mi'),'DD-MON-YYYY hh24:mi') from appln_table in ur query there is no single quote before hh24:mi > select to_date(to_char(bsns_dt,'DD-MON-YYYY') > ||' '||to_char(sysdate,**********hh24:mi'),'DD-MON-YYYY hh24:mi') from appln_table Report message to a moderator Re: ORA-01890: NLS error detected [message #27944 is a reply to message #27920] Thu, 13 November 2003 03:24 Aescoline S Messages: 2Registered: November 2003 Junior Member Sorry, that was a typographical error. When the query is run in the sql prompt the format we get after the execution of the query is : DD-MON-YY eg. '13-NOV-03' Report message to a moderator Re: ORA-01890: NLS error detected [message #228023 is a reply to message #27914] Fri, 30 March 2007 14:12 login100 Messages: 1Registered: March 2007 Junior Member It is an oracle bug. Request a patch from Oracle Support. We had the same issue on some oracle servers and that was the way we fixed it. Report message to a moderator

November 11, 2013 - 9:31 am UTC Category: Database � Version: 8.1.6 and 7.3.4 Latest Followup You Asked Hi TOM, Some question on Character set and NLS. 1) What is the different between US7ASCII and WE8ISO8859P1 character set and NLS? 2) Is there any problem for the https://asktom.oracle.com/pls/asktom/f?p=100:11:0%3A%3A%3A%3AP11_QUESTION_ID:1224836384599 DB with two diferrent character sets to interact, - trigger - dblink - export and import accross the DB. 3) In your opinion, which is more popular or "flexible", US7ACII or WE8ISO8859P1. 4) I have dbs with US7ASCII and WE8ISO8859P1, do I need to worry ? Thanks in advance for you response. robert and we said... 1) will NLS is national language support and encompasses lots of things like how to display currency, whether we use a comma or nls error a dot to separate numbers, how the name of a day is spelled and so on. character sets are how we store data. US7ASCII for example is a 7bit character set, the high bit is "stripped". The WE8ISO8859P1 is the standard western european 8 bit character set. It can store 2 times as many characters as the 7bit one can (special characters with umlats and such). 2) there are no "problems" just considerations. If I export from an 8bit database nls error detected and import into a 7bit -- I'll undergo a characterset conversion. My 7bit databasebase cannot store any 8bit characters, they will be mapped into the 7bit characterset (eg: the data will be DIFFERENT, I'll lose some characters that have the high bit set, they'll become some other character based on the rules for converting 8bit to 7bit). Going the other way, from 7bit to 8bit won't encounter any issues since the 7bit US7ASCII is a subset of the 8bit WE8ISO8859P1. You must consider this when using multiple charactersets. The strings will be converted from one to the other and you may "lose" some characters. 3) neither is more popular or flexible. They both do exactly what they do. the 8bit can hold more types of characters so unless you are doing a US only application, 8bit might be more appropriate. I've taken to creating all of my databases with 8bit now as I must support many countries and they get upset when we lose their special characters. 4) cannot answer that for you. It depends on what you put in there. You can convert the US7ASCII into WE8ISO8859P1 with later releases of Oracle (not 7.3, do not believe the functionality was implemented then). See the NLS guide, chapter 3 for details: http://download-east.oracle.com/docs/cd/A81042_01/DOC/server.816/a76966/ch3.htm#47136 actually, you may want to read through the entire document as it answers your questions directly in greater detail then I can here: http://download-east.or