The GMU failed to update a policy on target server, the error indicates an unique key error -- for policy, both ID and policy name need to be unique. Therefore the reason of conflict could be, same ID but different name (rare, maybe policy name was manually changed after last migrateIn), or different ID but same name (common, but the error message should be different, such as "(name) must be unique" ), or maybe the same policy is under different folder in source/target server (when migrateIn, you can specify --destFolder <destination folder> if you want to migrate to a different folder).
Check the /var/log/mysqld.log could give more details of the conflict.
Regards,
Mark
Original Message:
Sent: 07-10-2019 09:21 AM
From: Giridharan S
Subject: MigrateIn Conflict
Hi,
I am trying to migrateIn policy through GMU utility, but getting Invalid Resource Conflict.Attached screenshot for the reference.
PFB the commands which i have used to prepare the bundle file
GatewayMigrationUtility.bat migrateOut -h {host} -p 8443 -u {user} -x {encrypted password} --format singleFile --policyName /MyPru/Fragments/Policy/PF_OPS_Set_HTTP_Route_Parameters --dest {folder-path}\PF_OPS_Set_HTTP_Route_Parameters.xml --encryptionPassphrase {passphrase} --trustHostname --includeOnlyServicePolicy --defaultAction NewOrUpdate
Please suggest on this.
Thanks in Advance!
------------------------------
With Regards,
S Giridharan
------------------------------