Ora2Pg is a free tool used to migrate an Oracle database to a PostgreSQL compatible schema. It connects your Oracle database, scan it automatically and extracts its structure or data, it then generates SQL scripts that you can load into PostgreSQL.
Commit 5d0ad021b71f27d3ccf2f54e0909a00cf910f482 changes the output directory name used for the SEQUENCE_VALUES to remove the trailing double "s". So now the directory name is: ./schema/sequence_values .
However, when actually trying to export the sequence values, the directory name change is not reflected and consequently an error is generated:
Running: ora2pg -p -t SEQUENCE_VALUES -o sequence_values.sql -b ./schema/sequence_valuess -c ./config/ora2pg.conf
Aborting export...
FATAL: Can't open ./schema/sequence_valuess/sequence_values.sql: No such file or directory
Notice the use of the double trailing "s" when actually exporting.
Solution is to propagate the change from commit 5d0ad021b71f27d3ccf2f54e0909a00cf910f482 to the section of code that does the actual export.
Commit 5d0ad021b71f27d3ccf2f54e0909a00cf910f482 changes the output directory name used for the SEQUENCE_VALUES to remove the trailing double "s". So now the directory name is:
./schema/sequence_values
.However, when actually trying to export the sequence values, the directory name change is not reflected and consequently an error is generated:
Notice the use of the double trailing "s" when actually exporting.
Solution is to propagate the change from commit 5d0ad021b71f27d3ccf2f54e0909a00cf910f482 to the section of code that does the actual export.