dbxml_load_container [-d home] [-c container]
    [-s node|wholedoc] [-f file_list]
    [-p file_list_path] file1.xml file2.xml file3.xml ...

Description

The dbxml_load_container utility loads the identified XML documents into the identified container. XML files can either be identified as arguments to this command, or they can be identified in a file that is specified using the -f option.

Do not run this utility against an environment actively in use by another process. This utility does not share environments and you should not attempt to use it on an environment in use by another process. That is, this utility is meant for off-line use only.

If you run this utility against a transactionally protected container, you will need to dump the container to ensure that it can be restored. Mixing transactional writes with non-transactional writes can result in unrecoverable containers. Follow these steps to use this utility to load documents into an existing transactionally protectect container:

1. Make sure that there are no processes with open handles to the container.

2. Checkpoint your environment.

3. Use dbxml_load_container to load your documents.

4. Perform a hot or regular backup.

5. Start updating the container transactionally again.

The options are as follows:

-c

Specify the name of the container into which your want to load the identified documents. If the container does not currently exist, it is created for you.

-d

Specify the home directory for the database environment; by default the current working directory is used.

-f

Specify a file that contains a list of XML files to load into the container.

-p

Specify a path prefix to prepend to every filename contained in the file list specified by the -f option.

-s

Specify the container type. Valid value are:

• node

  Use node-level storage. XML documents are broken into their individual nodes, and the nodes are stored as individual records in the underlying database. This is both the default and the recommended container type.

• wholedoc

  Use whole-document storage. Entire XML documents are stored as individual records in the underlying database.

Note that if the container already exists, this option is ignored.

The dbxml_load_container utility exits 0 on success, and >0 if an error occurs.