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, 21, 22, 23

    Question

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

    Answer

    The following are the four most common situations.  Certain of the procedures can be complicated.  A site may want to contract with Ex Libris Professional Services to perform them....

    1.  In a single-Bib / multi-ADM situation, an ADM library (and the associated Course library) needs to be removed, while other xxx50 and xxx30 libraries need to remain.  

     ** See the article " How to remove an ADM library ".  In the case of the xxx30 Course library, after all of the tables have been successfully backed-up/exported, drop/delete the Oracle data for each library, using the SQL "drop user xxx30" command <where "xxx30" is the library>.  This will drop all of this library's tables (besides dropping the user).  Note:  certain xxx30 records are associated with xxx50 records (such as the z30, the z108, and the z107).   These tables are removed by the manage-92 ("Remove library") Service, described in the " How to remove an ADM library " article.

     

    2.  All of the libraries for all institutions need to be removed.  (Aleph is being migrated to a different library system.)

    ** The attached document  ,@api,deki,files,63883,Exporting_Aleph_Oracle_tables_to_another_vendor.docx  describes the export of a library's MARC bibliographic data using the print-03 Service and the other non-MARC tables using the file-03 Service. (If the library is being moved to a different Aleph installation, it may be that the Oracle Data Pump could be used.)

    There is no need to export the temporary or index tables, just the base tables. {See the article " 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).

     

    3.  All of the libraries (bib, adm, hol, course) for a particular institution need to be removed.  

    ** 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.   In this case certain shared files (such as the $usr_library patron files, the $pw_library files, and the shared z00p table) need to be considered.

        a. Remove the ADM library (abc50), as described in the 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, certain steps in that Article's Procedure may not be relevant, but step 5 {" Preventing access by staff and patrons of ADM library to be removed "}, having to do with deletion/preservation of shared patron records, is relevant.

        b. Export all of the other libraries' Oracle tables. The attached document  ,@api,deki,files,63883,Exporting_Aleph_Oracle_tables_to_another_vendor.docx  describes the export of a library's MARC bibliographic data using the print-03 Service and the other non-MARC tables using the file-03 Service. (If the library is being moved to a different Aleph installation, it may be that the Oracle Data Pump could be used.)

    There is no need to export the temporary or index tables, just the base tables. {See the article " 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 (the "u-tree"). There are two cases:  (1) where ABC has its own u-tree (at /exlibris/aleph/abc/unn_n/) and (2) where ABC shares the u-tree (at /exlibris/aleph/unn_n/).   In the first case, one would go to /exlibris/aleph/abc/ and tar/zip the unn_n/ directory, export it, then delete it:  rm -fr unn_n .   In the second case one would export the /exlibris/aleph/unn_n/abcnn/ library directories and then delete them:

         1) delete the library from the u-tree:
         > dlib xxxnn
         > dr
         > cd ..
         > rm -fr xxxnn

       and then edit various tables in the shared /exlibris/aleph/unn_n/alephe and ./alephe/tab directories
            $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

      to remove the library code....   $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.

     

    4. A sublibrary needs to be removed  

      ** Consult the articles:

            How to run p_item_11 item deletion for particular sublibraries *MASTER RECORD* 

            Question about removing a sublibrary from Aleph , and

            Changing sublibrary codes


     

    Category: System Management (500)


    • Article last edited: 18-Apr-2018