My Oracle Support Banner

Changing from US7ASCII or WE8ISO8859P1 or IW8ISO8859P8 to IW8MSWIN1255 in 8i, 9i, 10g and 11g. (Doc ID 1213683.1)

Last updated on DECEMBER 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 8.1.7 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Generic (Platform Independent)


NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material.  Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

To provide a guide to
*or change the NLS_CHARACTERSET from US7ASCII , WE8ISO8859P1or IW8ISO8859P8 to IW8MSWIN1255.
* or rescue Hebrew data stored in a WE8IOS8859P1 or US7ASCII database

We strongly advice to follow this note also when using export/import from an US7ASCII, WE8ISO8859P1 or IW8ISO8859P8 to a IW8MSWIN1255 database.


select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';

This note is ONLY for 8i, 9i, 10g and 11g it cannot be used for Oracle RDBMS 12c
For other characterset conversions and Oracle 12c please see <Note 225912.1> Changing the Database Character Set ( NLS_CHARACTERSET )


Any DBA wanting to change the current NLS_CHARACTERSET from IW8ISO8859P8 , WE8ISO8859P1 or US7ASCII to IW8MSWIN1255.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 1) Prerequisites
 US7ASCII versus IW8MSWIN1255
 WE8ISO8859P1 versus IW8MSWIN1255
 IW8ISO8859P8 versus IW8MSWIN1255
 2) Check the source database for:
 2.a) Invalid objects.
 2.b) Orphaned Datapump master tables (10g and up)
 2.c) Unneeded sample schema's/users.
 2.d) Objects in the recyclebin (10g an up)
 3) Check if there are no invalid code points in the database for the current NLS_CHARACTERSET:
 4) Csscan lists "Lossy" data in the scan performed in step 3.
 5) Final Csscan run when going to IW8MSWIN1255
 6) Performing the actual character set change:
 7) Make sure clients are using the correct NLS_LANG setting:
 8) Notes:

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.