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

    Data transfer for switch to production: Oracle data only?

    • Article Type: Q&A
    • Product: Aleph
    • Product Version: 20, 21, 22, 23


    In running Upgrade Express for Production after having done an initial test upgrade and making our local modifications to the u-tree, should the "Create Customer data" be done with "Pack the u-tree" and the Oracle data -- or just the Oracle data?

    Would all the modifications need to be redone if we moved over both the u-tree and the data?


    Yes, when the u-tree is moved over, all the modifications *would* need to be redone.


    A. Check the $alephe_root, $alephe_tab, and each library's $data_tab for changes which have occurred in your old version since the copy of the u-tree in the initial test upgrade -- and then make those same changes in the new version.

    B. Move only the Oracle data in doing the Production refresh.  Steps:

      On the Source server:

         2. Export customer data  

           ->  1. Export Oracle data  (this will generate the ./data/a20_1.tar.gz file), then:

         3. Transfer customer data to the target location   (or use sftp to do manual transfer)

      On the Target server:

         2. Install customer data

            -> 1. Install Oracle data      

    Note:  In doing this as part of the actual cutover, Aleph should be down on both the Source server and the Target.


    Category: Installation & Upgrades (500)

    Subject: Upgrade Express (500)

    • Article last edited:  06/24/2019