Oracle® Internet Directory Administrator's Guide 10g (9.0.4) Part Number B12118-01 |
|
Directory Entries Administration, 4 of 5
This section lists and describes some of the more common tasks you perform with bulk tools.
This section contains these topics:
See Also:
To import an LDIF file, you use the bulkload utility. This section discusses the tasks to process an LDIF file through bulkload.
Note: The bulkload utility expects an empty directory and will either fail or overwrite if there are existing entries. Before performing a bulk load, stop the Oracle Internet Directory processes. See Chapter 3, "Preliminary Tasks and Information" for instructions on stopping directory server instances. |
Note: To run shell script tools on the Windows operating system, you need one of the following UNIX emulation utilities:
|
This section contains these topics:
Before you import the file, back up the Oracle database server as a safety precaution.
To use bulkload and the other shell script tools that have commands that end with.sh
, you must provide the Oracle Internet Directory password. The default password is ods
, although the system administrator can change it by using the OID Database Password Utility.
On UNIX, the bulkload.sh
file usually resides in $
ORACLE_HOME/ldap/bin
. On Windows NT, this file usually resides in
ORACLE_HOME\ldap\bin
.
Check the input file by typing:
bulkload.sh -connect connect_string -checkpath_to_ldif-file_name
All schema violations are reported in$
ORACLE_HOME/ldap/log/schemacheck.log
If any violations are detected in the input file, use an ASCII text file editor to fix or remove them. If there are any duplicate entries, their DNs are logged in $
ORACLE_HOME/ldap/log/duplicate.log
.
After you have fixed any errors in the input file, rerun bulkload with the -generate
option as shown in the following example. During this step, LDIF data is converted to SQL*Loader specific format.
bulkload.sh -connect connect_string -generateldif-file_name
All loading errors are reported in$
ORACLE_HOME/ldap/log
When this command completes successfully, it generates *.dat
files in the $ORACLE_HOME/ldap/load
directory to be used by SQL*Loader in -load
mode. Do not modify these files.
After you have generated the input files, rerun bulkload with the -load
option. During this step, the *.dat
files, which are in Oracle SQL*Loader specific format, are loaded into the database and the attribute indexes are created. The syntax is:
bulkload.sh -connect connect_string -load
All loading errors are reported in the $
ORACLE_HOME/ldap/log/directory
with the file extension.bad
.
If bulk loading fails, the database could be left in an inconsistent state. It may be necessary to restore the database to its state prior to the bulk loading operation.
Converting directory data to LDIF by using LDIF Writer makes the data available for loading into a new node in a replicated directory or into another node for backup storage.
The bulkmodify utility enables you to modify a large number of existing entries efficiently.
The bulkdelete utility enables you to delete an entire subtree efficiently.
|
![]() Copyright © 1999, 2003 Oracle Corporation. All Rights Reserved. |
|