ORA:12712
hi...
my DB having WE8ISO8859P1 character set but I need to modify AL32UTF8
ALTER DATABASE CHARACTER SET UTF8;
If I modify that it gives the fallowing error
ORA-12712: new character set must be a superset of old character set
please give solution ........
Thanks,
1. backup your database
2. use exp to export your source database, character should be set as WEB8ISO8859P1
3. use imp to import into your target database, character should be set as UTF8 or AL32UTF8
4. use tool : csscan to check if there are characters which can not convert successfully.
Guide for csscan:
1. use sys to create a user account for csscan
sqlplus "/ as sysdba"
SQL>@?/rdbms/admin/csminst.sql
2.in dos command, you can execuse like this:
csscan FULL=Y FROMCHAR=WEB8ISO8859P1 TOCHAR=UTF8 LOG=WEB8check.log CAPTURE=Y ARRAY=1000000 PROCESS=2
3.you can check your WEB8check.log, if it can not convert, delete that row and insert again.
Good luck
Bruce
Similar Messages
-
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 -
ORA-12712: new character set must be a superset of old character ...-
Dear all ,
i have a problem with oracle database,
server configuration oracle 10g, solaris 9, sparc processor 64 bit,
i altered database character set to UTF8, whe i return database to old seeting ISO 8859-6
i got this error ORA-12712: new character set must be a superset of old character set.
anyone can help me and let me know how can i solve this error?
thanks
GasirYou should recreate a new database and use export/import to transfer data from the existing UTF8 database to the new ISO 8859-6 database according to the ]Globalization Guide.
-
Hi
I´m trying to change my character set to UTF8 but i dont know what characterset do i have?
I run the follow syntax and only i'm more confused:
SQL> show parameter nls_language;
NAME TYPE VALUE
nls_language string AMERICAN
SQL> select * from NLS_SESSION_PARAMETERS;
PARAMETER VALUE
NLS_LANGUAGE SPANISH
NLS_TERRITORY SPAIN
NLS_CURRENCY
NLS_ISO_CURRENCY SPAIN
NLS_NUMERIC_CHARACTERS ,.
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD/MM/RR
NLS_DATE_LANGUAGE SPANISH
NLS_SORT SPANISH
NLS_TIME_FORMAT HH24:MI:SSXFF
NLS_TIMESTAMP_FORMAT DD/MM/RR HH24:MI:SSXFF
PARAMETER VALUE
NLS_TIME_TZ_FORMAT HH24:MI:SSXFF TZR
NLS_TIMESTAMP_TZ_FORMAT DD/MM/RR HH24:MI:SSXFF TZR
NLS_DUAL_CURRENCY
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
17 filas seleccionadas.
SQL> select * from nls_database_parameters where parameter='NLS_NCHAR_CHARACTERSET';
PARAMETER VALUE
NLS_NCHAR_CHARACTERSET AL16UTF16
I remember when i installed my database, the character set was WE8MSWIN1252
I read that the NLS_LANG is composed by <language>_<territory>. <characterset>
But with the querys i can't understad if i have in my NLS LANGUAGE is spanish or american or what character set i have WE8MSWIN1252 or AL16UTF16
If i try to run
ALTER DATABASE CHARACTER SET UTF8 (or any other)
and i have the follow message error.
ORA-12712 new character set must be a superset of old character set
then i´m a little confused. I'm reading the information but i don't understand it.
Someone can tell me why my querys tell different things.
Thanks to all
Alexwhat is the difference between...sesion , instance and database parameters? for NLS_LANG.Session settings can generally override instance setting that can generally override database settings.
Note also that NLS_LANG has 3 parts:
- territory
- language
- character set.
Territory and language can be redefined in the client side using ALTER SESSION in your session but character set cannot be redefined using ALTER SESSION. You must redefine it at OS level with the environment variable (or registy setting under Windows).
See the reference document the Globalization Guide http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96529/ch3.htm#49632 -
Error while running package ORA-06553: PLS-553 character set name is not re
Hi all.
I have a problem with a package, when I run it returns me code error:
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
The full context of the problem is this:
Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
select * from nls_database_parameters;
Result from the old
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET US7ASCII
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
Result from the new
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET US7ASCII
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
Database Characterset is US7ASCII
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
alter database character set INTERNAL_CONVERT WE8MSWIN1252
Updating character set in controlfile to WE8MSWIN1252
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
RegardsOhselotl wrote:
Hi all.
I have a problem with a package, when I run it returns me code error:
ORA-06552: PL/SQL: Compilation unit analysis terminated
ORA-06553: PLS-553: character set name is not recognized
The full context of the problem is this:
Previously I had a developing data base, then was migrated to a new server. After that I started to receive the error, so I began to check for the solution.
My first move was compare the “old database” with the “new database”, so I check the nls parameters, and this was the result:
select * from nls_database_parameters;
Result from the old
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET US7ASCII
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
Result from the new
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET US7ASCII
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 10.2.0.1.0
As the result was identical, I decided to look for more info in the log file of the new database. What I find was this:
Database Characterset is US7ASCII
Threshold validation cannot be done before catproc is loaded.
Threshold validation cannot be done before catproc is loaded.
alter database character set INTERNAL_CONVERT WE8MSWIN1252
Updating character set in controlfile to WE8MSWIN1252
Synchronizing connection with database character set information
Refreshing type attributes with new character set information
Completed: alter database character set INTERNAL_CONVERT WE8MSWIN1252
*********************************************************************This is an unsupported method to change the characterset of a database - it has caused the corruption of your database beyond repair. Hopefully you have a backup you can recover from. Whoever did this did not know what they were doing.
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
alter database character set US7ASCII
ORA-12712 signalled during: alter database character set US7ASCII...
Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_3132.trc:
RegardsThe correct way to change the characterset of a database is documented - http://docs.oracle.com/cd/B19306_01/server.102/b14225/ch11charsetmig.htm#sthref1476
HTH
Srini -
Changing CHARACTER SET in OracleXE
Because this is my first post in this forum I like to say first "Hello" !
I do my first steps after installing OracleXE (OracleXEUnv.exe). In the database informations I saw that the Character Set (NLS_CHARACTERSET) is "AL32UTF8"., but I want to change it to "WE8MSWIN1252".
When I tried the SQL command "ALTER DATABASE CHARACTER SET WE8MSWIN1252;" but the system shows the message "ORA-12712: Der neue Zeichensatz muss eine Obermenge des alten Zeichensatzes sein".
How can I change the NLS_CHARACTERSET parameter ? Could it be that I have to deinstall this version und use instand the western european version (OracleXE.exe) ?
Kind regards, MichaelCould it be that I have to deinstall this version und
use instand the western european versionYup. You already knew the answer :) -
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?
thankshere 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 -
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 -
Not able to change NLS_CHARACTERSET
Hi ,
I want to change the character set of the data for supporting the Indian Languages.
When I used the beow command "alter database character set AL32UTF8;"
I got the below error
alter database character set AL32UTF8
ERROR at line 1:
ORA-12712: new character set must be a superset of old character set
Database properties are listed below
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8MSWIN1252
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
PARAMETER VALUE
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 11.1.0.6.0
Thanks in advance
RajeevPlease
do NOT use alter database in 10G or higher
do NOT use alter database (9ii) or Csalter without using Csscan
There is a step by step guide on My Oracle Support( https://support.oracle.com )
Note:260192.1 Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode)
it might also be usefull to read
Note:788156.1 AL32UTF8 / UTF8 (Unicode) Database Character Set Implications
note that there are on various "DBA" websites older and or incomplete versions of this guide and / or complete wrong "steps" to change to AL32UTF8
the might "appear" to work at first sight but often provoke data corruption. -
Can i Change Character set WE8ISO8859P1 TO AR8MSWIN1256 IN ORACLE 8i
I tried to change character set from WE8ISO8859P1 TO AR8MSWIN1256 on oracle 8i database.
Getting the follwoing error for both character set and National character set.
ORA-12712:New character set must be a superset of old character set.
My question can i change or have to do export and import in arabic character set DB.
nullHello Sarath,
There is an extension CODE PAGE with OPEN DATASET stmt.
Can you please elaborate which character set you want to write to the application server?
BR,
Suhas -
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 -
Question for experts/ wrapping - data pump
Hello All,
In am using ORACLE 10.2.0.4.0
i have an issue while export / import wrapped procedures:
I have some procedures / packages that are wrapped and when i do export for their related schema and then import it to the database, i got the below error
Compilation errors for PROCEDURE PROC_NAME
Error: PLS-00753: malformed or corrupted wrapped unit
Line: 1
Text: CREATE OR REPLACE PROCEDURE "PROC_NAME" wrapped
After i did many tests on this scenario i Noted that:
This error is not appearing on all procedures, there are some that will be corrupted after the import and some will not be corrupted.
After i did the normal import export, i found that the character set of the imp/exp is different then the one of the database, so i changed the character set of the database to be the same as the one used by the import, i redo my tests and i found that this solved the issue of normal imp/exp, so now and if i am doing normal exp/imp the recompilation of procedures will not fail after the normal old import. but at this stage the imp/exp character set has changed again.
The character set of my db was : AR8MSWIN1256 and when i did exp/imp it was for exp /imp AR8ISO8859P6, so i changed the one of my db to AR8ISO8859P6 , after changing the database character set to AR8ISO8859P6 the recompilation was working fine for the normal exp / imp, but now the character set for import/ export changed to AR8MSWIN1256 !! why ?
The Data pump export import was not solved even after changing the character set of the database, the procedures were imported with errors and it was fixed after recompiling it.
My issue that i have too many clients and i am not able always to change the character set of the database because i may face ERROR "ORA-12712: new character set must be a superset of old character set"
Hope the above description is clear,
Any suggestions or ideas to solve the issue of wrapped procedures with expdp/impdp? can i force certain character set for the expdp/impdp ? knowing that with release 10.2.0.1.0 the expdp/impdp is totally not working with the wrapped proceduresAny ideas?
-
Migrate database from UTF-8 to AL32UTF8
We've heard that support for the UTF-8 characterset is going to peter out. Our databases are all in the UTF-8 characterset, so we are considering migrating to AL32UTF8. Any issues we need to consider, or is it simply a case of switching the database characterset? The globalization whitepapers I've read don't seem to address this kind of migration.
Doc ID: Note:123670.1
Subject: Use Scanner Utility before Altering the Database Character Set
Type: BULLETIN
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 02-NOV-2000
Last Revision Date: 30-OCT-2003
A) Purpose. ----------- Before altering the character set of a database, check the convertibility of the data before converting. Character set conversions can cause data loss or data corruption. The Character Set Scanner utility provides this 2 features: 1) convertibility check of existing data and potential issues. The Scanner checks all character data in the database including the data dictionary and tests for the effects and problems of changing the character set encoding (characterset). At the end of the scan, it generates a summary and exception report of the database scan. 2) from csscan V1.1 onwards it allows you also to do a check if there is no data in the database that is incorrectly stored. This is used in [NOTE:225938.1] Database Character Set Healthcheck This note gives an example on how the output of the csscan tool looks like and some live examples of how to convert the characterset. Please use the following note: [NOTE:225912.1] Changing the Database Character Set - an Overview as a complete guide to plan the change of the database character set. B) Installation and setup. -------------------------- IMPORTANT: Check for the latest version on technet of the csscan tool for your platform: http://technet.oracle.com/software/tech/globalization/content.html and use this. ( [NOTE:179843.1] Versioning of the Character Set Scanner ) There is one know problem with the characterset scanner for 817: see [BUG:3043474] To install the Character Set Scanner, you must have DBA privileges on the Oracle database. If you encounter "CSS-0xxxx" type errors, first look in the "Character Set Scanner Error Messages " section of above docset. Run csminst.sql to create the needed user and tabels, You can modify the default tablespace for CSMIG by editing the csminst.sql script. Modify the following statement in csminst.sql to assign your preferred tablespace to CSMIG as follows: ALTER USER csmig DEFAULT TABLESPACE tablespace_name; Then run csminst.sql using these commands and SQL statements: cd $ORACLE_HOME/rdbms/admin set oracle_sid=<your SID> sqlplus "system/manager" SQL>spool csminst.log SQL> START csminst.sql check the csminst.log for errors. or for 9i: cd $ORACLE_HOME/rdbms/admin set oracle_sid=<your SID> sqlplus "/ as sysdba" SQL>spool csminst.log SQL> START csminst.sql check the csminst.log for errors. [NOTE:232242.1] Character set migration utility schema not installed in 9i / ORA-942 during csminst.sql Now you can run the scanner against this database. C:\>csscan help=y gives the help screen, we will show here some sample outputs of full database scans using the command line. See also Chapter 11 "Character Set Scanner" of the Oracle9i Database Globalization Support Guide Release 2 (9.2) Part Number A96529-01 C) Character Set Scanner Compatibility. --------------------------------------- see [NOTE:179843.1] Versioning of the Character Set Scanner D) There are 3 possible conversion statuses possible ---------------------------------------------------- *** ***************** *** Scanner statuses *** ***************** The Scanner utility reports 3 types of conversion status for each table and row: 1/ CHANGELESS which leads to consider that the object needs no conversion, the codepoint dous not change between the two charactersets for those characters. 2/ CONVERTIBLE which leads to consider that the object needs conversion by export/import. (the target charactersets is NO binary superset of the source characterset) The character itself is know in both charactersets but has another codepoint This is why the ALTER DATABASE CHARACTER SET <new_character_set>; command is enforcing that the NEW characterset needs to be a BINARY superset of the old one. So you wan't be allowed to use ALTER DATABASE CHARACTER SET <new_character_set>; 3/ EXCEPTIONAL which leads to consider that the data needs manual updates before conversion or that you have invalid data in the database. Note that the scanner cannot "see" what type of character is stored. It can only compare codepoints and look them up in in the characterset conversion lists of oracle. The scanner checks if in the target characterset the codepoint of the source characterset is a valid codepoint, or that there are mappings to another codepoint it has no knowlegde of the character it suppose to represent. This is a problem if you have stored incorrect data in the database by bypassing the NLS layers. But normally this will lead to the reporting of exceptional data. This information is clearly reported in the 2 following reports automatically generated by the Scanner utility. *** *********************************** *** Reports SCAN.TXT and SCAN.ERR *** *********************************** 1/ SCAN.TXT => objects in the data dictionary requiring an action such as renaming a table => application data requiring an action such exporting/importing data to be converted, updating data, rebuilding indexes, modifying column sizes Example [Data Dictionary Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 608,343 0 1 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 CLOB ---------------- -------------- -------------- -------------- -------------- Total 638,101 0 1 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 16 0 0 16 CHAR 2 1 1 4 LONG 0 0 0 0 CLOB 0 0 0 0 ---------------- -------------- -------------- -------------- -------------- Total 18 1 1 20 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ----------------------------------------- ---------------- ---------------- SYS.OBJ$ 0 1 U1.T_EXCEPTIONAL 0 1 U1.T_CONVERTIBLE 1 0 ----------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ----------------------------------------- ---------------- ---------------- SYS.OBJ$|NAME 0 1 U1.T_EXCEPTIONAL|C1 0 1 U1.T_CONVERTIBLE|C1 1 0 ----------------------------------------- ---------------- ---------------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) ---------------------------------------------------------------------------- SYS.I_OBJ2 on SYS.OBJ$(NAME) U1.I_T_CONVERTIBLE on U1.T_CONVERTIBLE(C1) --------------------------------------------------------------------------- 2/ SCAN.ERR => lists rowids of rows for which data is to be updated because of an EXCEPTIONAL status Example User : SYS Table : OBJ$ Column: NAME Type : VARCHAR2(30) Number of Exceptions : 1 Max Post Conversion Data Size: 33 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAASAABAAAAXjABF exceed column size 33 table_M-H_gM-Erer_drM-Bles_franM-5ais ------------------ ------------------ ----- ------------------------------ User : U1 Table : T_EXCEPTIONAL Column: C1 Type : CHAR(12) Number of Exceptions : 1 Max Post Conversion Data Size: 24 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAxDAAFAAAABDAAA exceed column size 24 M-EM-IM-HM-KM-LM-]M-NM-OM-AM-BM-QM-@ ------------------ ------------------ ----- ------------------------------ *** *************************** *** 3 statuses => 3 approaches *** *************************** 1/ When objects are in CHANGELESS status, they need not be converted. Issue the ALTER DATABASE CHARACTER SET statement on the database. This is possible when, and only when, the new character set is a strict superset of the current character set. 2a/ When a lot of objects are in CONVERTIBLE status, the data can be converted, and must be converted by Export: FULL Export + creation of a new database + FULL Import 2b/ When the database is large and only a few tables are in CONVERTIBLE status, whereas all the others are CHANGELESS, prefer the following method: Export selected tables + ALTER DATABASE CHARACTER SET if possible + Import the selected convertible tables (import will convert appropriately) 3/ However, if there are some cases in EXCEPTIONAL status reported, these exceptions must be handled one by one, and fixed first before using any of the above methods to do the conversions. This involves modifying data and/or modify structures to eliminate those exceptions. Again, see [NOTE:225912.1] Changing the Database Character Set - an Overview for more info en on how to deal with exceptional data. E) This are some sample outputs and live examples: -------------------------------------------------- *** Test1 on a WE8ISO8859P9 character set database to be converted to UTF8 1/ Create 4 tables : Table "table_� _gérer_drôles_français": table name is to be converted Table T_STANDARD: no data change required Table T_CONVERTIBLE: data are to be converted Table T_EXCEPTIONAL: data are to be updated before conversion $ NLS_LANG=american_america.WE8ISO8859P9 SQL> connect u1/u1 Connected. SQL> create table "table_� _gérer_drôles_français" (c1 char(16)); Table created. SQL> insert into "table_� _gérer_drôles_français" values ('A'); 1 row created. SQL> create table T_STANDARD (c1 char(12)) ; Table created. SQL> insert into T_STANDARD values ('aeiouaieou'); 1 row created. SQL> create table T_CONVERTIBLE (c1 CHAR(12)); Table created. SQL> create index i_t_convertible on t_convertible(c1) ; Index created. SQL> insert into T_CONVERTIBLE values ('éè� '); 1 row created. SQL> create table T_EXCEPTIONAL (c1 char(12)); Table created. SQL> insert into T_EXCEPTIONAL values ('éè� ùäöüêôîâ'); 1 row created. SQL> select * from T_EXCEPTIONAL; C1 ------------ éè� ùäöüêôîâ SQL> commit; Commit complete. 2/ Run the Character Set Scanner utility to provide report. ----------------------------------------------------------- Before running csscan, be aware of the following parameters: CAPTURE=Y records the ROWID for each cell of data that is problematic; use it only when there are small amounts of problem data because it might "flood" the database if lots of problematic data is expected. The ARRAY and PROCESS parameters for large databases are vital: * ARRAY can be set to a size in bytes which best represents the available real memory at scanner run time; the higher the better. * PROCESS spawns a process for parallel scanning and should be set to the number of available CPU's on the system which is hosting the database. $ csscan system/manager FULL=Y FROMCHAR=WE8ISO8859P9 TOCHAR=UTF8 CAPTURE=Y Character Set Scanner: Release 8.1.7.0.0 - Production on Thu Nov 9 10:36:15 2000 (c) Copyright 2000 Oracle Corporation. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production With the Partitioning option JServer Release 8.1.7.0.0 - 64bit Production Enter array fetch buffer size: 10240 > Enter number of scan processes to utilize(1..32): 1 > 4 Enumerating tables to scan... . process 1 scanning SYS.SOURCE$[AAAABAAABAAAADAAAA] . process 2 scanning SYS.SOURCE$[AAAABAAABAAAA8/AAA] . process 3 scanning SYS.TAB$ ...... . process 4 scanning U1.T_EXCEPTIONAL . process 4 scanning U1.table_� gérerdrôles_français . process 4 scanning U1.T_STANDARD . process 4 scanning U1.T_CONVERTIBLE . process 4 scanning SYS.SYN$ .... . process 3 scanning SYS.FILE$ Creating Database Scan Summary Report... Creating Individual Exception Report... Scanner terminated successfully. 3/ Examine the 2 provided reports : scan.txt and scan.err. ---------------------------------------------------------- Report scan.txt --------------- Database Scan Summary Report ... [Scan Summary] Some character type data in the data dictionary are not convertible to the new character set Some character type application data are not convertible to the new character set [Data Dictionary Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- ---------------- VARCHAR2 608,343 0 1 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 ---------------- -------------- -------------- -------------- ---------------- Total 638,101 0 1 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- ---------------- VARCHAR2 18 0 0 18 CHAR 1 1 1 3 LONG 0 0 0 0 ---------------- -------------- -------------- -------------- ---------------- Total 19 1 1 21 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional -------------------------------------------- ---------------- ---------------- SYS.OBJ$ 0 1 U1.T_CONVERTIBLE 1 0 U1.T_EXCEPTIONAL 0 1 -------------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional -------------------------------------------- ---------------- ---------------- SYS.OBJ$|NAME 0 1 U1.T_CONVERTIBLE|C1 1 0 U1.T_EXCEPTIONAL|C1 0 1 -------------------------------------------- ---------------- ---------------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) ------------------------------------------------------------------------------ SYS.I_OBJ2 on SYS.OBJ$(NAME) U1.I_T_CONVERTIBLE on U1.T_CONVERTIBLE(C1) ------------------------------------------------------------------------------ Report scan.err --------------- Database Scan Individual Exception Report ... [Application data individual exceptions] User : SYAR2(30) Number of Exceptions : 1 Max Post Conversion Data Size: 33 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAASAABAAAAXjABF exceed column size 33 table_M-H_gM-Erer_drM-Bles_franM-5ais ------------------ ------------------ ----- ------------------------------ User : U1 Table : T_EXCEPTIONAL Column: C1 Type : CHAR(12) Number of Exceptions : 1 Max Post Conversion Data Size: 22 ROWID Exception Type Size Cell Data(first 30 bytes) ------------------ ------------------ ----- ------------------------------ AAAAxDAAFAAAABDAAA exceed column size 22 M-EM-IM-HM-KM-LM-NM-OM-AM-BM-QM-@ ------------------ ------------------ ----- ------------------------------ 4/ Actions to take before character set conversion. --------------------------------------------------- a/ The table named "table_� _gérer_drôles_français" needs to be recreated with another name. SQL> alter table "table_� _gérer_drôles_français" rename to table_a_gerer_droles_francais; Table altered. b/ Export table U1.T_CONVERTIBLE: $ NLS_LANG=american_america.WE8ISO8859P9 $ exp userid=U1/U1 tables=T_CONVERTIBLE . . exporting table T_CONVERTIBLE 1 rows exported Export terminated successfully without warnings. c/ Since the exception refers to a too small column size, enlarge the column size of U1.T_EXCEPTIONAL.C1: SQL> alter table t_exceptional modify (c1 char(24)); Table altered. 5/ Perform another scan check before character set conversion. -------------------------------------------------------------- $ csscan system/manager FULL=Y FROMCHAR=WE8ISO8859P9 TOCHAR=UTF8 CAPTURE=Y => reports scan.txt: Datatype Changeless Convertible Exceptional Total --------------- -------------- -------------- ---------------- ---------------- VARCHAR2 608,344 0 0 608,344 CHAR 2 0 0 2 LONG 29,756 0 0 29,756 --------------- -------------- -------------- ---------------- ---------------- Total 638,102 0 0 638,102 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- ---------------- -------------- -------------- ---------------- VARCHAR2 18 0 0 18 CHAR 1 2 0 3 LONG 0 0 0 0 ---------------- ---------------- -------------- -------------- ---------------- Total 19 2 0 21 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ---------------------------------------------- ---------------- ---------------- U1.T_CONVERTIBLE 1 0 U1.T_EXCEPTIONAL 1 0 ---------------------------------------------- ---------------- ---------------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ---------------------------------------------- ---------------- ---------------- U1.T_CONVERTIBLE|C1 1 0 U1.T_EXCEPTIONAL|C1 1 0 ---------------------------------------------- ---------------- ---------------- => in scan.err, no more exception 6/ Last actions to take before character set conversion ------------------------------------------------------- Export table U1.T_EXCEPTIONAL: $ exp U1/U1 tables=T_CONVERTIBLE,T_EXCEPTIONAL Export: Release 8.1.7.0.0 - Production on Thu Nov 9 13:06:53 2000 About to export specified tables via Conventional Path ... . . exporting table T_CONVERTIBLE 1 rows exported . . exporting table T_EXCEPTIONAL 1 rows exported Export terminated successfully without warnings. 7/ Perform character set conversion ------------------------------------ Follow the steps in: [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set but you will get: SQL> alter database character set UTF8; alter database character set UTF8 * ERROR at line 1: ORA-12712: new character set must be a superset of old character set Since the character set UTF8 is not allowed in alter database, use FULL EXPORT , recreate the database with UTF8 character set, FULL IMPORT. See [NOTE:15095.1] Export/Import and NLS Considerations for more info on these steps. 8/ Actions to take after character set conversion. -------------------------------------------------- a/ Check the imported data of tables U1.T_CONVERTIBLE and U1.T_EXCEPTIONAL: Import: Release 8.1.7.0.0 - Production on Thu Nov 9 14:27:54 2000 import done in WE8ISO8859P9 character set and US7ASCII NCHAR character set import server uses UTF8 character set (possible charset conversion) . importing U1's objects into U1 . . importing table "T_CONVERTIBLE" IMP-00019: row rejected due to ORACLE error 1401 IMP-00003: ORACLE error 1401 encountered ORA-01401: inserted value too large for column Column 1 éè� 0 rows imported . . importing table "T_EXCEPTIONAL" IMP-00019: row rejected due to ORACLE error 1401 IMP-00003: ORACLE error 1401 encountered ORA-01401: inserted value too large for column Column 1 éè� ùäöüêôîâ 0 rows imported See [NOTE:119119.1] UTF8 Database Character Set Implications section "2.2.1 Example Export / Import into a UTF-8 Database" why this happens. b/ Change the column width of the tables and reimport the data: SQL> alter table U1.T_CONVERTIBLE modify (C1 CHAR(16)); Table altered. SQL> alter table U1.T_EXCEPTIONAL modify (C1 CHAR(36)); Table altered. $ imp U1/U1 FULL=Y IGNORE=Y Import: Release 8.1.7.0.0 - Production on Thu Nov 9 14:23:18 2000 import done in WE8ISO8859P9 character set and US7ASCII NCHAR character set import server uses UTF8 character set (possible charset conversion) . importing U1's objects into U1 . . importing table "T_CONVERTIBLE" 1 rows imported . . importing table "T_EXCEPTIONAL" 1 rows imported Import terminated successfully without warnings. c/ Check integrity for all CONVERTIBLE and EXCEPTIONAL objects: SQL> select * from U1.TABLE_A_GERER_DROLES_FRANCAIS; C1 ---------------- A SQL> select * from U1.T_CONVERTIBLE; C1 ---------------- éè� SQL> select * from U1.T_EXCEPTIONAL; C1 ------------------------------------ éè� ùäöüêôîâ *** on an US7ASCII database containing WE8ISO8859P1 characters *** to be altered to WE8ISO8859P9 Steps 1 and 2 are identical 3/ Run the Character Set Scanner utility to provide report. ----------------------------------------------------------- The database is US7ASCII but contains some WE8ISO8859P1 characters; then by setting FROMCHAR=WE8ISO8859P1, the scanner treats all cells as if they are from WE8ISO8859P1 and gives a more acurate result. $ csscan USERID=system/manager FULL=Y CAPTURE=Y FROMCHAR=WE8ISO8859P1 TOCHAR=WE8ISO8859P9 ...... . process 4 scanning U1.table_� gérerdrôles_français . process 4 scanning U1.T_STANDARD . process 4 scanning U1.T_CONVERTIBLE . process 4 scanning U1.T_EXCEPTIONAL ......t... Creating Individual Exception Report... Scanner terminated successfully. $ 4/ Examine the 2 provided reports : scan.txt and scan.err. ---------------------------------------------------------- Report scan.txt --------------- Database Scan Summary Report [Data Dictionary Conversion Summary] Datatype Changeless Convertible Exceptional Total --------------- -------------- -------------- -------------- -------------- VARCHAR2 608,314 0 0 608,314 CHAR 2 0 0 2 LONG 29,754 0 0 29,754 --------------- -------------- -------------- -------------- -------------- Total 638,070 0 0 638,070 [Application Data Conversion Summary] Datatype Changeless Convertible Exceptional Total ---------------- -------------- -------------- -------------- -------------- VARCHAR2 14 0 0 14 CHAR 4 0 0 4 LONG 0 0 0 0 ---------------- -------------- -------------- -------------- -------------- Total 18 0 0 18 [Distribution of Convertible Data per Table] USER.TABLE Convertible Exceptional ---------------------------- ------------ ----------- ---------------------------- ------------ ----------- [Distribution of Convertible Data per Column] USER.TABLE|COLUMN Convertible Exceptional ---------------------------- ------------ ----------- ---------------------------- ------------ ----------- [Indexes to be Rebuilt] USER.INDEX on USER.TABLE(COLUMN) -------------------------------------------------- -------------------------------------------------- Report scan.err --------------- Database Scan Individual Exception Report [Application data individual exceptions] 5/ Actions to take before character set conversion. --------------------------------------------------- In this case, execute the ALTER DATABASE CHARACTER SET which does not change the actual character codes, but only changes the character set declaration. To prevent any possible data loss, perform a FULL database backup before altering the database character set. 6/ Perform character set conversion. ------------------------------------ Follow the steps in: [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set 7/ Actions to take after character set conversion. -------------------------------------------------- Check integrity for all EXCEPTIONAL objects: SQL> select * from U1."table_� _gérer_drôles_français"; C1 ---------------- A SQL> select * from U1.T_CONVERTIBLE; C1 ------------ éè� SQL> select * from U1.T_EXCEPTIONAL; C1 ------------ éè� ùäöüêôîâ RELATED DOCUMENTS ----------------- [NOTE:15095.1] Export/Import and NLS Considerations [NOTE:119119.1] UTF8 Database Character Set Implications [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set [NOTE:66320.1] Changing the Database Character Set or the Database National Character Set [NOTE:119119.1] UTF8 database character set implications [BUG:1611255] CHARACTER SET SCANNER GETS SEGMENTATION FAULT WHEN ARRAY AND PROCESS ARE LARGE [NOTE:232242.1] Character set migration utility schema not installed in 9i / ORA-942 during csminst.sql
Joel P�rez -
Changing the Database characterset
Hi,
My oracle 9i database characterset is AL32UTF8.
I wanted to change this to UTF8 for some testing purpose...
After few days i need to reset this characterset back to AL32UTF8.
how should i proceed on this?
Plz adivice.....
Regards,
Ashok Kumar.GThanks Pierre Forstmann,
In metalink i found out the following
In 9i you can't simply use "ALTER DATABASE CHARACTERSET" to go from
AL32UTF8 to UTF8 because UTF8 is a SUB-set of AL32UTF8
(some codepoints which are correct in AL32UTF8 are not known in UTF8)
So you will run into ORA-12712 if you try alter database ....
I hope this makes sense when the database contains data.
suppose if i drop my schema(now the database has no user data) and try to change the database characterset from AL32UTF8 to UTF8 will it impact any other?
and after changing to UTF8 can i import the user data again (say from export file which was taken from a UTF8 database) ?
Regards,
Ashok Kumar.G
Maybe you are looking for
-
Help needed in finding these TCodes..
<b>Hi.. Could you explain the functions and usage of the CICO & EA40 TCode. Please provide the linked documents and PDF's to it. We are working on a performance related issue of a SAP system. How far could this TCode help us in achieving the goal? Ex
-
T-code HRBEN0005 calling different form for open enrollment
Hi, I have to create two different forms for different adjustment reasons for open enrollment(t-code HRBEN0005). But in the config table T74HL we can call only one form so I am looking for an enhancement where i can pass the form name according to t
-
I purchased a Canon EOS 70D and am unable to edit in camera raw and am unable to install the version of camera raw that supports the camera. I am running Windows 7 64 (Current Version) and CS5 Extended ver. 12.04 x64. I have installed Applications Ma
-
Bold 9700 and Visor Mount VM-605
Hello, I am new to this forum and this is my question: I install desktop manager V6 the other day & when i connected my 9700 to it is gave me the option to update the OS on my device I installed it & now my BB Visor Mount Speakerphone VM-605 will no
-
How can I make a simple script that places a spesific InDesign snippet in the document, at cursor point? Just like when draging a snippet in to a document. Im on a Mac