Character set issue after import?

Hi,
Source DB version:10.2.0.1
OS:Red hat Linux
Target DB version:10.2.0.1
OS:Windows server
source database character set:AL32UTF8
Performed the export as below
$export NLS_LANG=AMERICAN.AL32UTF8
Performed the full database export and it finished successfully with out any warnings
Export done in AL32UTF8 character set and AL16UTF16 NCHAR character set
Now imported into the target database as below.
target database character set:AL32UTF8
c:\>set NLS_LANG=AMERICAN.AL32UTF8
now run import command which imported successfully with out any warnings.
However I’m having problems with Greek characters. Most of them are shown as ?, while some of them are converted to Latin chars
For example:
This was supposed to be Αγγελική ???e????
And this Κουκουτσάκη ??????ts???
While this one should be Δήμητρα ??µ?t?a
From the import log file I can see that ‘import done in AL32UTF8 character set and AL16UTF16 NCHAR character set’ which I believe is correct.
Can any one tell me how i can over come this problem of greek charecters.
Thank you all.

PARAMETER
VALUE
NLS_LANGUAGE
AMERICAN
NLS_TERRITORY
AMERICA
NLS_CURRENCY
$
PARAMETER
VALUE
NLS_ISO_CURRENCY
AMERICA
NLS_NUMERIC_CHARACTERS
NLS_CHARACTERSET
AL32UTF8
PARAMETER
VALUE
NLS_CALENDAR
GREGORIAN
NLS_DATE_FORMAT
DD-MON-RR
NLS_DATE_LANGUAGE
AMERICAN
PARAMETER
VALUE
NLS_SORT
BINARY
NLS_TIME_FORMAT
HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT
DD-MON-RR HH.MI.SSXFF AM
PARAMETER
VALUE
NLS_TIME_TZ_FORMAT
HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT
DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY
$
PARAMETER
VALUE
NLS_COMP
BINARY
NLS_LENGTH_SEMANTICS
BYTE
NLS_NCHAR_CONV_EXCP
FALSE
PARAMETER
VALUE
NLS_NCHAR_CHARACTERSET
AL16UTF16
NLS_RDBMS_VERSION
10.2.0.1.0
20 rows selected.

Similar Messages

SCCM/WSUS issue after importing March CSA patch bundle

Hi, I am having an issue with security patch deployment since Tuesday night. Debugging is ongoing. I am running SCCM 2012 CU2.
Coincidentally, the problem appeared shortly after importing the March XP CSA (Custom Support Agreement) patch bundle into SCCM. From the client end, WUAHandler.log reported continuous failures/retries. On lower-end machines, system performance
became very poor. From the server end, starting up the Windows Server Update Services mmc (yes, I know you're not supposed to be doing anything in here, which I'm not) results in a connection error. The detailed error message is shown further down.
It was difficult to get the client machines to stop "thrashing" per WUAHandler.log. It wasn't until I de-installed/re-installed WSUS and ASP.NET that things quieted down yesterday afternoon. All appeared to be stable until this morning
when I re-added "Windows XP Custom Support" under the SUP Component Properties tab, imported the CSA bundle info, initiated a CAB synchronization from Microsoft, and re-enabled Software Updates on the clients.
Again, I would get the error when starting up the Windows Server Update Services mmc.
I am doing everything again, but this time one step at a time. My working theory is that there is some kind of corruption caused by the CSA import (this worked just fine up until Feb.). A few hours ago, Microsoft published a new CSA
patch bundle because a patch was apparently forgotten. Is it possible that there was some kind of corruption included with the original bundle published on Tuesday?
I will post what I find as a result of my debugging.
Thanks,
Nick.
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
System.IO.IOException -- The handshake failed due to an unexpected packet format.
Source
System
Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **
System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
Source
Microsoft.UpdateServices.Administration
Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpandFromLoad(SyncStatus status)

Yes, WCM.log showed the same 503 error starting on the Wednesday morning at 2:53am, and I also noticed wsuspool had stopped. My most noticeable symptom was the thrashing of wuahandler.log on the clients, causing poor system performance on machines with 2gb
of memory. Multiple de-installs/re-installs of WSUS failed to clear the issue until we increased the memory setting in IIS.
Nick
WCM.log:
System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String
ServerName, Boolean UseSSL, Int32 PortNumber) $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.225+240><thread=30872 (0x7898)>
Remote configuration failed on WSUS Server.~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-11-2015 02:53:26.226+240><thread=30872 (0x7898)>

