Just a quick note to explain today’s OPAC downtime.
We needed to apply a jumbo patch update to our Voyager system, fixing a number of bugs and (we hope) not introducing too many new ones. The patch got off to a slow start until a permissions problem was discovered then zoomed along until we hit what I knew was going to be a problem—separating off our Web OPAC server from the machine running Voyager and Oracle. The Voyager documentation assumes you’ll run everything on the same machine but for performance reasons, we use a separate server to handle the web traffic. Thanks to error logs, I finally figured out that several Oracle load libraries were missing and moved them over from the primary server.
Presto…OPAC returns.