Page 2 of 3

Re: Copy Rejected Data

Posted: Thu Jun 26, 2014 4:07 pm
by ClevelandSteve
But I need to specify a directory when copying many files using ON ANY NODE. I'm not sure what you are getting at. In an attempt to give Vertica what it wants I have tried specifying a file just to see what happens. When I specify a file it gave me the opposite error, "is not a directory". I'm stuck in a damned if you do, damned if you don't scenario.

Re: Copy Rejected Data

Posted: Thu Jun 26, 2014 7:06 pm
by JimKnicely
Is that "/myDirectory/" directory a shared directory between the nodes? Or a local directory on each node?

Re: Copy Rejected Data

Posted: Thu Jun 26, 2014 7:40 pm
by ClevelandSteve
Yes, it is a shared directory using a common mount point on each node. I do it that way so that I don't need to ssh to each node looking for the reject files. Each of the data files being used by the Copy statement have a unique name to prevent two nodes trying to write the same reject file.

Re: Copy Rejected Data

Posted: Tue Sep 23, 2014 3:16 pm
by ClevelandSteve
I'm still having this problem, and now it happening on a big important load. Has anyone else encountered this since I started the thread?

Re: Copy Rejected Data

Posted: Tue Sep 23, 2014 3:38 pm
by JimKnicely
Since you are using a shared directory maybe you need to have unique file names for each node?

Example:

Copy myTable From '/myDirectory/*' On Any Node
Rejected Data '/rejects_directory/node1.rej' On node_1, '/rejects_directory/node2.rej' on node_2
Exceptions '/exceptions_directory/node1.exp' On node_1, '/exceptions_directory/node2.exp' on node_2

Re: Copy Rejected Data

Posted: Tue Sep 23, 2014 3:39 pm
by NorbertKrupa
You may want to start a conversation on the Vertica Community.

Re: Copy Rejected Data

Posted: Tue Sep 23, 2014 4:23 pm
by scutter
I didn’t see any information in this thread on the version being used - or maybe I missed it. If you’re using 7.0 or later you can use REJECTED DATA AS TABLE and avoid this issue. But I imagine you would have tried that already so you must be on 6.1.3? :-)