Re: Full Ex/Im-port to New Instance, NT

From: Yassir Khogaly <yassir_at_khogaly.freeserve.co.uk>
Date: Mon, 12 Oct 1998 08:59:14 +0100
Message-ID: <6vsd7s$5m0$1@newsreader2.core.theplanet.net>

Document-ID:        <Note:15095.1>
Title:              EXPORT/IMPORT AND NLS CONSIDERATIONS
Author:
Circulation:        ** PUBLIC **
Department:
Document ID:                   106125.722
Title:                         EXPORT/IMPORT AND NLS CONSIDERATIONS
Creation Date:                 17 August 1996
Last Revison Date:             17 August 1998
Revision Number:               0
Product:                       NLS
Product Version:               GENERIC
Platform:                      GENERIC
Information Type:              ADVISORY
Impact:                        MEDIUM
Abstract:                      This document contains NLS considerations
                               when using export/import.
Keywords:                      NLS;NLS_LANG;EXPORT;IMPORT
------------------------------------------------------------------------
                   EXPORT/IMPORT AND NLS CONSIDERATIONS

If a user has exported/imported a database or table(s) and is now encountering
character set conversion problems, use the following information to confirm whether the export/import procedure was performed correctly:

--Export database using NLS_LANG to identify the source database's

      character set. Export stores the character set ID (not the text
      string) in the dump file.

--Establish NLS_LANG environment variable for Import session.
--Import reads the Export character set ID from the dump file and
      compares it with the session's character set as defined in NLS_LANG.
--No conversion occurs if the Export's character set and the Import's

      session character set are the same. If they are not the same,
      conversion is performed from the Export character set to the Import's
      session character set prior to the data being inserted into the
      database.

--The Import's session character set should be a superset of the
Export's

      character set otherwise special characters will not be correctly
      converted.

--Include the parameter 'CHARSET' when defining the Import parameter
set.

      CHARSET identifies the character set of the Export file. Currently
      in V7, the code expects the value in CHARSET to match the Export's
      file character set. If they do not match, IMP-42 will result.
      The CHARSET option was developed to import older export files
      which did not have stored character set ID information.


    --After the data has been converted to the Import's session character


      set, it is then converted to the database character set if they
      differ. The database character set should be a superset of the
      Import's session character set otherwise special characters will not
      be correctly converted.



    -------------------


    | db in character |     export            exp session is in character
    | set A           |---------------------> set B as defined by NLS_LANG.


    -------------------                       Therefore the dump file is in


         source                               character set B. Character set
                                              conversion may occur.

                                                        |
                                                        |
                                                        | move file over to
                                                        | another machine
                                                        |
                                                        V
         destination


    -------------------


    | db in character |     import            imp session is in character
    | set D           | <-------------------  set C as defined by NLS_LANG.


    -------------------                       The dump file is still in


                                              character set B. Character set
                                              conversion may occur.

    During the import process
    character set conversion
    may occur between character
    set C and the db's character
    set D if they differ.

The user needs to identify the following: --what is the database character set specified when issuing the   CREATE DATABASE for the source database (character set A in the above). --what is the client character set specified with NLS_LANG when the   data was inserted.
--what is the client character set when the data was exported (character   set B in the above).
--what is the database character set specified when issuing the CREATE   DATABASE for the destination database (character set D in the above). --what is the client character set when the data was imported.

It's important to note Import will do up to 2 character set conversions depending on:
(a) character set of export file, (b)NLS_LANG of import session and (c) character set of database.
Refer to bugs 220349,224161 and enhancement requests 181388,181389.

---

                                        Oracle Worldwide Customer Support

begin 666 Yassir Khogaly.vcf
M0D5'24XZ5D-!4D0-"E9%4E-)3TXZ,BXQ#0I..DMH;V=A;'D[66%S<VER#0I& M3CI987-S:7(@2VAO9V%L>0T*3U)'.D%%154-"E1)5$Q%.E-E;FEO<B!/<F%C M;&4_at_1$)!#0I414P[2$]-13M63TE#13HK-#0H,"DQ.#$@-#8P-# T,@T*5$5, M.T-%3$P[5D])0T4Z*S0T-#$Q.3 V-S<V#0I!1%([2$]-13M%3D-/1$E.1SU1 M54]4140M4%))3E1!0DQ%.CL[1FQA=" Y/3!$/3!!,3D_at_4V]U=&AL86YD)W,@ M1W)O=F4],$0],$$[0FEC:VQE>3M+96YT.T)2,2 R1$$[16YG;&%N9 T*3$%" M14P[2$]-13M%3D-/1$E.1SU154]4140M4%))3E1!0DQ%.D9L870@.3TP1#TP M03$Y(%-O=71H;&%N9"=S($=R;W9E/3!$/3!!/3!$/3!!0FEC:VQE>2P_at_2V5N M="!"4C$@,D1!/3!$/3!!16YG;&$]#0IN9 T*55),.FAT=' Z+R]W=W<N:VAO M9V%L>2YF<F5E<V5R=F4N8V\N=6L-"E523#IH='1P.B\O=W=W+F%E974N;W)G M+G5K#0I%34%)3#M04D5&.TE.5$523D54.GEA<W-I<D!K:&]G86QY+F9R965S M97)V92YC;RYU:PT*4D56.C$Y.3_at_Q,#$R5# W-3DQ-%H-"D5.1#I60T%21 T* `
end Received on Mon Oct 12 1998 - 02:59:14 CDT