5.1 hiqretry.sh

When a replication conflict arises, the Oracle Internet Directory replication server places the change in the retry queue and tries to apply it from there for a specified number of times. If it fails after that specified number, then the replication server puts the change in the human intervention queue. From there, the replication server repeats the change application process at less frequent intervals while awaiting your action.

At this point, you need to:

1. Examine the change in the human intervention queue.

2. Reconcile the conflicting changes using the Oracle Internet Directory Reconciliation Tool (see "oidreconcile").

3. Either place the change back into the retry queue (using hiqretry.sh) or into the purge queue (see "hiqpurge.sh").

Note: The Oracle Internet Directory server parameter orclSizeLimit, which is 1000 by default, limits the number of entries that the Human Intervention Queue Manipulation Tool can process . If you have more than 1000 entries in the human intervention queue, you must increase orclSizeLimit, or some entries will never be processed. Setting the parameter orclSizeLimit very high will impact server performance, because orclSizeLimit also controls the maximum number of entries to be returned by a search.

5.1.1 Syntax for hiqretry.sh

hiqretry.sh -connect connect_string {{-start change_number -end change_number }| {-equal change_number }} -supplier supplier_node

5.1.2 Arguments for hiqretry.sh

-connect connect_string

Required. The directory database connect string. If you already have a tnsnames.ora file configured, then this is the net service name specified in that file, which is located in $ORACLE_HOME/network/admin.

-start change_number

When specifying a range of change numbers to move from the human intervention queue into the retry queue, this argument specifies the starting change number. If you skip this argument, then the tool moves all the changes with change numbers less than or equal to the specified end change number back to the retry queue.

-end change_number

When specifying a range of change numbers to move from the human intervention queue into the retry queue, this argument specifies the ending change number. If you skip this argument, then the tool moves all the changes with change numbers greater than or equal to the specified start change number back to the retry queue.

-equal change_number

This argument specifies a single change number to move from the human intervention queue to the retry queue. This argument cannot be used with the -start or -end arguments.

-s supplier_node

Required. Specifies the supplier node where the changes originate.

5.1.3 Tasks and Examples for hiqretry.sh

Using the hiqretry.sh command-line tool, you can perform the following tasks:

• Retrying a HIQ Change Log

• Retrying a Range of HIQ Change Logs

• Retrying all HIQ Change Logs from a Supplier

5.1.3.1 Retrying a HIQ Change Log

The following example shows how to move a single replication change log conflict from the human intervention queue (HIQ) back into the retry queue. It moves the change numbered 10519 coming from the supplier node ldap_rep1.

Example:

hiqretry.sh -connect oiddb1 -equal 10519 -supplier ldap_repl

5.1.3.2 Retrying a Range of HIQ Change Logs

The following example shows how to move a range of replication change log conflicts from the human intervention queue (HIQ) back into the retry queue. It moves changes numbered between 10324 to 10579 coming from the supplier node ldap_rep1.

Example:

hiqretry.sh -connect oiddb1 -start 10324 -end 10579 -supplier ldap_repl

5.1.3.3 Retrying all HIQ Change Logs from a Supplier

The following example shows how to move all replication change log conflicts originating from a certain supplier from the human intervention queue (HIQ) back into the retry queue. It moves changes coming from the supplier node ldap_rep1.

Example:

hiqretry.sh -connect oiddb1 -supplier ldap_repl

5.1.4 Related Command-Line Tools for hiqretry.sh

• See "hiqpurge.sh"

• See "oidreconcile"