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

Description:
Our Upgrade Express util_upgrade "Check Environment" function shows the following:

Checking abc01...
Checking abc10...
Checking abc11...
Checking abc50...
Checking abc60...
Checking pwd50...
Checking alephe...
Checking usm01...
Checking usm10...
Checking usm50...
Checking usm60...
Checking vir01...
No alephe prof_library file

Should there be a prof_library file under alephe?

Resolution:
When they do util_upgrade, "View/Update upgrade parameters" and select "1. View Current Parameters", it shows alephe in the "Libraries to be upgraded".

It should not. There are no Oracle tables for alephe, so nothing to import. As far as aleph/u-tree files the Install customer data does the alephe separately and automatically. They should do "Update parameters" and remove "alephe".

The "Checking usmnn..." lines indicate that they are trying to upgrade the USMnn libraries.

In generating the "View/Update upgrade parameters" / "View Current Parameters" display, the ./util/make_default_conf procedure does the following:

set libraries=`$uk_root/source/proc/non_demo_libs`

that is, it specifically excludes the (USMnn) demo libraries.

It's possible that this could be circumvented, but the USMnn demo libraries are *not* intended to be changed by the customer (except the conducting of temporary tests by them or by Ex Libris staff).

The customer needs to use the USMnn tables as we are distributing them. They should *not* be carrying over USMnn data from a previous version.

• Article last edited: 10/8/2013