Closed sgrinko closed 1 year ago
Yes, message FATAL: you can not use global filters in ALLOW/EXCLUDE directive with SHOW_* reports
means that you can not use global object name inclusion/exclusion. You need to specify the type of the object, for example to exclude some tables and views:
EXCLUDE TABLE[MYTABLE1 MYTABLE2];VIEW[MYVIEW1 MYVIEW2]
A global declaration mean such definition:
EXCLUDE MYTABLE1 MYTABLE2 MYVIEW1 MYVIEW2
this kind of declaration is not supported because it will with be applied to all kind of export type.
Thank you!
Remade on:
EXCLUDE TABLE[SYS_FBA_.* BIN.*]
Now it works without errors. Reports are created.
Hi,
I test HEAD
On May, the following changes were made: https://github.com/darold/ora2pg/blob/269d550180b3bd5e36b45be55b884f4486082251/lib/Ora2Pg.pm#L1231
I.e. Table visibility restrictions cannot be used to issue the'SHOW'command. However, after executing the project initialization command:
ora2pg --project_base $HOME_DIR/ --init_project $SCHEMA -c /etc/ora2pg/ora2pg.conf
a file is created to export 'export_schema.sh', which contains the following code:We see here the use of the same configuration file for all commands
$namespace/config/ora2pg.conf
Since we use the
ALLOW\EXCLUDE
directives, this leads to errors in the logsand the absence of reports in the directory:
reports
within report files only 1 line:FATAL: you can not use global filters in ALLOW/EXCLUDE directive with SHOW_* reports
Configuration file 1 for all commands and the export script is generated automatically. We do not have the option to have a separate configuration file for
SHOW
commandsI propose to consider as an option: instead of interrupting work do
It's possible? Or maybe there's another workaround?