Oracle 10g db character set issue

I have a database 10g with database character set western
european "WE8ISO8859P1" and we are receiving data from source
database with database character set as "UTF8" during data load
for one of the tables we receive the following error "ORA-29275:
partial multibyte character" I understand this might be due to
the fact western european character set is not a subset/superset
of UTF8 .Am i right ? What would be the way around this ?

It is certainly possible that the issue is that your database characterset is a subset of UTF8.
How are you getting the data? Are we talking about a flat file? A query over a database link? Something else?
Does the data you're getting contain characters that cannot be represented in the ISO-8859 1 character set? It is quite common to send UTF-8 encoded files even when the underlying data is representable in other 8-bit character sets (like ISO-8859 1).
What are you trying to do with the data? Are you trying to load it into a CHAR/ VARCHAR2 column? A CLOB? A BLOB? An NCHAR/ NVARCHAR2? Something else?
Justin

Character Set issues. Please advise

I have a client who use a version 10gR2 DB that stores both English and French data. There are several times where they will send up .dmp file where we load it into ours.
2 questions.
What would be the best charater sets to use here in this setup?
I am assuming we would use
NLS_CHARACTERSET = WE8ISO9959P1
NLS_NCHAR_CHARACTERSET = AL16UTF16
Also if someone can confirm for me.
NLS_CHARACTERSET = database character set ???
NLS_NCHAR_CHARACTERSET = national character set???

So is it better to say that I should use the AL32UTF8
instead of AL16UTF16 ?It's not an instead of situation. AL32UTF8 is a valid setting for the database character set, which controls CHAR and VARCHAR2 columns. AL16UTF16 is a valid setting for the national character set which controls NCHAR and NVARCHAR2 columns.
Could you tell me the difference?The difference between the two encodings comes down to how many bytes are required to store a particular code point (character). AL32UTF8 is a variable-length character set, so 1 character will require between 1 and 3 bytes of storage (4 for the supplemental characters but those are rather rare). AL16UTF16 is a fixed-width character set, so 1 character will require 2 bytes of storage (4 for the rare supplemental characters again).
Also could you tell me the difference between
WE8ISO8859P15 and WE8ISO8859P1 ? There's a Wikipedia article that discusses the differences and has links to the two different code tables.
Werner's point is an excellent one as well. I was assuming that we were talking about how to set up both sides of this proposed system. If the source system already exists, there are additional considerations like ensuring that your target system supports a superset of the characters supported by the source system. Regardless, when doing imports & exports, as Werner points out, you need to ensure that NLS_LANG is set appropriately.
Justin

Foreign character set issue

Hi
This might sound a bit silly, but stay with me.
There's a database that decidedly supports UTF 8. I checked using this query
select * from nls_database_parameters where parameter like '%CHARACTERSET'
And got this result
NLS_CHARACTERSET UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16
It's Oracle 10g.
In a particular table, some text is stored in multiple languages. There are seven languages (English, Mandarin, Japanese, German...). Every language has 2-3 rows to itself. There's a column where I have to get rid of the trailing few characters, the number of which depends on the content of the string.
But I cannot see any of the Eastern languages in TOAD. The column is in VARCHAR2.
My problem is twofold.
1. What functions do I use to ensure that only the last few bytes are truncated, and there's no data loss (which many websites gravely warn of when dealing with foreign language data) ?
2. How can I see this foreign language text in TOAD/SQLPlus?
(Yes, I'm kind of new to the whole multiple-language-game. Please let me know if I've left out any important detail!)

Do you have metalink access?
If so, please see the notes below, there's a lot of good information in them:
158577.1 - NLS_LANG explained
260893.1 - Unicode Character Sets in the Database
788156.1 - UTF8 implications
With any character set situation there are at least two and a bit sides to the equation.
First is whether you are storing the correct data.
You're best using the DUMP function to inspect the stored data, e.g.
SELECT DUMP(<column_name>) FROM <table_name> WHERE ....This function may help you with your truncation of the last few bytes - not sure why you need to do this?
The "second and a bit" bit is having the correct client settings - NLS_LANG - and using a client which supports the characters required.
SQL*Plus has it's limitations here. Toad I don't know well enough but it should support full UTF8 characters.
SQL*Developer and iSQL*Plus both should support the full UTF8 - I tend to use the former, particularly for UTF8.

