Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Avoid pitfalls when working with an update set

Log in to subscribe to topics and get notified when content changes.

Avoid pitfalls when working with an update set

Because update sets make changes to an instance, review the following best practice information to avoid errors and performance issues.

  • Do not delete update sets. If an update set is deleted, any updated records may be overwritten in the next update.
  • Do not include the system_id field from the ldap_server_config record in an update set. An update set from a working configuration points to the wrong system_id node for the target instance and does not work.
  • Do not back out the Default update set. This action causes damage to the system.
  • Never change the update set field value (update_set) in a Customer Update record (sys_update_xml). If a customization is made in the wrong update set, take the following action:
    1. Switch to the desired update set.
    2. Modify the object (record) that was originally changed. You can make a trivial change, such as adding a field.
    3. Save the record.
    4. Back out the change just performed, and then save the record again.

      This action ensures that the latest version of the object is included in the desired update set and prevents duplicate updates for the same object in a single update set.

  • Do not mark an update set as Complete until it is ready to migrate. Once an update set is complete, do not change it back to In progress. Instead, create another update set for the rest of the changes, and make sure to commit them together in the order that they were created. Naming conventions may help in this case (for example, Performance Enhancements and Performance Enhancements 2).
  • Do not manually merge updates into an update set. Always use the Merge update sets module. This tool compares duplicate files between update sets and selects the newest version.
  • If a committed update set has a problem in the test instance, build the fix in another update set in the development instance. Commit this set to the test instance, and then make sure both sets are migrated to the production instance and committed in the order they were made.
  • Always preview an update set before committing it.
  • Set completed update sets on the production instance to ignore. This state ensures the update set is not reapplied when cloning the instance.
  • Keep a to-do list of manual changes and data loads that need to be completed after an update set is applied.
  • Do not make too many changes at one time. Verify that the correct changes have been made incrementally.