Oracle Database / Multitenant, Patching & Deployment
Handle Data Pump existing-table decisions deliberately
An import into a populated schema needs an explicit data policy. A table-exists message does not authorize truncating or replacing production content.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT owner, table_name, num_rows, last_analyzed FROM all_tables WHERE owner = 'APP_OWNER' AND table_name = 'APP_ORDERS';Read the result
The metadata establishes a visible existing table; NUM_ROWS is a statistics estimate, not a current reconciliation count.
Resolve and verify
Compare the import objective with existing data, constraints and dependencies. Choose the documented table-exists behavior in a reviewed import plan and validate results.
Operational precautions
Do not select REPLACE or TRUNCATE merely to suppress the warning. Both can destroy data or disrupt dependencies.