Re: Import Error Code IMP-00069, Please help.
Date: Sun, 12 Jan 2003 14:23:12 +0100
Message-ID: <3E216C40.1050507_at_netscape.net>
esee wrote:
> Hi,are you from SSS ? > > Originally posted by Jian Cheng >
>>Hi,
>>
>>I'm working on my Capstone project within Win2000 and Linux
>>environment. I created an
>>Oracle dmp file in User mode using Oracle Export on Win2000 that has
>>Oracal 8.1.7
>>installed. Then I tried to import this dmp file to a Linux machine
>>that runs Oracle
>>8.1.6. Here is the output when I ran Import:
>>
>>Connected to: Oracle8i Enterprise Edition Release 8.1.6.1.0 -
>>Production With the
>>Partitioning option JServer Release 8.1.6.0.0 - Production
>>
>>Export file created by EXPORT:V08.01.07 via conventional path import
>>done in US7ASCII
>>character set and US7ASCII NCHAR character set IMP-00069: Could not
>>convert to
>>environment national character set's handle IMP-00000: Import
>>terminated
>>unsuccessfully
>>
>>I would appreciate your help to resolve this problem. Thank you in
>>advance.
>>
> > Florence > > -- > Posted via http://dbforums.com
Do:
export NLS_LANG=.US7ASCII
(mind the dot!) before you attempt to import, or use the complete
NLS_LANG, e.g. export NLS_LANG=American_America.US7ASCII.
Then prepare for the incompatibility between EXP 817 and IMP 816... Better upgrade your Linux to 817, too.
There is no way to get this working AFAIK, as the 6 and 7 versions use different column names in views, that otherwise remained the same. The only option, I can think of (apart from the obvious above) is:
(1) make an entry in you Linux tnsnames.ora, so you can connect from
Linux to Win2K.
(2) make a full, cold backup of your Win2K db
(3) on the Linux machine, run catexp as sys or internal against the
Win2K machine.
(4) Make an export on the 816/Linux machine of your Win2K database,
using exp system_at_Win2K.
This is crucial! You need to run the 816 version tool against your
Win2K/817 database.
(5) Import into Linux 816. If all goes well, proceed, if not post
with error messages
(6) Two options: the short one: run catexp as sys or internal on your
Win2K box against the 817/Win2K database, or:
restore your backup; no need for recovery.
Grtz, Frank Received on Sun Jan 12 2003 - 14:23:12 CET