4.3 bulkmodify

The bulkmodify command-line tool enables you to modify a large number of existing entries in an efficient way. The bulkmodify tool supports the following:

Subtree based modification
A single attribute filter. For example, the filter could be objectclass=*, objectclass=oneclass, or telephonenumber=*.
Attribute value addition and replacement. It modifies all matched entries in bulk.

The bulkmodify tool performs schema checking on the specified attribute name and value pair during initialization. All entries that meet the following criteria are modified:

They are under the specified subtree.
They meet the single filter condition.
They contain the attribute to be modified as either mandatory or optional.

The directory server and directory replication server may be running concurrently while bulk modification is in progress, but the bulk modification does not affect the replication server. You must perform bulk modification against all replicas.

Note:

LDIF file based modification is not supported by bulkmodify. This type of modification requires per-entry-based schema checking, and therefore the performance gain over the existing ldapmodify tool is insignificant.

Make sure that when bulkmodify is invoked, server side entry cache is disabled.

You must restrict user access to the subtree during bulk modification. If necessary, access control item (ACI) restriction can be applied to the subtree being updated by bulkmodify.

You cannot use bulkmodify to add a value to single-valued attributes that already contain one value. If a second value is added, you must alter the directory schema to make that attribute multi-valued.

You cannot use bulkmodify to update the following attributes:

dn (use ldapmoddn instead)
cn (use ldapmodify instead)
userPassword (use ldapmodify instead)
orclPassword (use ldapmodify instead)
orclACI (use ldapmodify instead)
orclEntryLevelACI (use ldapmodify instead)

4.3.1 Syntax for bulkmodify

bulkmodify -c connect_string -b "base_dn" {-a attr_name | -r attr_name}  -v attr_value [-f filter] [-s number_of_entries] [-E character_set]

4.3.2 Arguments for bulkmodify

-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.

-b "base_dn"

Required. The DN of the subtree to be modified. Enclose the DN in quotes.

-a attr_name | -r attr_name

Required. The name of a single attribute to either add (-a) or replace (-r).

-v attr_value

Required. The single attribute value to add or replace. If the value contains spaces, enclose it in quotes.

-f filter

Optional. A filter string that contains a single attribute. Defaults to objectclass=*.

-s number_of_entries

Optional. The number of entries to be committed as part of one transaction. Defaults to 100.

-E character_set

Optional. The native character set encoding. Defaults to the character set of the user's terminal. Each supported character set has a unique acronym, for example, WE8MSWIN1252, JA16SJIS, or AL32UTF8.

4.3.3 Tasks and Examples for bulkmodify

Using the bulkmodify tool, you can perform the following task:

Updating an Attribute for Multiple Entries at Once

4.3.3.1 Updating an Attribute for Multiple Entries at Once

The following example shows how to modify an attribute for several entries using a filter. This command adds the telephone number 408-123-4567 to the entries of all employees who have Anne Smith as their manager.

Example:

bulkmodify -c orcl -b "c=US" -a telephoneNumber -v "408-123-4567" -f "manager=Anne Smith"

4.3 bulkmodify

4.3.1 Syntax for bulkmodify

4.3.2 Arguments for bulkmodify

4.3.3 Tasks and Examples for bulkmodify

4.3.3.1 Updating an Attribute for Multiple Entries at Once

4.3.4 Related Command-Line Tools for bulkmodify