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

Description:
We rebooted our test installation in order to rectify issues we were having with the reassignment of the name libcat2.abc.edu for our server to libcat.abc.edu. This made the test web opac available, but in the process our Oracle server became inactive, thus shutting down both our test and production environments. I am unable to restart the oracle server (via util o/1/1). I'm getting:

To continue you will need to enter ALEPH_DBA username/password.
username/password:ALEPH_DBA/ALEPH_DBA
...
idle> ERROR: ORA-01031: insufficient privileges

I ran aleph_shutdown, but could not run aleph_startup without a running Oracle server.

Resolution:
If the password for ALEPH_DBA has been changed to something other than "ALEPH_DBA", you need to use that changed password.

If you find that the permissions for ALEPH_DBA have somehow changed and you want to restore them to the original, see KB 16384-27217.

In this case, as in the case of KB 8192-9832, we found that, though the change of libcat2 to libcat had been made in aleph_start (aleph_db), it had not been made in $ORACLE_HOME/network/admin/tnsnames.ora and listener.ora files.

We changed all the occurrences of "libcat2" in this file to "libcat".

Also: the permissions on the two /exlibris1/aleph/ora_aleph/ files were changed to "-rw-rw-rw-".

Also: we needed to make the corrections described in KB 16384-21873.

After making these changes, an attempt to restart Oracle (with util o/1/1) was still getting the "insufficient privileges", but when the server was rebooted, Oracle started OK.