Professional Documents
Culture Documents
Abstract
This white paper is intended to help users understand the EMC Documentum dump and load utility and
troubleshoot problems encountered when using it.
August 2007
Table of Contents
Executive summary ............................................................................................ 4
Introduction ......................................................................................................... 4
Audience ...................................................................................................................................... 4
Preload................................................................................................................. 7
Load ..................................................................................................................... 7
Before you perform the load ........................................................................................................ 7
Sample script to load ................................................................................................................... 7
Executive summary
The EMC Documentum dump and load utility let you copy a full or partial repository, including content
from one machine to another. As with any migration across platforms or different databases, the utility
helps keep the Documentum data integrity intact.
Most businesses need to test their upgrades on a copy repository prior to their actual production in-place
upgrades. When trying to move a repository to a different database, dump and load is the best option.
Introduction
This white paper is intended to help users understand the Documentum dump and load process and
troubleshoot problems encountered when using dump and load. It provides information about dump and
load, tips and tricks, and best practices. For complete technical information on dump and load, please refer
to the EMC Documentum Content Server Version 5.3 SP 3 Release Notes and the EMC Documentum
Administrator Version 5.3 SP 1 User Guide.
Dump and load is not recommended or made for use as an alternate to a backup and restore utility.
Audience
This white paper is intended for repository administrators and developers who intend to copy or move full
or partial repositories. It also gives them a baseline overview of how dump and load works, and will help
them choose a custom predicate for their custom dumps requirement.
This white paper is not intended to assist developers who are writing custom scripts. In addition, this paper
is not intended to help administrators with troubleshooting their database issues prior to or after a dump and
load. Readers should consult their database administrators for any database issue prior to or during the
dump and load process.
Key features
Dump and load utilities provide users the ability to copy or move their repository from one machine to
another machine or onto the same machine. You can copy a partial repository, that is, a folder, a cabinet,
document of a particular type and so on. You can also do the following with dump and load utilities:
Copy a repository
Archive a repository
Work on cross-platforms
Work on cross-databases
Dump
A dump occurs by creating a dump record object and issuing a Save API on this dump record. The dump
creates a dump file that is in binary format. The dump file size depends on how the dump script looks like.
By default, the dump file contains only metadata so the dump contains only the reference to the content
file, but if you add to include the content parameter in the dump script then the dump file size will be
bigger since it includes the content and metadata.
The group to which that user belongs (dm_group), excluding other users
Ensure that there is enough disk space to accommodate the dump file.
smaller dump file size and a slightly faster dump. If the source and target repositories are on the same
machine then use include_content to F.
Run a count on dm_sysobject, dm_document, dmr_content, dm_user, and dm_group before you perform
the dump.
Type definitions are also dumped. If a subtype doesnt have any objects, then a subtype definition is
not dumped unless you specify that type in the dump script.
ACLs not associated with objects will not be dumped unless they have an entry in the dump script.
The following shows how to describe the custom type in the dump script:
append,c,l,type
your_type_name
append,c,l,predicate
1=1
1=1 means all objects of your custom type. To dump a smaller set you can use the WHERE clause in
the predicate attribute. The predicate has a maximum character size limit of 255.
However, when you dump an object, the server includes any objects referenced by the dumped object.
This process is recursive, so the resulting dump file can contain many more objects than the object
specified in the type, predicate, and predicate2 repeating attributes of the dump record. For example,
for dumping objects under a single cabinet, you can use the following predicate:
append,c,l,type
dm_sysObject
append,c,l,predicate
folder('/<name of the cabinet>',descend)
apply,c,NULL,SQL_TRACE,LEVEL,I,1
To disable SQL trace, use the following line as the last line of your dump or load script:
apply,c,NULL,SQL_TRACE,LEVEL,I,0
Preload
The filestore names of the associated content must match in the source and target repositories. To generate
a list of filestores that needs to be created before you run the load, you need to run the preload utility.
The syntax for the preload utility is as follows:
C:\> preload repository [-Uusername] -Ppassword -dump_file filename [-script_file name]
Load
A load is performed after creating a dm_load_record on the target repository. After finishing the dump on
the source repository, copy the dump file on to the target machine and run the load script via IAPI.
Create the necessary filestores as mentioned by preload results. Only the name has to match; the
location can be different.
The user performing the load should have read/write permission on this file.
If the dump didnt include content, the repository owner should have access to the source filestore.
Conclusion
This white paper has provided a step-by step process to do dump and load. Most of the technical details and
architecture overview has been described. Contact EMC Support for any issues that may arise during the
dump and load process.