Local connection is Detected while Creating Connection between Different Jira On-premise Instances

    This article applies to Exalate Classic only. If you're using the New Exalate experience, please refer to the New Exalate documentation.

    Problem

    You have 2 Jira on-premise instances and you're trying to set up a Connection between them.

    Error detail:

    Cause

    When the instances are created from the same back up they have the same server ID.

    Exalate uses the server ID to detect the local connection type.

    Solution

    You need to update a table in the database.

    The database table name is NODE.

    Run the following query to change the ID.

    UPDATE "AO_08F1AF_NODE" SET "INSTANCE_UID" = '<PICK A NEW UNIQUE IDENTIFIER>'