Migratiom from WE8MSWIN1252 to al32utf8
Hi
I need to migrate my db from western Europe character set to a multi byte character set.
I exported my data from 10g instance with WE8MSWIN1252 and then imported it to an 10g instance with AL32UTF8 and nsl_lenght_semantic = 'CHAR'.
The VARCHAR2 fields and char fields are still defined as bytes.
es. my_desc varchar2(100 byte )
Then I need to convert all varchars and char fields definition to 'CHAR'.
I know that I can perform this field by field using ALTER TABLE MODIFY.
All my tables are defined into one schema, (mySchema.tab1, mySchema.tab2,...).
so, I want to know if it is possible to do this conversion in one step?
Thanks
Mario
user8091088 wrote:
then imported it to an 10g instance with AL32UTF8 and nsl_lenght_semantic = 'CHAR'.
The VARCHAR2 fields and char fields are still defined as bytes.
es. my_desc varchar2(100 byte )Check your export dump. It could be that create statements etc. are using column length specified as 'byte'.
Metalink/MOS might have some Note that documents possible supported workarounds.
Similar Messages
-
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 -
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 -
Change Oracle XE from WE8MSWIN1252 to AL32UTF8
I want to change the character set of Oracle XE 10g on my machine from WE8MSWIN1252 to AL32UTF8. I understand I need to scan, change my NLS_LANG and export and them import into new XE with Universal character set.
I need some more details to these steps if someone can help out.
My current Oracle XE details:
NLS_LANGUAGE - AMERICAN
NLS_TERRITORY - AMERICA
NLS_CHARACTERSET - WE8MSWIN1252
I want NLS_CHARACTERSET to be AL32UTF8.
Thanks,Hi everbody,
Really OracleXE dont suport character convertion.
But I get the binary CSSCAN from another Oracle 10g Enterprise and copy to server of XE in $ORACLE_HOME/bin.
With this, I copy also CSALTER.PLB and CSMINST.SQL to ?/rdbms/admin and now, I have the scripts.
So, I run following the "howto" and read .log, .err and .out files generated from log=
If you receive the message "Checking or Converting phrase did not finish successfully", check the .err file and drop the tables listed as "with error". After this, the process run without erros and YES, the database is CHANGED.
I do this and I can afirm: this process works!
Ederson.Oliveira
www.rwit.com.br -
Convert Characterset from WE8MSWIN1252 to AL32UTF8
Dear Friends,
How to conver Characterset from WE8MSWIN1252 of Oracle 10.2.0.2 Database (32 bit Ent Edition) to AL32UTF8 on 11.2.0.2 (64 Bit Std Edition) during 11g DB Upgrade.
How to check the Limitations of Characterset conversions and the objects which will be affected during the conversion.
Regards,
DBIf you want help from this forum, i recommend:
1) Search before post
2) close your threads when it will be answered:
839396
Handle: 839396
Status Level: Newbie
Registered: Feb 23, 2011
Total Posts: 21
Total Questions: 14 (14 unresolved) -
Characterset conversion from WE8MSWIN1252 to AL32UTF8
DB Version:11g
Is it possible to convert a DB of WE8MSWIN1252 characterset to AL32UTF8?Yes it can be done..
Please refer below metalink notes:
Changing the Database Character Set ( NLS_CHARACTERSET ) [ID 225912.1]
AL32UTF8 / UTF8 (Unicode) Database Character Set Implications [ID 788156.1]
Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) [ID 260192.1]
Regards
Rajesh -
Need to change character set from WE8MSWIN1252 to AL32UTF8.
Hi,
We have installed the database with Character set WE8MSWIN1252. But off late we understood that client requirement is AL32UTF8. Is there any way to change in easy method?
Thanks in-advance.
Rgds
DBA.Pl also see these Docs
AL32UTF8 / UTF8 (Unicode) Database Character Set Implications [Document 788156.1]
Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) [Document 260192.1]
If you are using EBS, then also see
For 11i - Appendix A of "Oracle Applications 11i Internationalization Guide [Document 333785.1]"
For R12 - Appendix A of "Globalization Guide for Oracle Applications Release 12 [Document 393861.1]"
Changing the characterset of an existing database/application is not a trivial task - will require thorough planning and testing.
HTH
Srini -
CSSCAN in 11g - Characterset not changing from WE8IMSWIN1252 to AL32UTF8
All,
We have installed a 11g database in Linux box and once after that we wanted to change the character set to AL32UTF8 from default WE8MSWIN1252.
We took the cs-alter approach and ran cs-scan utility, upon going through csscan.txt files generated by csscan utility we found that there are no lossy data but convertible data was found in data dictionary. Below is the output from csscan.txt
This is the Scan Summary
*[Scan Summary]*
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
Database Scan Summary Report
Time Started : 2012-10-17 21:42:17
Time Completed: 2012-10-17 21:42:47
Process ID Time Started Time Completed
1 2012-10-17 21:42:18 2012-10-17 21:42:46
2 2012-10-17 21:42:18 2012-10-17 21:42:46
3 2012-10-17 21:42:18 2012-10-17 21:42:46
[Database Size]
Tablespace Used Free Total Expansion
SYSTEM 709.75M 256.00K 710.00M 2.42M
SYSAUX 645.63M 34.38M 680.00M 12.52M
UNDOTBS1 13.13M 16.88M 30.00M .00K
TEMP .00K .00K .00K .00K
USERS 1.31M 3.69M 5.00M .00K
HYPE_DATA 1,024.00K 19,999.00M 20,000.00M .00K
HYPE_INDX 1,024.00K 19,999.00M 20,000.00M .00K
Total 1,371.81M 40,053.19M 41,425.00M 14.94M
The size of the largest CLOB is 1625114 bytes
[Database Scan Parameters]
Parameter Value
CSSCAN Version v2.1
Instance Name dvhp081
Database Version 11.2.0.3.0
Scan type Full database
Scan CHAR data? YES
Database character set WE8MSWIN1252
FROMCHAR WE8MSWIN1252
TOCHAR al32utf8
Scan NCHAR data? NO
Array fetch buffer size 10240
Number of processes 3
Capture convertible data? NO
[Scan Summary]
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
[Data Dictionary Conversion Summary]
Data Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 5,408,302 0 0 0
CHAR 4,261 0 0 0
LONG 249,018 0 0 0
CLOB 67,652 3,794 0 0
VARRAY 49,807 0 0 0
Total 5,779,040 3,794 0 0
Total in percentage 99.934% 0.066% 0.000% 0.000%
The data dictionary can be safely migrated using the CSALTER script
XML CSX Dictionary Tables:
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 702 0 0 0
CHAR 0 0 0 0
LONG 0 0 0 0
CLOB 0 0 0 0
VARRAY 0 0 0 0
Total 702 0 0 0
Total in percentage 100.000% 0.000% 0.000% 0.000%
[Application Data Conversion Summary]
Datatype Changeless Convertible Truncation Lossy
VARCHAR2 2,550,581 0 0 0
CHAR 0 0 0 0
LONG 0 0 0 0
CLOB 22,187 8,287 0 0
VARRAY 0 0 0 0
Total 2,572,768 8,287 0 0
Total in percentage 99.679% 0.321% 0.000% 0.000%
[Distribution of Convertible, Truncated and Lossy Data by Table]
Data Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
MDSYS.SDO_COORD_OP_PARAM_VALS 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE 1 0 0
MDSYS.SDO_STYLES_TABLE 78 0 0
MDSYS.SDO_XML_SCHEMAS 5 0 0
SYS.METASTYLESHEET 179 0 0
SYS.RULE$ 1 0 0
SYS.SCHEDULER$_EVENT_LOG 356 0 0
SYS.WRH$_SQLTEXT 537 0 0
SYS.WRH$_SQL_PLAN 514 0 0
SYS.WRI$_ADV_DIRECTIVE_META 5 0 0
SYS.WRI$_ADV_OBJECTS 28 0 0
SYS.WRI$_ADV_SQLT_PLANS 2 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS 2 0 0
SYS.WRI$_DBU_FEATURE_METADATA 193 0 0
SYS.WRI$_DBU_FEATURE_USAGE 9 0 0
SYS.WRI$_DBU_HWM_METADATA 21 0 0
SYS.WRI$_REPT_FILES 27 0 0
SYSMAN.MGMT_IP_ELEM_DEFAULT_PARAMS 130 0 0
SYSMAN.MGMT_IP_REPORT_ELEM_PARAMS 1,475 0 0
SYSMAN.MGMT_IP_SQL_STATEMENTS 31 0 0
XML CSX Dictionary Tables:
USER.TABLE Convertible Truncation Lossy
Application Data:
USER.TABLE Convertible Truncation Lossy
APEX_030200.WWV_FLOW_BANNER 10 0 0
APEX_030200.WWV_FLOW_BUTTON_TEMPLATES 12 0 0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS 19 0 0
APEX_030200.WWV_FLOW_FLASH_CHART_SERIES 5 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES 298 0 0
APEX_030200.WWV_FLOW_PAGE_GENERIC_ATTR 44 0 0
APEX_030200.WWV_FLOW_PAGE_PLUGS 3,240 0 0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES 254 0 0
APEX_030200.WWV_FLOW_PROCESSING 45 0 0
APEX_030200.WWV_FLOW_ROW_TEMPLATES 66 0 0
APEX_030200.WWV_FLOW_SHORTCUTS 39 0 0
APEX_030200.WWV_FLOW_STEPS 1,795 0 0
APEX_030200.WWV_FLOW_STEP_PROCESSING 2,238 0 0
APEX_030200.WWV_FLOW_TEMPLATES 192 0 0
APEX_030200.WWV_FLOW_WORKSHEETS 30 0 0
[Distribution of Convertible, Truncated and Lossy Data by Column]
Data Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
MDSYS.SDO_COORD_OP_PARAM_VALS|PARAM_VALUE_FILE 200 0 0
MDSYS.SDO_GEOR_XMLSCHEMA_TABLE|XMLSCHEMA 1 0 0
MDSYS.SDO_STYLES_TABLE|DEFINITION 78 0 0
MDSYS.SDO_XML_SCHEMAS|XMLSCHEMA 5 0 0
SYS.METASTYLESHEET|STYLESHEET 179 0 0
SYS.RULE$|CONDITION 1 0 0
SYS.SCHEDULER$_EVENT_LOG|ADDITIONAL_INFO 356 0 0
SYS.WRH$_SQLTEXT|SQL_TEXT 537 0 0
SYS.WRH$_SQL_PLAN|OTHER_XML 514 0 0
SYS.WRI$_ADV_DIRECTIVE_META|DATA 5 0 0
SYS.WRI$_ADV_OBJECTS|ATTR4 28 0 0
SYS.WRI$_ADV_SQLT_PLANS|OTHER_XML 2 0 0
SYS.WRI$_ADV_SQLT_PLAN_STATS|OTHER 2 0 0
SYS.WRI$_DBU_FEATURE_METADATA|INST_CHK_LOGIC 22 0 0
SYS.WRI$_DBU_FEATURE_METADATA|USG_DET_LOGIC 171 0 0
SYS.WRI$_DBU_FEATURE_USAGE|FEATURE_INFO 9 0 0
SYS.WRI$_DBU_HWM_METADATA|LOGIC 21 0 0
SYS.WRI$_REPT_FILES|SYS_NC00005$ 27 0 0
SYSMAN.MGMT_IP_ELEM_DEFAULT_PARAMS|VALUE 130 0 0
SYSMAN.MGMT_IP_REPORT_ELEM_PARAMS|VALUE 1,475 0 0
SYSMAN.MGMT_IP_SQL_STATEMENTS|SQL_STATEMENT 31 0 0
XML CSX Dictionary Tables:
USER.TABLE|COLUMN Convertible Truncation Lossy
Application Data:
USER.TABLE|COLUMN Convertible Truncation Lossy
APEX_030200.WWV_FLOW_BANNER|BANNER 10 0 0
APEX_030200.WWV_FLOW_BUTTON_TEMPLATES|TEMPLATE 12 0 0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|AUTH_FUNC 8 0 0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|PAGE_SENT 10 0 0
APEX_030200.WWV_FLOW_CUSTOM_AUTH_SETUPS|POST_AUTH 1 0 0
APEX_030200.WWV_FLOW_FLASH_CHART_SERIES|SERIES_QU 5 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|ITEM_TEMPLATE 20 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|ITEM_TEMPLATE 20 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|LIST_TEMPLATE 105 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|LIST_TEMPLATE 105 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_LIST_ITEM 12 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_LIST_ITEM 12 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_TEMPLATE_ 12 0 0
APEX_030200.WWV_FLOW_LIST_TEMPLATES|SUB_TEMPLATE_ 12 0 0
APEX_030200.WWV_FLOW_PAGE_GENERIC_ATTR|ATTRIBUTE_ 44 0 0
APEX_030200.WWV_FLOW_PAGE_PLUGS|PLUG_SOURCE 3,240 0 0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES|TEMPLATE 166 0 0
APEX_030200.WWV_FLOW_PAGE_PLUG_TEMPLATES|TEMPLATE 88 0 0
APEX_030200.WWV_FLOW_PROCESSING|PROCESS_SQL_CLOB 45 0 0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE1 54 0 0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE2 10 0 0
APEX_030200.WWV_FLOW_ROW_TEMPLATES|ROW_TEMPLATE3 2 0 0
APEX_030200.WWV_FLOW_SHORTCUTS|SHORTCUT 39 0 0
APEX_030200.WWV_FLOW_STEPS|HELP_TEXT 1,513 0 0
APEX_030200.WWV_FLOW_STEPS|HTML_PAGE_HEADER 282 0 0
APEX_030200.WWV_FLOW_STEP_PROCESSING|PROCESS_SQL_ 2,238 0 0
APEX_030200.WWV_FLOW_TEMPLATES|BOX 64 0 0
APEX_030200.WWV_FLOW_TEMPLATES|FOOTER_TEMPLATE 64 0 0
APEX_030200.WWV_FLOW_TEMPLATES|HEADER_TEMPLATE 64 0 0
APEX_030200.WWV_FLOW_WORKSHEETS|SQL_QUERY 30 0 0
[Indexes to be Rebuilt]
USER.INDEX on USER.TABLE(COLUMN)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00078$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00079$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00080$)
APEX_030200.WWV_FLOW_WORKSHEETS_UNQ_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00081$)
APEX_030200.WWV_FLOW_WS_UNQ_ALIAS_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(SYS_NC00082$)
APEX_030200.WWV_FLOW_WS_UNQ_ALIAS_IDX on APEX_030200.WWV_FLOW_WORKSHEETS(ALIAS)
----------------------------------------------------------------------------------We followed few metalink documents *Solving Convertible or Lossy data in Data Dictionary objects reported by Csscan when changing the NLS_CHARACTERSET [ID 258904.1]* and found that we are good to go as convertible was found only in data dictionary and that too CLOB data. But while running csalter.plb csalter came out without changing the characterset. We ran the following query given the said document and it returned no rows which again confirms there is no problem and go ahead with running csalter.
SELECT DISTINCT z.owner_name
|| '.'
|| z.table_name
|| '('
|| z.column_name
|| ') - '
|| z.column_type
|| ' - '
|| z.error_type
|| ' ' NotHandledDataDictColumns
FROM csmig.csmv$errors z
WHERE z.owner_name IN
(SELECT DISTINCT username FROM csmig.csm$dictusers
) minus
SELECT DISTINCT z.owner_name
|| '.'
|| z.table_name
|| '('
|| z.column_name
|| ') - '
|| z.column_type
|| ' - '
|| z.error_type
|| ' ' DataDictConvCLob
FROM csmig.csmv$errors z
WHERE z.error_type ='CONVERTIBLE'
AND z.column_type = 'CLOB'
AND z.owner_name IN
(SELECT DISTINCT username FROM csmig.csm$dictusers
ORDER BY NotHandledDataDictColumns
/Sorry to have made the thread so big but to make sure and give a complete picture of the issue pasted the csscan contents. Request the PRO's to help us in this issue.You have convertible data in the application tables. CLOB or not, such data prevents csalter.plb from changing the character set.
You are on 11.2.0.3, so use the DMU (http://www.oracle.com/technetwork/products/globalization/dmu/overview/index.html). It can cope with such data.
-- Sergiusz -
Changing Character Set from AL16UTF16 to AL32UTF8
Hi,
I am stuck with a requirement to change the Character Set from AL16UTF16 to AL32UTF8.
I am trying to install the Oracle Content Database & the installer expects the target database to have a Character Set of AL32UTF8. The current Character Set of the Database is AL16UTF16. I am unable to change the Character set as it simply complains that AL32UTF8 is not a super-set of AL16UTF16.The documents that I have consulted mention that such a transitionis not recommended.
How do I convince the installer to continue the installation with AL16UTF16 ? Or, is it possile at all to change the Character Set from AL16UTF16 to AL32UTF8 ?
Please do let me know your thoughts on this.
Regards,
SandeepIs your data size above GBs? If not this might help before installation I guess ->
Changing the Database Character Set of an Existing Database
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
Kind regards,
Tonguç -
Characterset change from WE8ISO8859P1 to AL32UTF8
Hi,
I have restore the rman on new server oracle 11.2.0.3 (Previous backup was of oracle 10.2.0.4).
Then I have successfully upgrade the database to oracle 11g but issue which I am facing right now is that the old database have the character set WE8ISO8859P1 which is now upgraded to oracle 11.2.0.3 database server.
My required character set is AL32UTF32.
Now is there any way that while restoring the rman backup of oracle 10.2.0.4 on new server I set the character set to AL32UTF32.
Thank you for your cooperation.
Kind Regards,
Adnan HamdussalamIt means that either I have to change it before backup or after perform the full upgrade on new server oracle 11g and then convert the character set. Am I right?Yes, You are right.
I think as you are changing from WE8ISO8859P1 to AL32UTF8, so you do not need any tool.
Must read note,
*Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) [ID 260192.1]* -
Changing the Database Character Set From WE8MSWIN1252 to AR8MSWIN1256
good morning everybody,
I need your help to know all step which it is necessary to follow to change the Database Character Set From WE8MSWIN1252 to AR8MSWIN1256
thank youIf you have not already done so, read up on Character Set Migration and using the CSSCAN tool to verify the database before making any changes.
-
Changing database character set from US7ASCII to AL32UTF8
Our database is running on Oracle database 10.1.0.4.0 (AIX) The following are its parameters:
SQL> select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
VALUE
US7ASCII
We would like to change the database character set to AL32UTF8. After following Metalink notes: 260192.1 (which helped us resolve "Lossy" and "Truncated" data, the final output of the CSSCAN utility is:
[Scan Summary]
All character type data in the data dictionary are convertible to the new character set
All character type application data are convertible to the new character set
[Data Dictionary Conversion Summary]
The data dictionary can be safely migrated using the CSALTER script
We have no (0) Truncation and Lossy entries on the .txt file. We only have Changeless and Convertible. Now accdg to the documentation, we can do a FULL EXP and FULL IMP. But it did not detail how to do the conversion on the same database. The discussion on the document tells how to do it from one database to another database. But how about on the same database?
We cannot use CSALTER as stated on the document.
(Step 6
Step 12
12.c) When using Csalter/Alter database to go to AL32UTF8 and there was NO "Truncation" data, only "Convertible" and "Changeless" in the csscan done in point 4:)
After performing a FULL export of the database, how can we change its character set? What do we need to do the the existing database to change its character set to AL32UTF8 before we import back our dump file into the same database?
Please help.There you are! Thanks! Seems like I am right in my understanding about the Oracle Official Documentation. Thanks!
Hmmmmm...when you say:
*"you can do selective export of only convertible tables, truncate the tables, use CSALTER, and re-import."*
This means that:
1. After running csscan on database PROD, i will take note of the convertible tables in the .txt output file.
2. Perform selective EXPORT on PROD (EXP the convertible tables)
3. Truncate the convertible tables on PROD database
4. Use CSALTER on PROD database
5. Re-import the tables into PROD database
6. Housekeeping.
Will you tell me if these steps are the correct one? Based on our scenario: This is what i have understood referring to the Official Doc.
Am i correct?
I really appreciate your help Sergiusz. -
Running instances with different character set WE8MSWIN1252 and AL32UTF8
We have db instances running AL32UTF8 character set and our applications are built around it, however we have request to create instances using WE8MSWIN1252 character set for another application without bringing in new h/w (server).
what are the ways to implement it?
Edited by: raygear on Aug 23, 2012 7:06 PMWhat is the problem? Run DBCA in the advanced mode and specify the required database character set for the new database.
-- Sergiusz -
Some Arabic Characters missing thru dblink from AR8ISO8859P6 to AL32UTF8
Hello all,
we have two databases, one with AR8ISO8859P6 character set, and the other is AL32UTF8. When we try to access the value of the former database from the AL32UTF8, some of the arabic characters are shown as reversed question marks. If anybody knows a fix, or, workaround , please let me knowHello,
Are you using AL32UTF8 for the PlsqlNLSLanguage parameter in your DAD?
Regards,
Arie. -
Chang Charactor set WE8MSWIN1252 to AL32UTF8 for creating RCU
Hi
how can I chang the Charactor set for creating RCU,
Thanks,
Sri.Balaa wrote:
Sri,
Follow the below steps,
conn / as sysdba
col parameter format a30
col value format a30
SELECT view_name FROM dba_views WHERE view_name LIKE '%NLS%';
SELECT * FROM v$nls_parameters;
SHUTDOWN IMMEDIATE;
STARTUP RESTRICT;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE CHARACTER SET AL32UTF8;
-- if the above fails:
ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
SHUTDOWN IMMEDIATE;
STARTUP;
SELECT * FROM v$nls_parameters;
Thanks,
Balaa...
Absolutely the INCORRECT thing to do !!
This will result in corruption of your database that you cannot recover from.
Review MOS Doc - 260912.1
Difference between NLS_CHARACTERSETAL32UTF8 & NLS_CHARACTERSET WE8MSWIN125
Supported methods are documented - Character Set Migration
Maybe you are looking for
-
Activation failed in DSO for BI 7
Hi, I have an existing custom DSO. I want a add a new infoobject ZMATERIAL which has ZMATL_GRP as attribute. I have firstly added ZMATERIAL at data source and acivated . DTP is already activated. Now I have added ZMATERIAL in DSO and trying to ac
-
Hi, I have a question on Human Task component in BPEL. How do we configure the identity store for users . I mean i did exported some users onto my local machine following the link in the documentation. But how to work on the Human Task at the client
-
OEM agent taking too much db time
Hi, In my db, the OEMAgent was always the top consumer of CPU and IO times (because of the dynamic sql code?). The violating SP is attached at the end. For some reason, it is getting called thousands of times. Is this normally? What is the reason? Ho
-
Best Ideas for Analog video...
I'm doing a low end high school football team video. Unfortunatelly it was shot by a parent that doesn't have the latest camera technology. It was shot in analog video. I looked into some Analog to Digital Video converters. http://www.nextag.com/CHAN
-
Why when I e-mail a PDF form, does the recipient get a blank form?
Why when I e-mail a PDF form, does the recipient get a blank form?