9i Character Set Issues

Hi All,
I have a done a search through the forums on this topic, and revealed many answers to my question, however I need some more information to help me resolve an Issue.
Here goes...
Our company has a French/Canadian client that has installed 9i with the characterset of WE8DEC. The software that we wrote and provided them with does not support this characterset, and in turn they are seeing inverted question marks in place of some characters (Usually accented characters).
Basically, I want to understand the options that our client has in terms of possible solutions.
I understand that the characterset can only be altered in the database to a superset of the current characterset, so this affords us no option in this regard.
My suggestions so far, is to create a new database and transfer the data accross, however will this actually cure the issue? Will the data transfer accross and convert into it's correct character? or will it just transfer as an inverted "?".
Would an upgrade to 10g help them? Or would the issue remain?
Is there anything that can be done on the O/S or Client level to rectify this?
All help greatly appreciated!
Thanks.

user10498503 wrote:
Hi All,
I have a done a search through the forums on this topic, and revealed many answers to my question, however I need some more information to help me resolve an Issue.
Here goes...
Our company has a French/Canadian client that has installed 9i with the characterset of WE8DEC. The software that we wrote and provided them with does not support this characterset, and in turn they are seeing inverted question marks in place of some characters (Usually accented characters).
Basically, I want to understand the options that our client has in terms of possible solutions.
I understand that the characterset can only be altered in the database to a superset of the current characterset, so this affords us no option in this regard.
My suggestions so far, is to create a new database and transfer the data accross, however will this actually cure the issue? Will the data transfer accross and convert into it's correct character? or will it just transfer as an inverted "?".Your issue has a client side component (the NLS_LANG setting already mentioned here) and a potential server side component (corrupted/invalid data in the database), depending on what happened so far.
The client side issue could lead to corrupted data in the database, and there is no way of "correcting" this automatically, even if you move to a new database using a different character set on 9i, or upgrade to 10g.
If a client that writes into the database uses a wrong NLS_LANG setting, you're potentially ending up with corrupted data in the database.
If a client that reads data from the database uses a wrong NLS_LANG setting, you're potentially ending up with corrupted data on the front end application (the typical "?" question mark).
All this has nothing to do yet if your database character set is actually capable of storing the characters you attempt to store from the client side.
So I think you first need to determine if your database contains invalid data using the "CSSCAN" utility. For more information, check the manuals and MetaLink:
http://download.oracle.com/docs/cd/B10501_01/server.920/a96529/ch11.htm
Depending on your findings you'll find the possible actions on MetaLink.
Then you should determine if your client NLS_LANG is appropriate. There is a very good FAQ available here how to check the current setting and determine the correct setting:
http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/

German character set issues on Solaris

Hi,
I am facing an issue with German character settings with my Java application on a solaris box.
When I run my application on the box, and I pass an input file with German special characters they get converted as ?. However, other normal English characters are formed properly.
When I run the same application on another Solaris box with a different JRE, the German characters are formed properly.
I understand that there is a difference in the archiecture between the 2 boxes ie.e
64 bit SPARC machine v/s 32 bit x86 machine
the JRE
1.4.2_03(64bit) v/s 1.4.1_01
I am tryinbg to evaludate further differences between the 2 environments to pinpoint the issue, and get this resolved on the 1st box.
Can anyone provide me any inputs?
Lavin

When you read the file, please point out what character set using. For example:
FileInputStream fstream = new FileInputStream(url.getFile());
DataInputStream in = new DataInputStream(fstream);
BufferedReader br = new BufferedReader(new InputStreamReader(in, Charset.forName("ISO-8859-1")));
br.readLine();
This link possibly can help you.
http://www.velocityreviews.com/forums/t126128-jdk-14-character-set-change.html

Specifying character set on application import

