- Article Type: General
- Product: Aleph
- Product Version: 20
The v20 Ex Libris Backup Package fails on our server....
idle> idle> Database closed.
ORACLE instance shut down.
idle> ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
ORA-03114: not connected to ORACLE
idle> ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
The generic Ex Libris Backup Package is not set up to accommodate a two-task environment, with a separate database server.
Although the hot backups have been working, cold backups should be done too.
Ex Libris staff have stated: "We don't provide a method to automate the Aleph Shutdown, in a TWO_TASK environment for Oracle Cold Backup."
One way to do it, without great checking, is to have crontab on the app server do Aleph shutdown and startup, like :
00:00 Aleph_shutdown on app server
00:15 oracle cold backup on db server
03:00 aleph startup on app server
However, as a non-OSP site, you need to create such crontab entries, and test them thoroughly. Ex Libris can not be responsible for these.
- Article last edited: 10/8/2013