The following set of commands will dump all of your relevant information out of your docbase. It will extract all of your content objects (and their content), as well as your formats and users:
The first step in actually performing the load, is to run “preload”. This is another utility program that should be located on your Documentum server. It can be executed from the following command line:
It is therefore possible that you will have duplicate objects in you docbase after a load.
This is common for generic objects that are created with every docbase(such as templates).
It can also occur if you perform two loads from dump files that contain the same objects.
There is no real way to avoid this. Your only option is to manually delete the unwanted duplicates.
In our example, we specified how to set parameters on what objects are dumped from your source docbase.
create,c,dm_dump_record
set,c,l,file_name
c:\temp\adump.new
set,c,l,include_content
T
append,c,l,type
dm_sysobject
append,c,l,predicate
1=1
append,c,l,type
dm_format
append,c,l,predicate
1=1
append,c,l,type
dm_user
append,c,l,predicate
1=1
save,c,l
getmessage,c
This script dumpts all dm_sysobject objects, dm_format objects, and dm_user objects from you docbase. Also the content of these objects will be included. You will notice that for each object type we append a predicate of “1=1″. Since the predicate is required, this is a way of tricking Documentum into exporting all objects.How to Perform a Load
The load process is very similar to the dump process. First, you will probably want to create a brand new docbase. It is possible to load into an existing docbase, but depending on what is in your dump file, you may end up with conflicts in your docbase. You will then want to move your dump file onto the same server as your new docbase (in our case, adump.new). This will reduce network traffic and speed up your load process.The first step in actually performing the load, is to run “preload”. This is another utility program that should be located on your Documentum server. It can be executed from the following command line:
preload -dump_file -script_file -U -P
This performs several checks on your docbase. It may produce a script that you will need to modify and run. If so, the script is well commented and tells you what edits to make. Next, run the iapi32 application again, this time connecting to your new docbase. The following script, when executed, will perform the load process.
create,c,dm_load_record
set,c,l,file_name
c:\temp\adump.new
save,c,l
Documentum does not overwrite objects during the load process.It is therefore possible that you will have duplicate objects in you docbase after a load.
This is common for generic objects that are created with every docbase(such as templates).
It can also occur if you perform two loads from dump files that contain the same objects.
There is no real way to avoid this. Your only option is to manually delete the unwanted duplicates.
It is recommended that you use the following syntax:
set c,l,dump_operation
full_docbase_dump
No comments:
Post a Comment