hi --
I'm running into a problem that I think has to do w/ character sets.
I'm using non-breaking spaces in numerous LOVs; they're entered in as ALT +0160 on the keypad. These non-breaking spaces work great in the development environment of APEX (eg in the development app), and now I need to export/import the app to a production environment, which is runtime only.
The NLS_CHARACTERSET on both the development and production databases is US7ASCII.
When I import the app into the runtime installation of APEX I simply run the export file in sqlplus as the schema user.
(It has been scp'd over, as a text file, from the development server.)
The application imports and runs fine, but the non breaking spaces are displayed as garbage characters.
I did some testing on apex.oracle.com. I noticed that when I specify character set of unicode utf-8 on import,
the non-breaking spaces work properly. When I specify US-ASCII, I get the same garbage I'm getting in
my production environment.
When I export the app from the development environment, the character set is fixed (cannot be changed) to unicode utf-8. But I'm not doing anything to set the character set on import (don't know that I can...), and I wonder if it's adopting the database default character set of ASCII.
How can I get the imported app to use the desired character set? Am I going to have to convert this to a development
environment just so I can specify the character set on import, or is there a way to do it in sqlplus?
I'm not entirely sure I'm on the right track... but maybe someone has ideas how to get these non breaking spaces working in the production environment.
If access to my workspace on apex.oracle.com would be helpful, let me know.
Thanks,
Carol

I forgot to mention that, from what I've recently read, ASCII does not have a representation for non breaking spaces... so the behavior I'm experiencing is at least consistent with that...

Character set mismatch during import

I have exported a tablespace from a database using transportable tablespace option
with CHARACTERSET UTF8. And I tried to import into another db where the CHARACTERSET is US7ASCII. Now it says that it cannot import because the charactersets are different. Is there any way to get around this problem?
Regards,
Kallur Manoj.

Manoj,
One of the limitations for transportable tablespace is that the source and target databases should use the same character set and national character set.
You may need to either export the tablespace with us7ascii, or import to a db with utf8 characterset.
AGK

Help:character set mismatch after DB installation

hai friends,
After my oracle installtion database character set *(AL32UTF8)* and client character
set*(WE8MSWIN1252)* became different..and a message specifies that i can set client character set through
HKLM/SOFTWARE/ORACLE/KEY_trial registry..so what i suposed to do..now the NLS_LAG.reg contains the value as AMERICAN_AMERICA.WE8MSWIN1252...so for changing from one character set to another what i have to type inside NLS_LAG.reg...
thanks in advance...

The client character set must match the Operating System code page, so check HKLM\SYSTEM\CurrentControlSet\Control\Nls\CodePage\, look for an entry with name ACP, if its value is "1252" then NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252 is OK. See Note *179133.1* The correct NLS_LANG in a Windows Environment for more information.
HTH
Enrique

Issues after Importing sun java creator2 update1 project to netbeans 5.5.1

After Importing my SJC2U1 project into my netbeans 5.5.1 ,my project can see javax.faces.* package.even when i right click to fix import ,it was saying package javax.faces does not exist

Hi,
I am responsible for Migration testing effort in Visual Web Pack QE team. Would it be possible that you could send your original Creator project to me at my email address.
yousuf dot haider at sun dot com
Rest assured that this will only be used internally inside Sun and will be kept confidential.
Thanks
Yousuf

PL/SQL XML generation: Character set issues

Hi,
I am using the PL/SQL DOM (wrappers to the Java DOM), to generate XML from bits of database information. (On Oracle 8i).
The output XML must be in UTF-8, and the database character set must be anything I want it to be. So I call
setCharset(doc, 'UTF8')
at the beginning, and I call
writeToClob(doc, xmllob, 'UTF8')
at the end, just to cover all eventualities.
However, any character outside ASCII gets
replaced with the character string "\xBF\xBF", which is rather tedious.
If, instead, we go via
writeToBuffer(doc, xmlbuf, 'UTF8')
and then dump the buffer contents into a clob, the UTF8 encoding is preserved, and everything works.
(This latter method is not good enough for my needs; I need more than 32K of data...)
So I was wondering if any kind soul could tell me what I am doing wrong.
Thanks,
<< Mike Alexander >>
null

