Shulou(Shulou.com)05/31 Report--

Editor to share with you how to import imp garbled code, I believe that most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to understand it!

During imp import, it is found that the character sets of the two databases are the same, but after imp import, the comments are garbled:

SQL > select userenv ('language') from dual

USERENV ('LANGUAGE')

AMERICAN_AMERICA.ZHS16GBK

The error is as follows:

Import: Release 10.2.0.4.0-Production on Fri Dec 29 09:40:26 2017

Copyright (c) 1982, 2007, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Export file created by EXPORT:V10.02.01 via conventional path

Import done in US7ASCII character set and AL16UTF16 NCHAR character set

Import server uses ZHS16GBK character set (possible charset conversion)

Export client uses ZHS16GBK character set (possible charset conversion)

IMP-00017: following statement failed with ORACLE error 1917:

Check and find that the encoding of the client is different, so configure it in .bash _ profile

Client configuration on imp:

Export NLS_LANG=AMERICAN_AMERICA.ZHS16GBK

Problem solved.

The above is all the contents of this article "how to import garbled codes into imp". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.