ASCII to character

hie gurus
im looking for an FM to convert ASCII to character or any giudelines to help me achieve my requirement
regards
prince

Hi,
report asciicode.
Parameters : c1 type c.
field-symbols : <n> type x.
data : rn type i.
assign c1 to <n> casting.
move <n> to rn.
write rn.
Fm:n = STRLEN( text ).
i = 0.
do n times
call function URL_ASCII_CODE_GET
trans_char = text+i(1).
i = i + 1.
Perform ur logic with Char_code.
Regards,
Shiva Kumar

Similar Messages

How to convert ascii to character

how to convert ascii to character is there any function module or any code.plz help me in finding this.

Hi,
please go through this
If I give input as 65 (ascill value) I want display 'A'.
Below logic is for convert from character to ascii value.
report Ascii_convert.
*Going from A to 65
data : c value 'A'.
field-symbols : <n> type x.
data : rn type i.
assign c to <n> casting.
move <n> to rn.
write rn.
*Going from 66 to B
data : i type i value 66.
data : x type x.
field-symbols : <fc> type c.
move i to x.
assign x to <fc> casting type c.
move <fc> to c.
write c.
i hope this will help you ,
Raja T

Convert integers to equivalent characters in string - NOT ASCII code character

I have to output my data and associated string information to a string array and then to a spreadsheet file.
I want to do this by converting integers (and other numbers) to an identical string of characters.
I have tried Type Cast with a string constant as the type input but it DOES NOT WORK. Instead, I get the ASCII character whose numerical designation matches the integer, e.g. integer "50" become capital "P".
I want integer "50" to be string "50".
Please advise and no, I do not want to make arrays of clusters.
Solved!
Go to Solution.

I found my answer but only after searching for "Number" conversion rather than "Integer" conversions.
In the Programming palette - String Functions - String/Number Conversion - Number to Decimal String:
"Converts number to a string of decimal digits at least width characters wide or wider if necessary. If number is floating-point, it is rounded to a 64-bit integer before conversion."

How can I read a file with ASCII Special Character into a SQL table using SSIS 2008?

I've tried everything to read this file and am getting no where. Help how can I read this file and load a SQL table?
RS - AscII - 30 (Record Separator)
GS - AscII - 29 (Group Separator)
Thank you for your assistance - Covi
Mark Covian

We can use script component as source/transformation to read the text file and assign the contains to a string. Split the string by chr(30) i.e RS and finally stored into an array or write to the output buffer of the script component.
For example on how to use script component refer this link
http://social.technet.microsoft.com/Forums/en-US/6ff2007d-d246-4107-b77c-624781baab38/how-to-use-substring-in-derived-column-in-ssis?forum=sqlintegrationservices
Regards, RSingh

Ascii table - character matching table

Where can I find a character mapping table for character set WE8ISO8859P1
Olav Torvund
[email protected]