I have the same problem. Is there any solution found?
only xslprocessor.valueOf returns values of xml document not loosing special symbols.

Urgent :SQL Loader Arabic Character Set Issue

HI all,
I am loading arabic characters into my database using SQL Loader using a fixed length data file. I had set my characterset and NLS_LANG set to UTF8.When I try to load the chararacter 'B' in arabic data i.e. ' لا ' , it gets loaded as junk in the table. All other characters are loaded correctly. Please help me in this issue and its very urgent.
Thanks,
Karthik

Hi,
Thanks for the responses.
Even after setting the characterset to arabic and the problem continues to persist. This problem occurs only with the character "b".
Please find my sample control file,input file and nls_parameters below:
My control file
LOAD DATA
characterset UTF8
LENGTH SEMANTICS CHAR
BYTEORDER little endian
INFILE 'C:\sample tape files\ARAB.txt'
replace INTO TABLE user1
TRAILING NULLCOLS
name POSITION(1:2) CHAR(1),
id POSITION (3:3) CHAR(1) ,
salary POSITION (4:5) CHAR(2)
My Input file - Fixed Format
?a01
??b02
?c03
The ? indicates arabic characters.Arabic fonts must be installed to view them.
NLS_PARAMETERS
PARAMETER     VALUE
NLS_LANGUAGE     ARABIC
NLS_TERRITORY     UNITED ARAB EMIRATES
NLS_CURRENCY     ?.?.
NLS_ISO_CURRENCY     UNITED ARAB EMIRATES
NLS_NUMERIC_CHARACTERS     .,
NLS_CALENDAR     GREGORIAN
NLS_DATE_FORMAT     DD/MM/RR
NLS_DATE_LANGUAGE     ARABIC
NLS_SORT     ARABIC
NLS_TIME_FORMAT     HH12:MI:SSXFF PM
NLS_TIMESTAMP_FORMAT     DD/MM/RR HH12:MI:SSXFF PM
NLS_TIME_TZ_FORMAT     HH12:MI:SSXFF PM TZR
NLS_TIMESTAMP_TZ_FORMAT     DD/MM/RR HH12:MI:SSXFF PM TZR
NLS_DUAL_CURRENCY     ?.?.
NLS_COMP     BINARY
NLS_LENGTH_SEMANTICS     CHAR
NLS_NCHAR_CONV_EXCP     FALSE

Font issues after import

I'm working on an application that uses embedded fonts. After the initial import, the fonts do not render correctly, when I use several fonts.
If after the import I change the font, it works correctly.
Any idea will be truly appreciated.

I'm probably missing something. Here's my code:
textFlow = TextConverter.importToFlow( xml, TextConverter.TEXT_LAYOUT_FORMAT);
textFlow.flowComposer = new StandardFlowComposer();
if( editManager == null && undoManager == null){
     undoManager = new UndoManager();
     editManager = new EditManager( undoManager );
     textFlow.interactionManager = editManager;
     textFlow.interactionManager.selectRange(0,0);
textFlow.flowComposer.updateAllControllers();
I replaced "textFlow.flowComposer.updateAllControllers();" with:
var cf:TextLayoutFormat = new TextLayoutFormat();
cf.fontLookup = flash.text.engine.FontLookup.EMBEDDED_CFF;
IEditManager( textFlow.interactionManager ).applyLeafFormat(cf);
but still get the same result. The font doesn't render correctly after the import.

Need to undo set up after importing contents from old Macse

I just set up my new MB pro with OX X Mavericks. I choosed the option of "import contents from other mac" and brought my entire user identity and contents from my old MB air. But it created a whole new user identity in my new computer. I don't like it and want to undo it and start all set up again from the begining. Any ideas of how to do it. I have all my contentes backuped, so I'm not worried about that... By the way, I heard many times that it was not a good idea to start using a new Mac bringing all contents from your old one this way. Any comments to this?

You typed you migrated from your old partners PC - try using their password. It sounds like you've done what is in these articles, but maybe there will be something new.
Reset Password
Reset Password using Apple ID
If you can see the other computer in Finder, try drag and drop copying the files. Can you copy the files to a Flash drive or external hard drive and then download them?

Character set issue after import?

Similar Messages

Maybe you are looking for