What about Chinese garbled code when sqlldr imports data?
This article introduces the relevant knowledge of "how to do Chinese garbled when sqlldr imports data". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!
Previous ctl file definition
Click (here) to collapse or open
LOAD DATA
CHARACTERSET ZHS16GBK
INFILE 'wxls.csv'
APPEND
INTO TABLE temp_import20171201
FIELDS TERMINATED BY ","
TRAILING NULLCOLS
(TEL
RESELLER
PAPERS_NO
PRODUCT_NAME
TICKET_PRICE
CONSUME_TIME DATE "YYYY-MM-DD HH24:mi:ss"
ORDER_NO
)
Import data
Click (here) to collapse or open
Sqlldr userid=test/test control=import.ctl log=import.log bad=bad.log
The results show that all the Chinese characters are garbled.
Modify the ctl file
Click (here) to collapse or open
LOAD DATA
CHARACTERSET ZHS16GBK
INFILE 'wxls.csv'
APPEND
INTO TABLE temp_import20171201
FIELDS TERMINATED BY ","
TRAILING NULLCOLS
(TEL
RESELLER
PAPERS_NO
PRODUCT_NAME
TICKET_PRICE
CONSUME_TIME DATE "YYYY-MM-DD HH24:mi:ss"
ORDER_NO
)
Click (here) to collapse or open
Sql > delete from temp_import20171201
Query after import, the result is normal, do not edit the file under windows must be dos2uninx under linux
This is the end of the content of "what to do with Chinese garbled when sqlldr imports data". Thank you for your reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!