Hi,
that's odd. I got all of them 255 total. Here is a portion of it.
CHR         dec
Y            89
Z            90
[            91
\            92
]            93
^            94
_            95
`            96
a            97
b            98
c            99
CHR         dec
d           100
e           101
f           102
g           103
h           104
i           105
j           106
k           107
l           108
m           109
n           110
CHR         dec
---- ----------U

How can i convert values in my string to ascii characters

Hi guy.
I am wrinting a code but i m stuck, I have a string with (Battle of Midway) in it, Now i want to convert each character in this string with the asci character,,,
String temp = {"Battle of Midway"};
so the ascii will be:
B=66 a=97 t=116 l=108 e=101 o=111 f=102 M=77 i=105 d=100 w=119 y=121
i found all these number for all the charachers, but i donno how to covert this string into ascii characerts... ofcurse i can do it one by one...but is there any class or method i can use for this,,,,, Once i convert all the character (from string) to ascii character THEN i have to convert it back from ascii to character,,
Is anybody has any idea
Thanks alot in Advance

You get get the ascii code for those characters by doing something like:
int ascii = str.charAt(0); //Get ascii value for the first character.
Kaj

How do you output a backspace character?

Hi there,
I'm creating a VI in which I need to output the backspace character to a TCP output. I want the cursor on the terminal to actually back up one character so I'm assuming I need to output the ASCII backspace character. However, I don't know how to do this. I've tried sending out \b but instead of a backspace, the character string is just \b.
Is there a way I can convert an integer to an ASCII character? Or is there another way to do this? Thanks a lot!!
-Mike

If you want to send a \b, then right click on the control and select '\' Codes Display and then enter \b. Otherwise, the characters will be no interpreted correctly. Another way to do it is turn on Hex Display and enter 08.

How to see if a R3 system is an ASCII system??

Hi all,
I must to do an heterogenoues system copy of an R3 4.6C from:
Source System: Windows-Oracle
to:
Target System: AS400-DB2
I'd like to known if the source system is an ASCII system....how to see it??
I must to see the NLS Parameter in V$parameter of the DB???
Any ideas??
Thanks in advanced

what do you mean by "ascii"? character set?
if yes, log onto system, use <sid>adm and call sqlplus:
> sqlplus /nolog
> connect / as sysdba
> select value from v$parameters where parameter = 'NLS_CHARACTERSET';
GreetZ, AH

Function to replace/delete specific character(s) in a string

Hi, experienced CVI guys,
Are there some functions shipped with CVI to replace or delete specific characters in a string?
For example, I want to replace all \/|- with an empty string, or to delete them. What can I do? Loops are too complex.
Original string:
Erasing Device...
\|/- \ \ \\|/-\|/ \
Report
07-Sep-2010, 08:04:55
Result I want is
Erasing Device...
Report
07-Sep-2010, 08:04:55
Thanks.
Solved!
Go to Solution.

labc:
How generic do you want to make your filter?
For our discussion, I'll call your series of characters a text spinner. I'm assuming the number of characters in it may vary, but that the pattern is consistent in the respect: the spinner is made up of characters like \ / | -, each followed by the ASCII backspace (char) 8. (That's 8 cast as a character, which is not the same as '8'.) In your sample spinner pattern, every occurrence of the ASCII backspace is preceded by one of the spinner characters. Let's assume that this pattern is constant.
So what I'd do is search through your input string (yes, using a loop) and copy the input string byte by byte to an output string. If you find an ASCII backspace in the input string, skip it, and overwrite the last character in the output string (which is one of the spinner characters) with the next character in the input string.
Yes, you are using a loop, but it's not too complex.
Here's the whole loop, written as a function.
// filterSpinner function to strip the text spinner characters out of a string.
// The text spinner is made up of \ / | - characters separated by (char) 8 (ASCII backspace)
int filterSpinner(char *inputString, char *outputString)
int inputPtr, outputPtr = 0;
// walk though the input string
for (inputPtr = 0; inputPtr < strlen(inputString); inputPtr++, outputPtr++)
  // search for the ASCII backspace character that's part of the spinner
  if (inputString[inputPtr] == 8)
   // if the ASCII backspace is found,
   inputPtr++;  // increment the inputString pointer to skip the backspace
   outputPtr--; // decrement the outputString pointer to overwrite
       // the spinner character that preceded the backspace
  outputString[outputPtr] = inputString[inputPtr];
outputString[outputPtr] = '\0';
return 0;
You'll also find an attached CVI program which uses it on your sample string.
Attachments:
FilterSpinner1.zip ‏5 KB

Storing a Non Printable -from keyboard- Character in Varchar2 Column

Hi,
I want to store a non-printable character in a varchar2 column. This character should be non-printable -from keyboard- for all character sets -or very difficult to print from keyboard-. It doesn't matter, whether it can be displayed on screen or not. It does matter INSTR function returns the character position of that character. It should be able to import export data without any problem for any NLS specific operating environment. For example, I plan to use chr(1) do you think it's appropriate? I appreciate your helps.
Best Regards,
Salim

What is the business requirement you're trying to satisfy?
If your database character set is based on ASCII, CHR(1) (the Start of Header) character is likely to be transferred between systems without character set conversion. Non-ASCII character sets (i.e. Big5 for Chinese data) don't necessarily share the same control characters, though, and generally won't have the same binary representation of an ASCII control character (so CHR(1) in a non-ASCII based database wouldn't necessarily return the same character that CHR(1) would in an ASCII based database).
Justin

Character Encoding doubt

Hi Friends,
I need to do this part in my programs
"The string should take a parameter i.e upto 20 bytes long.And it must be encoded as character sequence using the "US-ASCII" standard character encoding.The unused bytes must be filled with space character."I tried doing this:
String parameter = "Hello";
byte[] beta = new byte[20];
Char[] ch = parameter.toCharArray();
beta = parameter.getBytes();Is this the write way,and do i need to set the encoding to "US-ASCII" .if yes,how to do that??Any help would be appreciated.
Thanks

Thanks sabre,
I got one small doubt more..would appreciate if anybody would help..
So,I created a class to send the data,but i have some problems receiving the data back from the server.This is my class:
import java.net.*;
import java.io.*;
public class SocketCat {
public static void main(String[] args) {
                                          String parameter = "Tester                              ";
          byte[] buf = new byte[40];
          try{
          buf = parameter.getBytes("ASCII");
          }catch(Exception e){
          e.printStackTrace();
     try{
            // get a datagram socket
        DatagramSocket socket = new DatagramSocket();
            // send request
        InetAddress address = InetAddress.getByName("localhost");
        DatagramPacket packet = new DatagramPacket(buf, buf.length, address, 3590);
        socket.send(packet);
         byte[] buffer = new byte[2000];
        // get response
        packet = new DatagramPacket(buffer, buffer.length);
        socket.receive(packet);
        // display response
        String received = new String(packet.getData(),"ASCII");
        System.out.println("Data Recd: " + received);
             socket.close();
        }catch(Exception e){
          e.printStackTrace();
}I would like to change this line:
byte[] buffer = new byte[2000];to be initialised to the same size as the size of incoming data...is there any way to do so???
And I am getting some strange characters I don't know why,am i doin anything wrong here??
thanks

Character Set Inquiry

I have a database which is installed with ASCII as character set and I can store chinese in it. I find that it is possible to install the dB with character set for BIG5 or GB for storing chinese. What's the difference?
Moreover, how oracle perform sorting for BIG5 and GB?

Exactly 1TB? Slightly under/slightly over?
Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
#1 Apply a Solaris label
If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
disk 1
disk 2
disk 3
disk 50Then feed that to format like this:
# format -f /tmp/disklist or whatever you've named the file.
#2 Apply the partition layout to all disks you want.
You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
# prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
Darren

Need help with converting characters to ASCII code

Hey. Im trying to write a program to make Caesar Ciphers by random numbers. This cipher must also wrap from front to end of ASCII code, so that if, for example, the character being ciphered is Z and its being modified by +3, the result ciphered character is not "]", but "c".
Im planning on reading the text that the user inputs (using ConsoleIO) into a string and then seperating each character into a character[]. Then, i would like to find the ASCII code of each character and print out the ASCII code character of the old ASCII code + the modifier.
So far, this is what i have (sorry for the length, i like to space things out so that its easier on the eyes and more organized... X-( ... ):
public class EvanFinalB {
     static ConsoleIO kbd = new ConsoleIO();
     static String enteredPhrase;
     static int phraseLength;
     public static void main(String[] args)
          System.out.println("Enter a phrase and this program will cipher it into a secret message.");
          System.out.println("/nEnter your phrase here:");
          //read phrase
          enteredPhrase = kbd.toString();
          //find length of entered text
          phraseLength = enteredPhrase.length();
          //declare arrays for the individual characters of the entered text and the ciphered characters
          char[] enteredChar = new char[phraseLength + 1];
          char[] cipheredChar = new char[phraseLength + 1];
          //loop converting of entered text into seperate characters
          for(int x = 1; x <= phraseLength; x++)
               enteredChar[x] = enteredPhrase.charAt(x);
               cipheredChar[x] = cipher(enteredChar[x]);//call cipher() method to find new ciphered character
     //wrap from front to end of ASCII code
     static char cipher(char enteredChar)
          //choose random number to cipher message by
          int modifier = (int)(Math.random() * 26) + 1;
          if(enteredChar + modifier > 90)//90 is the ASCII code for "Z" which is the last capital letter
               cipheredChar = (97 + (modifier - (90 - enteredChar)));//97 is the ASCII code for "a" which is the first lower case letter
          return cipheredChar[1];
}The program is obviously in its early stages but (i started creating it today actually), if there is a simple method or anything that i can use to find the ASCII value of a character in order to use enteredChar so that 'enteredChar' is equal to the ASCII code of the new ciphered character, please help me out...Thanks
P.S. If there's an easier way to go about creating a program for Caesar Ciphers, let me know.

The following code is from my Java textbook Big Java by Cay Horstmann. It is not my code and it's just to guide you in your own cipher.
import java.io.InputStream;
import java.io.OutputStream;
import java.io.IOException;
   This class encrypts files using the Caesar cipher.
   For decryption, use an encryptor whose key is the
   negative of the encryption key.
public class CaesarCipher
      Constructs a cipher object with a given key.
      @param aKey the encryption key
   public CaesarCipher(int aKey)
      key = aKey;
      Encrypts the contents of a stream.
      @param in the input stream
      @param out the output stream
   public void encryptStream(InputStream in, OutputStream out)
         throws IOException
      boolean done = false;
      while (!done)
         int next = in.read();
         if (next == -1) done = true;
         else
            byte b = (byte) next;
            byte c = encrypt(b);
            out.write(c);
      Encrypts a byte.
      @param b the byte to encrypt
      @return the encrypted byte
   public byte encrypt(byte b)
      return (byte) (b + key);
   private int key;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.IOException;
import java.io.OutputStream;
import java.util.Scanner;
   This program encrypts a file, using the Caesar cipher.
public class CaesarEncryptor
   public static void main(String[] args)
      Scanner in = new Scanner(System.in);
      try
         System.out.print("Input file: ");
         String inFile = in.next();
         System.out.print("Output file: ");
         String outFile = in.next();
         System.out.print("Encryption key: ");
         int key = in.nextInt();
         InputStream inStream = new FileInputStream(inFile);
         OutputStream outStream = new FileOutputStream(outFile);
         CaesarCipher cipher = new CaesarCipher(key);
         cipher.encryptStream(inStream, outStream);
         inStream.close();
         outStream.close();
      catch (IOException exception)
         System.out.println("Error processing file: " + exception);
}

Cast ascii to decimal

hi
im having a slight issue converting ascii to decimal.
i have an ascii string which is basically an incrementing number.
when i look at it as a hex string (by setting hex code in an indicator) i get:
0001
0002
0003
and so on.
however, when i convert this ascii string to decimal i get really large numbers.
when i get 0002 the decimal number is 131072.
this is equivalent to 20000 hex.
so it appears that i have 4 trailing hex zeros in there. not sure where they come from or how to get rid of them.
any ideas anyone?

slugger wrote:
im having a slight issue converting ascii to decimal.
Next time also try to be more specific.
The words "cast" and "convert" mean very different things, so don't use them interchangeably. (detals)
Your input is NOT ASCII (a character encoding scheme) but just a plain string.
The word "decimal" is a formatting specification, not a numeric data type.
Your problem also shows why type cast is relatively dangerous unless you know exactly what you are doing. There is no error output, e.g. if the string is shorter than needed for the datatype. It would be safer to use "unflatten from string" becaue it would alert you about the data mismatch at run time.
LabVIEW Champion . Do more with less code and in less time .

Change character set

Hi
is anyone can tell me how to change characterset.
i try with alter session but it doesnt work.
thanks

Article from Metalink
Doc ID:      Note:66320.1
Subject:      Changing the Database Character Set or the Database National Character Set
Type:      BULLETIN
Status:      PUBLISHED
     Content Type:      TEXT/PLAIN
Creation Date:      23-OCT-1998
Last Revision Date:      12-DEC-2003
PURPOSE ======= To explain how to change the database character set or national character set of an existing Oracle8(i) or Oracle9i database without having to recreate the database. 1. SCOPE & APPLICATION ====================== The method described here is documented in the Oracle 8.1.x and Oracle9i documentation. It is not documented but it can be used in version 8.0.x. It does not work in Oracle7. The database character set is the character set of CHAR, VARCHAR2, LONG, and CLOB data stored in the database columns, and of SQL and PL/SQL text stored in the Data Dictionary. The national character set is the character set of NCHAR, NVARCHAR2, and NCLOB data. In certain database configurations the CLOB and NCLOB data are stored in the fixed-width Unicode encoding UCS-2. If you are using CLOB or NCLOB please make sure you read section "4. HANDLING CLOB AND NCLOB COLUMNS" below in this document. Before changing the character set of a database make sure you understand how Oracle deals with character sets. Before proceeding please refer to [NOTE:158577.1] "NLS_LANG Explained (How Does Client-Server Character Conversion Work?)". See also [NOTE:225912.1] "Changing the Database Character Set - an Overview" for general discussion about various methods of migration to a different database character set. If you are migrating an Oracle Applications instance, read [NOTE:124721.1] "Migrating an Applications Installation to a New Character Set" for specific steps that have to be performed. If you are migrating from 8.x to 9.x please have a look at [NOTE:140014.1] "ALERT: Oracle8/8i to Oracle9i Using New "AL16UTF16"" and other referenced notes below. Before using the method described in this note it is essential to do a full backup of the database and to use the Character Set Scanner utility to check your data. See the section "2. USING THE CHARACTER SET SCANNER" below. Note that changing the database or the national character set as described in this document does not change the actual character codes, it only changes the character set declaration. If you want to convert the contents of the database (character codes) from one character set to another you must use the Oracle Export and Import utilities. This is needed, for example, if the source character set is not a binary subset of the target character set, i.e. if a character exists in the source and in the target character set but not with the same binary code. All binary subset-superset relationships between characters sets recognized by the Oracle Server are listed in [NOTE:119164.1] "Changing Database Character Set - Valid Superset Definitions". Note: The varying width character sets (like UTF8) are not supported as national character sets in Oracle8(i) (see [NOTE:62107.1]). Thus, changing the national character set from a fixed width character set to a varying width character set is not supported in Oracle8(i). NCHAR types in Oracle8 and Oracle8i were designed to support special Oracle specific fixed-width Asian character sets, that were introduced to provide higher performance processing of Asian character data. Examples of these character sets are : JA16EUCFIXED ,JA16SJISFIXED , ZHT32EUCFIXED. For a definition of varying width character sets see also section "4. HANDLING CLOB AND NCLOB COLUMNS" below. WARNING: Do not use any undocumented Oracle7 method to change the database character set of an Oracle8(i) or Oracle9i database. This will corrupt the database. 2. USING THE CHARACTER SET SCANNER ================================== Character data in the Oracle 8.1.6 and later database versions can be efficiently checked for possible character set migration problems with help of the Character Set Scanner utility. This utility is included in the Oracle Server 8.1.7 software distribution and the newest Character Set Scanner version can be downloaded from the Oracle Technology Network site, http://otn.oracle.com The Character Set Scanner on OTN is available for limited number of platforms only but it can be used with databases on other platforms in the client/server configuration -- as long as the database version matches the Character Set Scanner version and platforms are either both ASCII-based or both EBCDIC-based. It is recommended to use the newest Character Set Scanner version available from the OTN site. The Character Set Scanner is documented in the following manuals: - "Oracle8i Documentation Addendum, Release 3 (8.1.7)", Chapter 3 - "Oracle9i Globalization Support Guide, Release 1 (9.0.1)", Chapter 10 - "Oracle9i Database Globalization Support Guide, Release 2 (9.2)", Chapter 11 Note: The Character Set Scanner coming with Oracle 8.1.7 and Oracle 9.0.1 does not have a separate version number. It reports the database release number in its banner. This version of the Scanner does not check for illegal character codes in a database if the FROMCHAR and TOCHAR (or FROMNCHAR and TONCHAR) parameters have the same value (i.e. you simulate migration from a character set to itself). The Character Set Scanner 1.0, available on OTN, reports its version number as x.x.x.1.0, where x.x.x is the database version number. This version adds a few bug fixes and it supports FROMCHAR=TOCHAR provided it is not UTF8. The Character Set Scanner 1.1, available on OTN and with Release 2 (9.2) of the Oracle Server, reports its version number as v1.1 followed by the database version number. This version adds another bug fixes and the full support for FROMCHAR=TOCHAR. None of the above versions of the Scanner can correctly analyze CLOB or NCLOB values if the database or the national character set, respectively, is multibyte. The Scanner reports such values randomly as Convertible or Lossy. The version 1.2 of the Scanner will mark all such values as Changeless (as they are always stored in the Unicode UCS-2 encoding and thus they do not change when the database or national character set is changed from one multibyte to another). Character Set Scanner 2.0 will correctly check CLOBs and NCLOBs for possible data loss when migrating from a multibyte character set to its subset. To verify that your database contains only valid codes, specify the new database character set in the TOCHAR parameter and/or the new national character set in the TONCHAR parameter. Specify FULL=Y to scan the whole database. Set ARRAY and PROCESS parameters depending on your system's resources to speed up the scanning. FROMCHAR and FROMNCHAR will default to the original database and national character sets. The Character Set Scanner should report only Changless data in both the Data Dictionary and in application data. If any Convertible or Exceptional data are reported, the ALTER DATABASE [NATIONAL] CHARACTER SET statement must not be used without further investigation of the source and type of these data. In situations in which the ALTER DATABASE [NATIONAL] CHARACTER SET statement is used to repair an incorrect database character set declaration rather than to simply migrate to a new wider character set, you may be advised by Oracle Support Services analysts to execute the statement even if Exceptional data are reported. For more information see also [NOTE:225912.1] "Changing the Database Character Set - a short Overview". 3. CHANGING THE DATABASE OR THE NATIONAL CHARACTER SET ====================================================== Oracle8(i) introduces a new documented method of changing the database and national character sets. The method uses two SQL statements, which are described in the Oracle8i National Language Support Guide: ALTER DATABASE [<db_name>] CHARACTER SET <new_character_set> ALTER DATABASE [<db_name>] NATIONAL CHARACTER SET <new_NCHAR_character_set> The database name is optional. The character set name should be specified without quotes, for example: ALTER DATABASE CHARACTER SET WE8ISO8859P1 To change the database character set perform the following steps. Note that some of them have been erroneously omitted from the Oracle8i documentation: 1. Use the Character Set Scanner utility to verify that your database contains only valid character codes -- see "2. USING THE CHARACTER SET SCANNER" above. 2. If necessary, prepare CLOB columns for the character set change -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. Omitting this step can lead to corrupted CLOB/NCLOB values in the database. If SYS.METASTYLESHEET (STYLESHEET) is populated (9i and up only) then see [NOTE:213015.1] "SYS.METASTYLESHEET marked as having convertible data (ORA-12716 when trying to convert character set)" for the actions that need to be taken. 3. Make sure the parallel_server parameter in INIT.ORA is set to false or it is not set at all. 4. Execute the following commands in Server Manager (Oracle8) or sqlplus (Oracle9), connected as INTERNAL or "/ AS SYSDBA": SHUTDOWN IMMEDIATE; -- or NORMAL <do a full database backup> STARTUP MOUNT; ALTER SYSTEM ENABLE RESTRICTED SESSION; ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0; ALTER SYSTEM SET AQ_TM_PROCESSES=0; ALTER DATABASE OPEN; ALTER DATABASE CHARACTER SET <new_character_set>; SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP RESTRICT; 5. Restore the parallel_server parameter in INIT.ORA, if necessary. 6. Execute the following commands: SHUTDOWN IMMEDIATE; -- OR NORMAL STARTUP; The double restart is necessary in Oracle8(i) because of a SGA initialization bug, fixed in Oracle9i. 7. If necessary, restore CLOB columns -- see "4. HANDLING CLOB AND NCLOB COLUMNS" below. To change the national character set replace the ALTER DATABASE CHARACTER SET statement with ALTER DATABASE NATIONAL CHARACTER SET. You can issue both statements together if you wish. Error Conditions ---------------- A number of error conditions may be reported when trying to change the database or national character set. In Oracle8(i) the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: ORA-01679: database must be mounted EXCLUSIVE and not open to activate - if you do not enable restricted session - if you startup the instance in PARALLEL/SHARED mode - if you do not set the number of queue processes to 0 - if you do not set the number of AQ time manager processes to 0 - if anybody is logged in apart from you. This error message is misleading. The command requires the database to be open but only one session, the one executing the command, is allowed. For the above error conditions Oracle9i will report one of the errors: ORA-12719: operation requires database is in RESTRICTED mode ORA-12720: operation requires database is in EXCLUSIVE mode ORA-12721: operation cannot execute when other sessions are active Oracle9i can also report: ORA-12718: operation requires connection as SYS if you are not connect as SYS (INTERNAL, "/ AS SYSDBA"). If the specified new character set name is not recognized, Oracle will report one of the errors: ORA-24329: invalid character set identifier ORA-12714: invalid national character set specified ORA-12715: invalid character set specified The ALTER DATABASE [NATIONAL] CHARACTER SET command will only work if the old character set is considered a binary subset of the new character set. Oracle Server 8.0.3 to 8.1.5 recognizes US7ASCII as the binary subset of all ASCII-based character sets. It also treats each character set as a binary subset of itself. No other combinations are recognized. Newer Oracle Server versions recognize additional subset/superset combinations, which are listed in [NOTE:119164.1]. If the old character set is not recognized as a binary subset of the new character set, the ALTER DATABASE [NATIONAL] CHARACTER SET statement will return: - in Oracle 8.1.5 and above: ORA-12712: new character set must be a superset of old character set - in Oracle 8.0.5 and 8.0.6: ORA-12710: new character set must be a superset of old character set - in Oracle 8.0.3 and 8.0.4: ORA-24329: invalid character set identifier You will also get these errors if you try to change the characterset of a US7ASCII database that was started without a (correct) ORA_NLSxx parameter. See [NOTE:77442.1] It may be necessary to switch off the superset check to allow changes between formally incompatible character sets to solve certain character set problems or to speed up migration of huge databases. Oracle Support Services may pass the necessary information to customers after verifying the safety of the change for the customers' environments. If in Oracle9i an ALTER DATABASE NATIONAL CHARACTER SET is issued and there are N-type colums who contain data then this error is returned: ORA-12717:Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists The error only speaks about Nclob but Nchar and Nvarchar2 are also checked see [NOTE:2310895.9] for bug [BUG:2310895] 4. HANDLING CLOB AND NCLOB COLUMNS ================================== Background ---------- In a fixed width character set codes of all characters have the same number of bytes. Fixed width character sets are: all single-byte character sets and those multibyte character sets which have names ending with 'FIXED'. In Oracle9i the character set AL16UTF16 is also fixed width. In a varying width character set codes of different characters may have different number of bytes. All multibyte character sets except those with names ending with FIXED (and except Oracle9i AL16UTF16 character set) are varying width. Single-byte character sets are character sets with names of the form xxx7yyyyyy and xxx8yyyyyy. Each character code of a single-byte character set occupies exactly one byte. Multibyte character sets are all other character sets (including UTF8). Some -- usually most -- character codes of a multibyte character set occupy more than one byte. CLOB values in a database whose database character set is fixed width are stored in this character set. CLOB values in an Oracle 8.0.x database whose database character set is varying width are not allowed. They have to be NULL. CLOB values in an Oracle >= 8.1.5 database whose database character set is varying width are stored in the fixed width Unicode UCS-2 encoding. The same holds for NCLOB values and the national character set. The UCS-2 storage format of character LOB values, as implemented in Oracle8i, ensures that calculation of character positions in LOB values is fast. Finding the byte offset of a character stored in a varying width character set would require reading the whole LOB value up to this character (possibly 4GB). In the fixed width character sets the byte offsets are simply character offsets multiplied by the number of bytes in a character code. In UCS-2 byte offsets are simply twice the character offsets. As the Unicode character set contains all characters defined in any other Oracle character set, there is no data loss when a CLOB/NCLOB value is converted to UCS-2 from the character set in which it was provided by a client program (usually the NLS_LANG character set). CLOB Values and the Database Character Set Change ------------------------------------------------- In Oracle 8.0.x CLOB values are invalid in varying width character sets. Thus you must delete all CLOB column values before changing the database character set to a varying width character set. In Oracle 8.1.5 and later CLOB values are valid in varying width character sets but they are converted to Unicode UCS-2 before being stored. But UCS-2 encoding is not a binary superset of any other Oracle character set. Even codes of the basic ASCII characters are different, e.g. single-byte code for "A"=0x41 becomes two-byte code 0x0041. This implies that even if the new varying width character set is a binary superset of the old fixed width character set and thus VARCHAR2/LONG character codes remain valid, the fixed width character codes in CLOB values will not longer be valid in UCS-2. As mentioned above, the ALTER DATABASE [NATIONAL] CHARACTER SET statement does not change character codes. Thus, before changing a fixed width database character set to a varying width character set (like UTF8) in Oracle 8.1.5 or later, you first have to export all tables containing non-NULL CLOB columns, then truncate these tables, then change the database character set and, finally, import the tables back to the database. The import step will perform the required conversion. If you omit the steps above, the character set change will succeed in Oracle8(i) (Oracle9i disallows the change in such situation) and the CLOBs may appear to be correctly legible but as their encoding is incorrect, they will cause problems in further operations. For example, CREATE TABLE AS SELECT will not correctly copy such CLOB columns. Also, after installation of the 8.1.7.3 server patchset the CLOB columns will not longer be legible. LONG columns are always stored in the database character set and thus they behave like CHAR/VARCHAR2 in respect to the character set change. BLOBs and BFILEs are binary raw datatypes and their processing does not depend on any Oracle character set setting. NCLOB Values and the National Character Set Change -------------------------------------------------- The above discussion about changing the database character set and exporting and importing CLOB values is theoretically applicable to the change of the national character set and to NCLOB values. But as varying width character sets are not supported as national character sets in Oracle8(i), changing the national character set from a fixed width character set to a varying width character set is not supported at all. Preparing CLOB Columns for the Character Set Change --------------------------------------------------- Take a backup of the database. If using Advanced Replication or deferred transactions functionality, make sure that there are no outstanding deferred transactions with CLOB parameters, i.e. DEFLOB view must have no rows with non-NULL CLOB_COL column; to make sure that replication environment remains consistent use only recommended methods of purging deferred transaction queue, preferably quiescing the replication environment. Then: - If changing the database character set from a fixed width character set to a varying with character set in Oracle 8.0.x, set all CLOB column values to NULL -- you are not allowed to use CLOB columns after the character set change. - If changing the database character set from a fixed width character set to a varying width character set in Oracle 8.1.5 or later, perform table-level export of all tables containing CLOB columns, including SYSTEM's tables. Set NLS_LANG to the old database character set for the Export utility. Then truncate these tables. Restoring CLOB Columns after the Character Set Change ----------------------------------------------------- In Oracle 8.1.5 or later, after changing the character set as described above (steps 3. to 6.), restore CLOB columns exported in step 2. by importing them back into the database. Set NLS_LANG to the old database character set for the Import utility to avoid IMP-16 errors and data loss. RELATED DOCUMENTS: ================== [NOTE:13856.1] V7: Changing the Database Character Set -- This note has limited distribution, please contact Oracle Support [NOTE:62107.1] The National Character Set in Oracle8 [NOTE:119164.1] Changing Database Character set - Valid Superset definitions [NOTE:118242.1] ALERT: Changing the Database or National Character Set Can Corrupt LOB Values <Note.158577.1> NLS_LANG Explained (How Does Client-Server Character Conversion Work?) [NOTE:140014.1] ALERT: Oracle8/8i to Oracle9i using New "AL16UTF16" [NOTE:159657.1] Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9i (incl. 9.2) [NOTE:124721.1] Migrating an Applications Installation to a New Character Set Oracle8i National Language Support Guide Oracle8i Release 3 (8.1.7) Readme - Section 18.12 "Restricted ALTER DATABASE CHARACTER SET Command Support (CLOB and NCLOB)" Oracle8i Documentation Addendum, Release 3 (8.1.7) - Chapter 3 "New Character Set Scanner Utility" Oracle8i Application Developer's Guide - Large Objects (LOBs), Release 2 - Chapter 2 "Basic Components" Oracle8 Application Developer's Guide, Release 8.0 - Chapter 6 "Large Objects (LOBs)", Section "Introduction to LOBs" Oracle9i Globalization Guide, Release 1 (9.0.1) Oracle9i Database Globalization Guide, Release 2 (9.2) For further NLS / Globalization information you may start here: [NOTE:150091.1] Globalization Technology (NLS) Library index .
     Copyright (c) 1995,2000 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
Joel P�rez

ASCII to character

Similar Messages

Maybe you are looking for