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

    Exported normalization rules are being imported into the wrong machine

    • Article Type: General
    • Product: Primo
    • Product Version: 3

    Problem Symptoms:
    - Normalization rules set is exported using the export script - ./export_nm_config.sh <set_name>
    - Import script is run in the target machine - ./import_nm_config.sh <imp_dir>
    - The normalization set is being imported into another machine.

    Cause:
    A parameter "property name="hibernate.connection.url" in hibernate.cfg.xml is not updated with the current machine's name.

    Resolution:
    1.? In the FE servers, edit hibernate.cfg.xml:
    cd /exlibris/primo/p<r>_<x>/ng/primo/home/profile/publish/knp/conf/import
    vi hibernate.cfg.xml

    2. Update the parameter <property name="hibernate.connection.url> which set the database connection the following format:
    jdbc:oracle:thin:@<database_server><SID>
    Where:
    <database_server> ?€“ Indicates the database server with port, for example: <serverhostname:1521>.
    <SID> ?€“ Indicates the SID (which is usually prm3 or prm4).

    3. Run the import script again.

    Additional Information

    Information on normalization rules export and import can be found on Primo System Administration Guide, chapter 5 - "Copying Primo Data from One Machine to Another" (April 4, 2012 version).

    Category: BO Configuration

    Subject: Normalization Rule Configuration


    • Article last edited: 11/21/2013
    //Feedback