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

Description:
Can you advise on the relevance of the following files and directories and whether we can delete any of them?

/exlibris/aleph/u17_2/ext01/
/exlibris/aleph/u17_2/ext02/
/exlibris/aleph/u17_1/pwd00/bor_pics
/exlibris/aleph/u17_1/pwd00/bor_pics.old
/exlibris/aleph/u17_2/pwd00/bor_pics
/exlibris/aleph/u17_2/pwd00/bor_pics.old

The /files/ directory exists in several libraries and folders. Can you advise on its relevance?
/exlibris/aleph/u17_1/…../files/
/exlibris/aleph/u17_2/…../files/

Resolution:
The ext01 and ext02 libraries are used by the system. But normally they are in the a-tree. Do "dlib ext01", then "dr", then "pwd". since it shows "./a17_1" and since aleph_start shows:

setenv ext01_dev ${ALEPH_MOUNT}/a ...

the u-tree ext01 and ext02 are extraneous and can be deleted.

The /bor_pics directory needs to exist in your $usr_library. Your $usr_library is sta50.

pwd00 is your $pw_library (password library). It does not need to have the /bor_pics (or bor_pics.old) directory.

The /files directory ($data_files) is where the Aleph backup utilities (p_file_03, util a/19, etc.) place their output files and where the restore utililties look for their input.

Some batch jobs write sequential work files to the /files directory prior loading them into Oracle.

The /files directory contains certain files (que_batch_lock, que_batch_status, que_batch, lib_batch_log, batch_log) which should be preserved .
Other, outdated .seq backup, transfer, or indexing work files can be deleted.

See KB's 3975 and 3976 for a general discussion of clean-up issues.

• Article last edited: 10/8/2013