Unless I am really mistaken, sqlldr will import external data into an Oracle database. The Perl system command will just start sqlldr for you and then sqlldr takes over. The data doesn't pass through your perl-script at all.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply]
[d/l]
[select] |
yes.I agree on u.So the issue is strange.Though the text is gbk or utf8,I can configure the characterset zhs16gbk or al32utf8 in control file.
Oh,right,I have missed a important information.when I rename the title of my data text to test.txt,then no matter what the encoding of my data text,the issue will disappear!!!I can import it .So I think there is something unkonown in perl.
| [reply] |
What do you mean with "pre-treatment" of the data text? The perl part of your program does not do anything with the data-file.
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] |
thank u very much.Because I have check the code and discover the fault.And indeed there is no relationship between the bug and perl or sqlldr.
| [reply] |