No, it is not a good approach, there are a lot of problems, e.g.
- Doing a data import after the indexes are created will slow down the import considerable.
- the import will fire all insert triggers. That may slow down the import, too, and it may have unwanted side effects
- The current values of the sequences do not match to data.
You should use the QUERY parameter. So if you want to exclude the LOG and MESSAGE table of the APP schema add
to the parameter file of your export.
Another way to accomplish this task is to split this into two export. This is a little bit more complex but avoids reading table data.
- export the schema and exclude the large tables. his task is independent from the size of the two large tables
- export the structure of the two large tables. The fime for this task is also independent of the size of the two tables
first export (schema export with data)
EXCLUDE=TABLE:"in ('LOG', 'MESSAGES')
CONTENT=ALL # this is the default, so it must not be specified
second export (table exports without data)
At first you import the schema dump, then you import the table dump. For both imports you can use the