• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
We recently transferred a copy of our production u_tree to new development and staging installations, and discovered that some of our updated tables did not seem to be taking effect. While tracing the logs and searching the KB, we determined that the production files had datestamps earlier than default configs that had been copied to /tmp/utf_files. Running util/x/7 seems to have resolved the problem.

We're trying to decide if we should schedule a brief period of production down-time to run this process on our main aleph server, just in case the upgrade process from Nov 2009 through Jan 2010 might have a similar problem.

Do you recommend our doing so, or should the upgrade express scripts for 18->19 and 19->20 have touched the date stamps of all u_tree configuration files?

Resolution:
Upgrade Express does not touch the u-tree configuration file timestamps.

util x/7 is a Post-Upgrade-Express step. In the upgrade_util menu:

8. Perform Post Upgrade Express Actions

1. Remove UTF files (util-x-7)

You need to do this. It just takes a few seconds.

• Article last edited: 9/18/2014