It's correct.
When you use the option REPLACE in the IMPORT tool, the import will
truncate the table, so no log about the deletes will be created.
However the inserts are logged.
So DPROP will find only the inserts, because DPROP uses the DB2's log,
to know what records should be created or deleted.
After a load like that, you may use a COLD REFRESH on the target table,
so the target table will be in sync with the source.
"REPLACE
Deletes all existing data from the table by truncating the data
object, and inserts the imported data. The table definition and the
index definitions are not changed. This option can only be used if the
table exists. It is not valid for tables with DATALINK columns. If this
option is used when moving data between hierarchies, only the data for
an entire hierarchy, not individual subtables, can be replaced."
If you had used load, would be worst, because the LOAD only creates a
little log, so your new records wouldn't be there either...
JC escreveu:
I have a table which is replicated for after images only. I tried to
do an import using the replace option into the source table with data.
For some of the rows, they were not in the import file, so were
replaced in the master table as a result of the import. For the
replica database table, the "deleted" rows were not removed; they still
exist, along with all the new/updated records from the import. Is this
a restriction of DProp? Thanks.
