Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Removing Aleph libraries (and sublibraries)

    • Article Type: Q&A
    • Product: Aleph
    • Product Version: 20

    Question

    Is there a document describing how to remove a library or sublibrary from Aleph?

    Answer

    Different procedures need to be used, depending on the type of library. The most common cases are those shown below:

    1. Removing a sublibrary

    As described in Articles 000019678 ("How to run p_item_11 item deletion for particular sublibraries") and 000014871 ("Question about removing a sublibrary from Aleph"), the item-11 (Item deletion) Service is key to this process.

    Article 000018149 ("Changing sublibrary codes") is also relevant.


    2. Removing an ADM library

    See Article 000024664 ("How to remove an ADM library").


    3. Removing the bib/adm/hol libraries for a particular institution

    [Note: This is a rather complicated procedure. The site may want to contract with Ex Libris Professional Services to do this.]

    This is the case where the ABC library moving off of the system has its own Bib (abc01), ADM (abc50), HOL (abc60), and Course Reserves (abc30) libraries, separate from the main (DEF) libraries: def01, def50, def60, and def30.

    a. Remove the ADM library (abc50), as described in Article ("How to remove an ADM library"). The ADM library's tables should be exported and deleted as part of this process. Since *all* of the abc01 and abc60 records will be deleted, steps 1 and 2 in that Article's Procedure may not be relevant, but step 3 {Consult Article 000024663 ("Preventing access by staff and patrons of ADM library being removed")}, having to do with deletion/preservation of shared patron records is definitely relevant.

    b. Export all of the other libraries' Oracle tables. If the library is being moved to a different Aleph installation, it may be that the Oracle Data Pump could be used. Otherwise, use the file-03 utility, which will create sequential files which can be input to a different system. There is no need to export the temporary or index tables, just the base tables. {See Article 000023573 ("Which tables are index, temporary, and base tables?") in this regard.}

    After all of the tables have been successfully exported, drop/delete the Oracle data for each library, using the SQL "drop user xxxnn" command <where "xxxnn" is the library>; this will drop all of this library's tables (besides dropping the user).

    c. Export all of the other ABC libraries' Aleph tables. Then delete the Aleph tables:

    1) delete the library from the u-tree:

    > dlib xxxnn
    > dr
    > cd ..
    > rm -fr xxxnn

    2) Delete the library(s) from the system-level tables in $alephe_root and $alephe_tab:

    $alephe_tab/job_list
    $alephe_tab/library_relation
    $alephe_tab/tab_library_group
    $alephe_tab/tab_base.lng
    $alephe_tab/tab_oclc
    $alephe_root/aleph_start.private
    $alephe_root/www_f_lng/base-list

    $alephe_tab/tab_sub_library.lng should have already been updated by the removal of the ADM library.

    grep on the library codes to see if there are other tables which need to be updated.

    Category: System Management (500)


    • Article last edited: 9/29/2014