IMP-00038: Could not&n…

Import: Release 11.2.0.1.0 - Production on Fri Dec 12 17:06:06 2014

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

IMP-00038: Could not convert to environment character set's handle
IMP-00000: Import terminated unsuccessfully

 

 

Import Fails With Error IMP-38 (文档 ID 1024237.6) 转到底部 

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

Applies to:
Oracle Database - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.
***Checked for relevance on 09-Sep-2014***

Symptoms
You are doing either a Table, User, or Full import and it fails with error IMP-38:

IMP-00038: Could not find environment character set handle
Cause
Dump file is corrupt or environment variables not properly set.

Solution
There are a few things to consider when approaching this issue:

1.If the export dump file was transferred from one location to another using FTP, make sure that it was sent using BINARY mode.

2.Check that that the dump file has not been edited in any way. This is not a supported activity.

3.Check the environment settings.

a. Make sure that environment variable LD_LIBRARY_PATH is pointing to the correct ORACLE_HOME for the version of the Export binary that is being used.
    LD_LIBRARY_PATH should be set to $ORACLE_HOME/lib.
    If this is not set correctly, the export executable will not be able to find the correct NLS files.

b. If using Oracle7.2.2, ensure that the environment variable ORA_NLS is set properly. It should be set to:
    $ORACLE_HOME/ocommon/nls/admin/data

c. Set environment variable NLS_LANG to the character set of the export dump file.
    The export may have been created from a database that is using a character set that is different from the one used for the target database.
    This is especially true if one database uses a 7-bit character set and the other uses an 8-bit character set.
Note:
The import character set should be a superset of the export character set, otherwise special characters will not be correctly converted.
References
NOTE:15095.1 - Old Exp/Imp (not datapump) and NLS Considerations
NOTE:225912.1 - Changing Or Choosing the Database Character Set ( NLS_CHARACTERSET )
NOTE:1012189.6 - Errors IMP-9 IMP-30 Or IMP-37 When Trying to Import (IMP) A Transferred Export Dump File
NOTE:1012613.6 - ORA_NLS AND ORACLE 7.2.2