You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the actual files on disk do not use the new names, and instead use the old partition names in the filename. Example:
ls -1 data/SAMPLE_TABLE*
SAMPLE_TABLE_data.sql
SAMPLE_TABLE_SYS_P72925_data.sql
SAMPLE_TABLE_SYS_P72926_data.sql
SAMPLE_TABLE_SYS_P72927_data.sql
SAMPLE_TABLE_SYS_P72929_data.sql
And consequently, when running import_all.sh the script will fail as it cannot find the properly named files on disk.
Even if exporting partitions with RENAME_PARTITION=0 and using the COPY option to export to disk (and not to write directly into the PostgreSQL target), the exported files have an incorrect file name as they include the table name while the data/data.sql references to those files do not.
Ora2Pg version:
$ ora2pg --version
Ora2Pg v24.3
The text was updated successfully, but these errors were encountered:
Exporting from Oracle to disk using the command:
Export includes a PARTITIONED table and consequently am including the Ora2Pg configuration parameter:
After exporting, the
data/data.sql
file uses the renamed partitions. Excerpt for example:But the actual files on disk do not use the new names, and instead use the old partition names in the filename. Example:
ls -1 data/SAMPLE_TABLE* SAMPLE_TABLE_data.sql SAMPLE_TABLE_SYS_P72925_data.sql SAMPLE_TABLE_SYS_P72926_data.sql SAMPLE_TABLE_SYS_P72927_data.sql SAMPLE_TABLE_SYS_P72929_data.sql
And consequently, when running
import_all.sh
the script will fail as it cannot find the properly named files on disk.Even if exporting partitions with
RENAME_PARTITION=0
and using the COPY option to export to disk (and not to write directly into the PostgreSQL target), the exported files have an incorrect file name as they include the table name while thedata/data.sql
references to those files do not.Ora2Pg version:
The text was updated successfully, but these errors were encountered: