Character set AL32UTF8;
Hello All,
I have oracle 10gr2 and i want to get support of Portuguese character set, for that , i suppose AL32UTF8 is recommended, but when i try to modify the character set i get this error.
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
WE8ISO8859P1
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
what should i do now? any idea?
thanks
here it is:
SQL> select news_detail from news_tbl;
NEWS_DETAIL
<p>A Directora nacional-Adjunta do Patrim?nio ligado ao Minist?rio das Finan?as
de Mo?ambique, Albertina Fruquia, esteve nesta quarta-feira, do dia 22 de Novemb
ro, na Secretaria de Log?stica e Tecnologia de Informa??o ( SLTI )para conhecer
o sistema de compras do Governo Federal Brasileiro e verificar a possibilidade d
e estabelecer acordos de coopera??o nessa ?rea.</p>
<p> </p>
<p>Na opini?o da Directora Mo?ambicana, o Brasil tem uma experi?ncia importante
em compras p?blicas que pode colaborar com Mo?ambique nesta ?rea. Ela lembrou qu
e o pa?s Africano est? imlpementando um novo regulamento de compras que constitu
i o preg?o presencial, modalidade regulamentada no Brasil desde 2000.</p>
<p> </p>
you can see that even in sqlplus the data is not shown the portugueses language chars, now what you think, that whether this data is stored wrong or either i can recover it by changing chars set or language?
Message was edited by:
nayyares
Message was edited by:
nayyares
Similar Messages
-
How to Import Database user in oracle which have character set AL32UTF8?
Hello All,
I want export one database user which have character set in WE8MSWIN1252 and I want to Import that Database user in oracle which have character set AL32UTF8 without changing character set.
is there any argument in import command??
thanksThere's no problem, export and import will take care of character set conversions, the only problem is AL32UTF8 is a variable size character set, if 'ñ' uses 1 byte in WE8MSWIN1252, in AL32UTF8 it will use 2 bytes, so it's recommended to pre-create the tables with "char" instead of "byte": create table xxx ( col1 varchar2(100 char), ... )
Enrique -
OWB 11.1.0.6.0 with database character set AL32UTF8 is not working
Hi ,
we are working for a project for Turkey.
if we insert Turkish characters in database ,in sqldevelpoer we are able to see the correct data. but when i load a file from preprocessor in OWB Process Flow, the characters which are in Turkish got changed to different characters in database. our databse character set is AL32UTF8. could you please throw some light on this please.
Many thanks,
kiranmai.hi ,
ya we are using the correct dataset only in preprocessr configuration. actually it was a problem with OWB only ,
i have changed database character set to WE8ISO8859P9,then i am able to se correct Trukey chars in database. i think it was a SR for oracle . -
ORA-12712 error while changing nls character set to AL32UTF8
Hi,
It is strongly recommend to use database character set AL32UTF8 when ever a database is going to used with our XML capabilities. The database character set in the installed DB is WE8MSWIN1252. For making use of XML DB features, I need to change it to AL32UTF8. But, when I try doing this, I'm getting ORA-12712: new character set must be a superset of old character set. Is there a way to solve this issue?
Thanks in advance,
Divya.Hi,
a change from we8mswin1252 to al32utf8 is not directly possible. This is because al32utf is not a binary superset of we8mswin1252.
There are 2 options:
- use full export and import
- Use of the Alter in a sort of restricted way
The method you can choose depends on the characters in the database, is it only ASCII then the second one can work, in other cases the first one is needed.
It is all described in the Support Note 260192.1, "Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)". Get it from the support/metalink site.
You can also read the chapters about this issue in the Globalization Guide: [url http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch11charsetmig.htm#g1011430]Change characterset.
Herald ten Dam
http://htendam.wordpress.com -
Oracle11g: how I change character set to AL32UTF8?
Hi, a software is requiring to have a database with AL32UTF8 character set.
For what I understand I have an instance of db with
nls_language=american
I tried:
SQL> alter database character set AL32UTF8;
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
what's wrong? How can I achieve this?
Thanks a lot.
Warning: you are talking with a non expert. :)802428 wrote:
Hi schavali,
I am new bee to oracle and BPM so i am unable to get which database you are talking about to drop & recreate and also how to do so.
Any help over this will be highly appreciable.
Regards,
ITM CrazyWe are referring to OP's database (where the characterset is set to WE8MSWIN1252)
Srini -
Unable to migrate table, character set from WE8MSWIN1252 to AL32UTF8
Hi,
On our source db the character set is AL32UTF8
On our own db, we used the default character set of WE8MSWIN1252 .
When migrating one of the table, we get an error of this: ORA-29275: partial multibyte character
So in to alter our character set from WE8MSWIN1252 to AL32UTF8, we get this error:
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
I would sure not like to reinstall the db and migrate the tables again. Thanks.See this related thread - Re: Want to change characterset of DB
You can use the ALTER DATABASE CHARACTER SET command in very few cases. You will most likely have to recreate the database and re-migrate the data.
HTH
Srini -
Conversion of character sets (UCS2 of MSSQL to AL32UTF8 of Oracle Warehouse
Hi all,
I installed my enviroment as below.
Server:
Windows 7 Professional
SQL Server 20012
Character Set: UCS2
Client:
Linux REDHAT 5
Oracle Warehouse 11gR2 (11.2.0.1)
Oracle Database Gateway for MSSQL Server 11.2.0.1
Character Set:AL32UTF8
I installed the gateway for connecting the Oracle Warehouse with MSSQL DB. However, the characters are not readable, because the character of MSSQL DB is coded via one byte character, and the Oracle character is coded like multibyte character.
Input:
Table name on the MSSQL DB: Table_Name
Output:
Table name on the Oracle Warehouse Import Wirzard:◊T◊a◊b◊le◊_◊N◊a◊m◊e
It causes error by importing the table, because the OWB doesn't allow the unreadable characters of table name.
Do you have an idea for resolving it.
Thanks and kind regards,
HipOk, I have changed it as you wrote:
HS_FDS_CONNECT_INFO=100.30.4.157:1433//bob
HS_FDS_TRACE_LEVEL=255
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER
HS_TRANSACTION_MODEL=READ_ONLY
HS_LANGUAGE=american_america.we8mswin1252
HS_NLS_NCHAR=UCS2
HS_NLS_LENGTH_SEMANTICS=CHAR
and I also added the listern.ora:
(SID_DESC =
(SID_NAME=bob)
(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_2)
(ENVS=LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/dbhome_2/dg4msql/driver/lib;/u01/app/oracle/product/11.2.0/dbhome_2/lib)
(PROGRAM=dg4msql)
tnsname.ora:
bob =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA = (SID = bob))
(HS = OK)
SQL> select * from all_users@bob;
USERNAME USER_ID CREATED
public 0 08-APR-03
dbo 1 08-APR-03
guest 2 08-APR-03
INFORMATION_SCHEMA 3 13-APR-09
sys 4 13-APR-09
db_owner 16384 08-APR-03
db_accessadmin 16385 08-APR-03
db_securityadmin 16386 08-APR-03
db_ddladmin 16387 08-APR-03
db_backupoperator 16389 08-APR-03
db_datareader 16390 08-APR-03
db_datawriter 16391 08-APR-03
db_denydatareader 16392 08-APR-03
db_denydatawriter 16393 08-APR-03
14 rows selected.
The Oracle Warehouse Builder still has the same error by the conversion of character sets.
Hip -
Unable to alter character set from WE8MSWIN1252 to AL32UTF8
Hi,
I am trying to migrate some tables to my database.
On the source DB, the character set is AL32UTF8
On My database, the character set is WE8MSWIN1252.
When I tried to alter the character set, I get this error message:
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
Any help? Thanks.Pl refrain from posting duplicate threads :-)
Unable to migrate table, character set from WE8MSWIN1252 to AL32UTF8
Srini -
Java Character set error while loding data using iSetup
Hi,
I am getting the following error while migrating settup data from R12 (12.1.2) Instance to another R12 (12.1.2) Instance, Both the Database has same DB character set (AL32UTF8)
we are getting this error while migrating any setup data
Actual error is
Downloading the extract from central instance
Successfully copied the Extract
Time taken to download Extract and write as zip file = 0 seconds
Validating Primary Extract...
Source Java Charset: AL32UTF8
Target Java Charset: UTF-8
Target Java Charset does not match with Source Java Charset
java.lang.Exception: Target Java Charset does not match with Source Java Charset
at oracle.apps.az.r12.common.cpserver.PreValidator.validate(PreValidator.java:191)
at oracle.apps.az.r12.loader.cpserver.APILoader.callAPIs(APILoader.java:119)
at oracle.apps.az.r12.loader.cpserver.LoaderContextImpl.load(LoaderContextImpl.java:66)
at oracle.apps.az.r12.loader.cpserver.LoaderCp.runProgram(LoaderCp.java:65)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Error while loading apis
java.lang.NullPointerException
at oracle.apps.az.r12.loader.cpserver.APILoader.callAPIs(APILoader.java:158)
at oracle.apps.az.r12.loader.cpserver.LoaderContextImpl.load(LoaderContextImpl.java:66)
at oracle.apps.az.r12.loader.cpserver.LoaderCp.runProgram(LoaderCp.java:65)
at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Please help in identifying and resolving the issue
SachinThe Source and Target DB character set is same
Output from the query
------------- Source --------------
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
AL32UTF8
And target Instance
-------------- Target----------------------
SQL> select value from nls_database_parameters where parameter='NLS_CHARACTERSET';
VALUE
AL32UTF8
The Error is about Source and Target JAVA Character set
I will check the Prevalidator xml from How to use iSetup and update the note
Thanks
Sachin -
Character Set Error in PL/SQL
Hi,
While connecting to PL/SQL Developer I am getting this following error.
Database character set (AL32UTF8) and client character set (WE8MSWIN1252) are different.
Character set conversion may cause unexpected results.
Note: you can set the client character set through the NLS_LANG registry key in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_XE.
Please help me avoid this error.
Thanks.That is presumably a PL/SQL Developer error. You may want to contact the vendor of that particular product to understand that warning because it makes no sense to me.
It is perfectly appropriate, and quite normal, for the client character set to be a subset of the database character set. Setting the client character set to match the database character set can create a host of problems that lead to invalid data being stored in the database. This appears designed to increase the odds that this particular tool will work correctly while decreasing the odds that everything else in your environment will work correctly. That seems like a relatively poor trade-off to me.
Justin -
hi my database character set is non-AL32UTF8 HOW can i change this to be AL32UTF8 am in database 11g
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
PARAMETER
VALUE
NLS_CHARACTERSET
WE8MSWIN1252
NLS_NCHAR_CHARACTERSET
AL16UTF16
there is something in database i cannot drop databasei did this
SQL> @C:\app\Tshifhiwa\product\11.2.0\dbhome_1\RDBMS\ADMIN\csalter.plb
insert into csm$dictusers
ERROR at line 1:
ORA-00942: table or view does not exist
Function created.
Warning: Function created with compilation errors.
Warning: Procedure created with compilation errors.
This script will update the content of the Oracle Data Dictionary.
Please ensure you have a full backup before initiating this procedure.
Would you like to proceed (Y/N)?y
old 6: if (UPPER('&conf') <> 'Y') then
new 6: if (UPPER('y') <> 'Y') then
csm$main();
ERROR at line 10:
ORA-06550: line 10, column 5:
PLS-00905: object SYS.CSM$MAIN is invalid
ORA-06550: line 10, column 5:
PL/SQL: Statement ignored
select value into svalue from csm$parameters where name='CSALTER_FINISHED';
ERROR at line 9:
ORA-06550: line 9, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 9, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 18, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 18, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 21, column 38:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 21, column 8:
PL/SQL: SQL Statement ignored
ORA-06550: line 27, column 35:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 27, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 30, column 38:
PL/SQL: ORA-00942: table or view does not exist
ORA-06550: line 30, column 8:
PL/SQL: SQL Statement ignored
delete from csm$dictusers where username in ('PM', 'SH', 'HR', 'OE')
ERROR at line 1:
ORA-00942: table or view does not exist
Function dropped.
Function dropped.
Procedure dropped.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM ENABLE RESTRICTED SESSION
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET AQ_TM_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ERROR:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 4360
Session ID: 139 Serial number: 6
SQL> connect /as sysdba
Connected to an idle instance.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 373293520 bytes
Database Buffers 155189248 bytes
Redo Buffers 5804032 bytes
Database mounted.
SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
System altered.
SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
System altered.
SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
System altered.
SQL> ALTER DATABASE OPEN;
Database altered.
SQL> ALTER DATABASE CHARACTER SET 'AL32UTF8';
ALTER DATABASE CHARACTER SET 'AL32UTF8'
ERROR at line 1:
ORA-24329: invalid character set identifier
SQL> ALTER DATABASE CHARACTER SET AL32UTF8;
ALTER DATABASE CHARACTER SET AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
PARAMETER
VALUE
NLS_CHARACTERSET
WE8MSWIN1252
NLS_NCHAR_CHARACTERSET -
Character set in MDL export/import
Hi,
we are running OWB 10.1.0.2. In order to get version control, we perform MDL exports of collections from our development environment and then import them into our test and production environments. Each environment uses its own design repository, but all repositories are in the same database.
When doing an export of a collection, we always specify the character set AL32UTF8 because that is what we are running in the repository database. When later doing an import using the graphical user interface, it is not possible to specify the character set (but this can be done when using the import utility). According to the documentation, the GUI import will then assume that the character set in the collection is the character set of the client, which usually is WE8MSWIN1252. (The documentation also says that it IS possible to specify the character set during GUI import, this is obviously a documentation error).
My questions are: What is the point of specifying character set when doing exports and imports? Could an AL32UTF8 export followed by an WE8MSWIN1252 import cause problems? I assume that the character set used by export is specified in the collection file, so does the import then convert it to WE8MSWIN1252 (or the character set specified in the import utility)?
Or, to be more general: What is actually happening with the character sets during MDL export/import?
/Kjell GullbergDear ski123,
I think you are not going to loose any data of yours when you migrate the database. You may proceed to the import.
Please find below documentations;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14196/install003.htm#sthref81
For Database Character Set, select from one of the following options:
*Use the Default—Select this option if you need to support only the language currently used by the operating system for all your database users and your database applications.
*Use Unicode (AL32UTF8)—Select this option if you need to support multiple languages for your database users and your database applications.
*Choose from the list of character sets—Select this option if you want the Oracle Database to use a character set other than the default character set used by the operating system.Choosing a Character Set;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#NLSPG002
AL32UTF8;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/glossary.htm#sthref2039
Hope That Helps.
Ogan -
Agent control character set problem
Hi,
here's my problem :
i've got the grid that's running on a RHES4 with an agent. On another RHES4, i've got 10g databases that run and another agent.
The repository database is configured like this :
nsl_language = AMERICAN
nls_territory = AMERICA
character set = AL32UTF8
all the uploads from the agent on the RHES4 where the grid is installed are ok.
On the other server, as soon as there's an UTF8 character in a xml file (like " é " ou " ' "), the upload fails and the agent stops.
in the logs, it s clear it comes from this. I've deleted all the occurences of UTF8 characters in the xml file and restarted the upload and it's ok...
I've tested different configurations but without success.
Any clue ?
AlivetuThanks for the reply,
NLS LANG is set on the 2 machines with FRENCHFRANCE.WE8ISO8859P15
I've added the line '<?xml version="1.0" encoding="ISO-8859-1"?>' at the beginning of the xml file that doesn't work and made a 'emctl upload'....it has passed and the agent has stopped arrived to another UTF8 xml file...
So, it really is a character set problem but where to set it ???
Alivetu -
DBCA doesn't save character set information in the template!!
Hello,
I have found a problem using the DBCA when creating a template with a database character set of AL32UTF8.
When I create a database using the aforementioned template from the commandline (dbca -silent) it reverts the character set to WE8ISO8859P1.
If I try and alter the character set after creation using:
ALTER DATABASE CHARACTER SET AL32UTF8;
it complains that tis cannot be done, so I must set this in the template.
Am I missing something obvious? Why is this information not being stored in the .dbc file?
Many thanks
Nic HemleyWell, having patched the template xml file i then had to do:
dbca -silent -createDatabase -templateName advisor.dbc -gdbName advisor.invocom -sid advisor -sysPassword j3r3m1aha -continueOnNonFatalErrors false
apparently the .dbc is required on the template name
However.....
NLS_DATE_LANGUAGE
NLS_DATE_FORMAT
NLS_LANGUAGE
NLS_TERRITORY
NLS_ISO_CURRENCY
are not set in the template either...why is the template missing so much stuff that i thought i had configured? -
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
Maybe you are looking for
-
2504 controller + 2602 APs = wireless clients connectivity problems
Hello, everybody! I have a connectivity problems of wireless clients. The symptoms are: 1) Some clients receive 169.254.x.x., instead a correct DHCP addresses, less in a minute connection drops, and in controller's "Monitor" > "Clients" tab these cli
-
Advance one frame at a time. Quick question.
Hi, sorry for the really bad question but my keyboard does not have a page up and a page down button So what other short cut is there to do this? Is there a way I can assign my own shortcuts like FCP and Premiere? Thanks!...
-
Can anyone help with scripting problem?
I finally figured our how to write my own scripting in InDesign (CS2) to format the schedules I work on. Now we upgraded to CS4 and they don't work anymore. I'm not knowledgeable enough to know why it's not working. I someone familiar with this? I co
-
I'm getting an error (BEA-090508) when trying to apply SSL and starting the server
I'm trying to apply SSL with my own CA on a Weblogic Server. I'm getting an error (BEA-090508) when trying to start the server. regards
-
Problems with Menu Bar after recent security update
Ever since installing yesterday's security update I have been having problems with the menu bar. When clicking on the blue Apple in the upper left hand corner, no drop-down menu appears as it should. This problem also occurs in the drop-down menu nam