Thanks for your response.
the NULL values from Oracle were indeed replaced by \N in the data output. How do I go about loading this file? I hope I do not have to temporary replace \N with a string in the flat file and then later update in Postgres.Thanks.
103 48299 \N G 3 45
...
...
On Fri, Mar 16, 2018 at 2:06 PM, Pavel Stehule <pavel.stehule@xxxxxxxxx> wrote:
2018-03-16 18:12 GMT+01:00 Charlin Barak <charlinbarak@xxxxxxxxx>:Hi,I'm using ora2pg to migrate our Oracle database to Postgres. I was able to generate the data file using TYPE=COPY but when I attempted to load the file via psql, I got lots of "invalid command \N" errors. The resolution on the internet was not clear and was not ora2pg related. How do I resolve this issue? Can someone provide some guidance?\N is symbol for NULL. but \cmd are psql commands too. This behave means so psql lost synchronization and try to eval data like commands. psql import is tolerant - that means so source of this issue is lost usually. Try to import data with option ON_ERROR_STOP
https://stackoverflow.com/questions/4480381/postgres- sql-fail-on-script-error RegardsPavelThanks.
