So I'm trying to load data from a csv file into a db. The documentation for the db says that the db expects all files being loaded is in the Unicode UTF-8 format. I checked my file format and I got that it's "ASCII text with very long lines with CRLF line terminators". The db says it's fine with ASCII text since it's UTF-8 compatible. But for some reason I'm having issues. So I'm wondering if it's b/c of the "with very long lines with CRLF line terminators" or if it's something totally different. If it does have to do with CRLF line terminators, how can I fix this in Linux?

maybe ? what db system is this (mysql ?). what issues are you having (what are the error messages).

did you create the file in windows or something. is it possible to create the file on linux to avoid the possibility of crlf's . theres a program dos2unix which sometimes helps with this kind of thing.

HP Vertica is the db system and it's telling me that the file cannot be found but I'm in the correct directory and checked my spelling multiple times so I'm confused. It did give me a hint saying if using the ON ANY NODE option I needed to put the data file in same location on each node (although I'm not specifying this option, I did try putting the data file in the same location on each node of my cluster). So right now I'm kind of at a dead end and am hoping someone may be able to help me troubleshoot this issue.

I downloaded the file I wanted to load online (it's like over 1000 rows so I wouldn't want to create it from scratch in Linux). Oh and this file was originally an Excel file (I just converted it to .csv). I'll look into the dos2unix program and see if that'll help.

Thanks

Exactly how are you directing the database to load the file?

One system I'm familiar with, you give the database system the file to load... But you can't give it a relative name - it must be the complete path or the database will not be able to find it. That is because the database engine doesn't have the same context as the user interface.

1 members found this post helpful.

@jpollard - Thanks! Using the complete path worked - I feel dumb for not trying that before.

for future reference you should copy-paste the command you use as well as any error that is reported so that people can identify things that are obvious.