Announcement

Collapse
No announcement yet.

Migration Project bug to migrate Agents

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Migration Project bug to migrate Agents

    Hi,

    Migration Project is supporting inserts and updates to migrate database objects from the source to the target system. This is causing issues when a migration requires a deletion of database tables.

    Example:
    1. Agent in source system is created with 5 actions
    2. Agent is migrated from source to target system using Migration Project
    3. Agent is source system is changed by deleting 2 of the agent actions.
    4. Agent is migration from source to target system using Migration Project
    5. Agent in target system still has 5 actions

    Before we had Migration Project, and using an on-premise instance, it was good practice to delete all agent action rows with a SQL statement in the target system before loading the updated agent, but this can't be done in OTM Cloud because delete SQL statements can no longer be executed.

    The above also applies to Planning Parameter Sets and a number of other OTM objects.

    Has anyone been faced with this issue yet? What workarounds exist?

    Thanks,

    Lourens


  • #2
    Hi Lourens,

    You can try DB.XML Export/Import for agents.

    This also refreshes the cache automatically. It has both the options of IU and RC where RC does replace everything.

    The xml for objects inside migration project are in db.xml format only.

    Thanks
    Anurag Saini
    -------
    Thanks and Regards
    Anurag Saini
    MavenWire

    Comment


    • #3
      Hi Anurag,

      Are you suggesting to manually modify the Migration Project db-xml files to include RC logic for Agents, before uploading in the target environment? I wondered if there was a setting in OTM to make this happen automatically.

      Thanks,

      Lourens

      Comment

      Working...
      X