Can we use assumetargetdef along with sourcedef

Question

Can we use assumetargetdef along with sourcedef

Answer 1

FISH2 wrote:
Yes you can, if you have the below costraints.
{SOURCEDEFS <full_pathname>} | ASSUMETARGETDEFS
Use SOURCEDEFSif the source and target  tables have different definitions. Specify the source data-definitions file generated by DEFGEN.
Use ASSUMETARGETDEFS, if the source and target tables have the same definitions.
For Oracle databases that use multi-byte character sets, you must use SOURCEDEFS(with a DEFGEN-generated definitions file) if the source semantics setting is in bytes and the target is in characters. This is required even when the source and target data definitions are identical.
In other words, after taking into consideration the constraints noted in the documentation, the answer is "No, you can't."
Can we use assumetargetdef along with sourcedef
You should state what it is, exactly that you are trying to achieve.  "Source definitions" are for the trail being read. There is only one "definition" for the trail. ("Definition" in this sense, means the DDL that was used to generate the tables on the source database.)  The data captured from the source database is "applied" via SQL to the "target" database. The data is "mapped" from the source schema to the target schema. If you don't know what the source schema was, you can assume the target & source schemas are the same, and use the "AssumeTargetDefs" parameter.  However, if the source & target table definitions are different, then you'd use "SourceDefs {definitions file}" together with a database connection to the target database for the "target definitions".  (There are specific instances where you can have a "sourcedefs {file}" together in the same parameter file with a "targetdefs {file}", but that doesn't usually apply. It allows doing mapping upstream, before accessing the target database, to create a trail with a different definition (schema) than the original source database.)