For me, the release of the Universal Driver 5.0 for use with OpenInsight 9.4 was one of the best enhancements in recent times for people running OpenInsight. It had new features that were sought after by many VARs and end users, and now it just got better with the release of 18.104.22.168.
Now available from www.revelation.com, this new version replaces all previous versions of the Universal Driver 5 and it is available at no cost to anyone who has purchased the Universal Driver 5. Don’t feel left behind if you have an older version of the UD because we have an upgrade path for anyone running the UD and a new purchase option if this is your first time using the UD to enhance your deployed system.
So what’s all the excitement about?
The Universal Driver 22.214.171.124 resolves a potential memory leak /overrun issue when running in ‘debug output’ or logging mode.
It has also been enhanced to eliminate ‘hanging’ when shutting down the service. This should allow sites to terminate and restart the Universal Driver without requiring a server reboot.
The new version addresses an issue that recently came to light where the record count and alpha values in the file header can get corrupted when several incomplete latent select / readnext are followed by a complete latent_Select/readnext. This corruption has the side effect to cause the LK to expand rapidly. A later complete select/readnext can repair the header and cause the UD to resize the table to normal size. From the outside it looks like the service is bogging down for no reason. In extreme cases the resize can crash the service and leave a huge file on the server. It appears that this is a long-standing issue which may explain some of the issues witnessed by large sites.
The Volume Shadow Copy Service (VSS) feature now pauses the resizing thread and flushes all buffers. Before 126.96.36.199 there was the possibility of a file being resized during the snapshot and of some new header record counts / alpha values not being written to disk.
Revelation have implemented the ability to pause the resizing thread. The idea is to let the UD continue to queue files for resizing, pause the resize thread during the day so it does not slow the server, then release the thread in the evening to let the files catch up.
Revelation has also implemented a set-sizelock call inside the UD. Prior to 188.8.131.52 the fix_lh program must OSBWrite the new sizelock into the header, which is not compatible with using a sharename to isolate the rev files. The next UD Manager will support this feature. The goal is to provide fine-grained control of resizing. In theory you could pause the resizing thread, then view which files are going to resize, and control the order of the resizing by locking or releasing individual tables.
A “feature” where the UD will clear a sizelock of 1 has also been identified and removed in the new version. Revelation has always stated that you presize a file, set sizelock to 1 and load it with data. But, the UD clears the 1 on any select / readnext, making the feature less useful. They have therefore removed this feature from the UD so that it is easier to pre-size tables and to leave them set to expand only.
The Universal Driver 184.108.40.206 software can be downloaded HERE.