Generating the Version Mismatch Report
Before initiating the import activity, it's recommended to check for any version mismatches between the source system and the target system. To generate the version mismatch report, use the -p or --mismatchReport parameter in the import command:
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u <username> -c "<context>" -l "<directory>" -p
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u demo -c "/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=Drive System" -l "D:\importedFiles\packageDeliveries\20131202" -p
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u demo -c "/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=Drive System" -l "D:\importedFiles\packageDeliveries\20131202" -p
The report is generated for received deliveries that have version mismatch data, regardless of whether version throttling is enabled or disabled. You can find the report in the Attachments tab of the received delivery.
To import and overwrite data marked with the Locked for Replication lock without version throttling, use the command line utility and specify the -o or --overwrite parameter. For example:
windchill com.ptc.windchill.rd.cli.WindchillPackage import -u demo -c "/wt.inf.container.OrgContainer=Demo Organization/wt.pdmlink.PDMLinkProduct=Drive System" -l "D:\importedFiles\packageDeliveries\20131202" -o
After successfully importing the received delivery, the replication lock changes to the product design lock, named Locked by Product Design Package. If an object still shows the replication lock, it was not imported due to issues such as version mismatch, object inaccessibility, or non-overridable conflict. Access the version mismatch report and import log in the Attachments tab of the received delivery to identify and resolve such issues, then retry the import.
The import log file shows the value YES for LOCAL_OBJECTS_OVERWRITE_MODE if the replication lock was applied. However, when importing an incremental package, the log file for the received delivery shows the value NO.
If a received delivery is imported partially (status Unsuccessful: Partial Import), and you try to import the same uploaded received delivery again, the import log for the earlier import is retained as is. A new import log is generated for the latest import.
 |
• Only base packages can be successfully imported when using the replication lock with or without version throttling. Incremental packages are not supported for import through the replication lock process.
• For change management objects:
◦ When importing a replication package, for a change notice being overwritten, all associated local change tasks are removed and recreated based on the source package.
◦ Effectivity is collected only if the effectivity context is marked for replication or is already replicated. Date effectivity is collected even if the effectivity context is not assigned.
◦ The entire change network is collected when applying the replication lock.
|
If a base package is successfully imported, any change on the source system can be directly replicated on the target system through an incremental package.
The version mismatch report generated for the received delivery, regardless of the version throttling condition, lists the versions available in the target but not in the source system.
For example, version A.2 is not available in the source system.
If you do not have access to an object in the target system that is available in the source system, the message You do not have access to the object is displayed. The iteration identity and context information are replaced with Secured Information.
The version mismatch report without version throttling is generated only when you use the -o or --overwrite command when importing a received delivery.
The received delivery shows the import status as In progress while the report is being generated, and Ready after it is generated. The report is overwritten with every import against the same received delivery.
| | The version mismatch report is removed if you perform the import action again without the -o or --overwrite. |
Some objects not displayed in the version mismatch report may be skipped from import due to business rules or to maintain data integrity. For example, in the case of a family table, even if only one instance is listed in the version mismatch report, none of the instances are imported. Such objects are listed in the Method Server Log.