- 浏览: 88696 次
- 性别:
- 来自: 上海
文章分类
最新评论
-
zq_zero:
很好,不过如果改为用字符串数组来存储迭代结果和判断是否重 ...
Oracle自定义聚合函数实现字符串拼接 -
sea0108:
good。。
Oracle自定义聚合函数实现字符串拼接
http://www.bluefishgroup.com/library/2003/dump-and-load-a-docbase/
December 21, 2003 - Article by Richard Rans
A brief introduction to the concepts of Documentum’s dump and load feature, as well as an example of performing a dump and load.
– Table of Contents
* Introduction
* How to Perform a Dump
* How to Perform a Load
* Fundamental Concepts
* What if I Have a Problem
Introduction
Dump and load is a feature built into Documentum. It allows you to take the entire contents of your docbase, and write them out to a single file. This can be done not only for content, but for users, groups, acls, etc. The file that gets written out is in a proprietary format, so the only thing you can do with it is load it into another docbase, thus “dump and load”. However, this feature is often used for:
* Backing up your docbase (although you will still probably want a more reliable backup process, like a file system backup).
* Moving or copying your docbase to a new machine or environment (ie, creating a test docbase from your production docbase).
* It is also frequently the recommended upgrade path when moving to a new version of Documentum’s server product.
How to Perform a Dump
The most common method for performing this is using Documentum’s API interface. On the server that Documentum is installed you will find a file called iapi32.exe. Look in your Documentum server directory under product\4.x\bin. Run this application from a DOS window. It will prompt you for the docbase you wish to connect to, as well as a username and password. Connect to the docbase you wish to dump.
You will soon be at an api command prompt. From this prompt, you can issue any of Documentum’s api commands. In this case we will be issueing the command to create a dump file from the docbase you are currently connected to. In most cases, 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:
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. You could have used other criteria, such as:
* object_name=’abcd1′
* folder(’/abcd1′,descend)
Once the dump is complete, you will have a file c:\temp\adump.new that contains all of your docbase information. This file can then be loaded into a new docbase of your choice.
There are additional DFC classes and methods that support XML in Documentum Applications (IDfXMLDocType, DfXmlQuery) that this article doesn’t address, but that hopefully future articles will.
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
Fundamental Concepts
When attempting a dump and load process, there are certain concepts you should understand during the process:
* A dump operation will perform a series of Documentum calls. Each of these calls, in turn, make calls to the underlying database and retrievals from your Documentum filestore(s). This may put unusual strain on your servers. You should be prepared for this and perform you dump and loads during periods when users are not accessing the system. In addition, you need to make sure you have adequate space allocated in your database log and redo files.
* 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.
* In our example, we specified how to set parameters on what objects are dummped from your source docbase. if you intend to perform a full docbase dump, it is recommended that you use the following syntax:
set c,l,dump_operation
full_docbase_dump
* Registered tables are not included in your dump (or load) process. You must manually move and re-register these in your new docbase.
What if I Have a Problem
Occasionally dump or the load will fail. That is why this isn’t the most highly recommended way to perform docbase backups. A detail description of all of the ways to fix a broken dump and load is out of scope of this document. Your best bet is to contact Documentum’s technical support or your system’s integrator. That being said, here as some of the things that you can expect to hear, or that may be causing your problem:
* Did you perform dmclean prior to creating your dump file? This may clean up your docbase and fixes many dump and load issues. See your adminstrators guide for more details.
* Do you have a single folder with thousands of objects in it? Dump and load frequently has problems if there are a tremendous number of documents in a single folder. Try deleting some of your documents that are no longer required, and re-do your dump file. Or, you my be able to execute multiple dumps into separate files by setting a different predicate each time.
* Do you have a single object with thousands of versions? This is common with some of Documentum’s automatically created report files. If you can clean up those objects, it may resolve your issue. You can also configure Documentum to not create or save those reports as frequently. See your adminstrators guide for more details.
* Are you performing a full docbase dump. If not, you may be experiencing a relationship integrity problem. Try a full docbase dump and see if that resolves your issue.
* Add a trace command to your dump script: “apply,c,NULL,SQL_TRACE,LEVEL,I,1″. This may provide some clues as to why the dump is failing.
* Frequently, due to the amount of database activity occuring, your database log files may fill up. You can work with your DBA to increase the size of these files, or even reduce logging during the process.
* Do both of your docbases have the same docbase ID? If so, your load process will fail.
* You have the option of reverting or restarting a load process. To do this, you must make note of the load’s object ID. This object ID will be displayed immediately after you enter the “create,c,dm_load_record” command. To revert the load, issue the following command:
fetch,c,{loadobjectID}
revert,c,l (or issue save,c,l to restart the load)
December 21, 2003 - Article by Richard Rans
A brief introduction to the concepts of Documentum’s dump and load feature, as well as an example of performing a dump and load.
– Table of Contents
* Introduction
* How to Perform a Dump
* How to Perform a Load
* Fundamental Concepts
* What if I Have a Problem
Introduction
Dump and load is a feature built into Documentum. It allows you to take the entire contents of your docbase, and write them out to a single file. This can be done not only for content, but for users, groups, acls, etc. The file that gets written out is in a proprietary format, so the only thing you can do with it is load it into another docbase, thus “dump and load”. However, this feature is often used for:
* Backing up your docbase (although you will still probably want a more reliable backup process, like a file system backup).
* Moving or copying your docbase to a new machine or environment (ie, creating a test docbase from your production docbase).
* It is also frequently the recommended upgrade path when moving to a new version of Documentum’s server product.
How to Perform a Dump
The most common method for performing this is using Documentum’s API interface. On the server that Documentum is installed you will find a file called iapi32.exe. Look in your Documentum server directory under product\4.x\bin. Run this application from a DOS window. It will prompt you for the docbase you wish to connect to, as well as a username and password. Connect to the docbase you wish to dump.
You will soon be at an api command prompt. From this prompt, you can issue any of Documentum’s api commands. In this case we will be issueing the command to create a dump file from the docbase you are currently connected to. In most cases, 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:
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. You could have used other criteria, such as:
* object_name=’abcd1′
* folder(’/abcd1′,descend)
Once the dump is complete, you will have a file c:\temp\adump.new that contains all of your docbase information. This file can then be loaded into a new docbase of your choice.
There are additional DFC classes and methods that support XML in Documentum Applications (IDfXMLDocType, DfXmlQuery) that this article doesn’t address, but that hopefully future articles will.
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
Fundamental Concepts
When attempting a dump and load process, there are certain concepts you should understand during the process:
* A dump operation will perform a series of Documentum calls. Each of these calls, in turn, make calls to the underlying database and retrievals from your Documentum filestore(s). This may put unusual strain on your servers. You should be prepared for this and perform you dump and loads during periods when users are not accessing the system. In addition, you need to make sure you have adequate space allocated in your database log and redo files.
* 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.
* In our example, we specified how to set parameters on what objects are dummped from your source docbase. if you intend to perform a full docbase dump, it is recommended that you use the following syntax:
set c,l,dump_operation
full_docbase_dump
* Registered tables are not included in your dump (or load) process. You must manually move and re-register these in your new docbase.
What if I Have a Problem
Occasionally dump or the load will fail. That is why this isn’t the most highly recommended way to perform docbase backups. A detail description of all of the ways to fix a broken dump and load is out of scope of this document. Your best bet is to contact Documentum’s technical support or your system’s integrator. That being said, here as some of the things that you can expect to hear, or that may be causing your problem:
* Did you perform dmclean prior to creating your dump file? This may clean up your docbase and fixes many dump and load issues. See your adminstrators guide for more details.
* Do you have a single folder with thousands of objects in it? Dump and load frequently has problems if there are a tremendous number of documents in a single folder. Try deleting some of your documents that are no longer required, and re-do your dump file. Or, you my be able to execute multiple dumps into separate files by setting a different predicate each time.
* Do you have a single object with thousands of versions? This is common with some of Documentum’s automatically created report files. If you can clean up those objects, it may resolve your issue. You can also configure Documentum to not create or save those reports as frequently. See your adminstrators guide for more details.
* Are you performing a full docbase dump. If not, you may be experiencing a relationship integrity problem. Try a full docbase dump and see if that resolves your issue.
* Add a trace command to your dump script: “apply,c,NULL,SQL_TRACE,LEVEL,I,1″. This may provide some clues as to why the dump is failing.
* Frequently, due to the amount of database activity occuring, your database log files may fill up. You can work with your DBA to increase the size of these files, or even reduce logging during the process.
* Do both of your docbases have the same docbase ID? If so, your load process will fail.
* You have the option of reverting or restarting a load process. To do this, you must make note of the load’s object ID. This object ID will be displayed immediately after you enter the “create,c,dm_load_record” command. To revert the load, issue the following command:
fetch,c,{loadobjectID}
revert,c,l (or issue save,c,l to restart the load)
发表评论
-
调用DFS创建文档报 type dm_literal_expr failed
2012-03-18 16:06 1613调用DFS时报如下错误: [DM_SESSION_W_FET ... -
Assign multiple groups as performer of activity using code in workflow
2012-02-03 17:02 932I determine the groups dynamica ... -
content server
2012-02-02 15:23 704当使用的composer修改属性的相关约束条件,比如是否为空, ... -
dfc session Monitor
2012-01-31 10:53 988You can enable logging on the s ... -
DFC Session Management Srinivas Jakkula
2012-01-19 14:02 1663摘要:这个文档从application出发,介绍DFC Ses ... -
Documentum
2012-01-04 18:35 874查询所有需要在属性页要显示的属性 select r_o ... -
query attribute map dictionary
2011-12-28 13:15 776select map_display_string, map_ ... -
Invoking UCF in custom import component
2011-12-28 13:09 11611)I have made some changes in t ... -
When open tasklist form, it pops up exception casued by [DM_SESSION_E_SETUP_ROLE
2011-12-28 13:05 2356Symptoms An error has occurr ... -
dfc trace performance anaysis
2011-09-14 09:57 10751)设置dfc.properties enable dfc t ... -
Tuning the Performance of documentum UCF Content Transfer
2011-05-27 09:12 3129In Documentum applications, the ... -
Add or delete a custom attribute
2011-03-22 10:43 7311)alter type <custom_type&g ... -
Some basic guidelines for setting the J2EE Application Server JVM memory
2011-03-21 14:40 2352Please refer to WDK/Webtop depl ... -
type attribute label is not localized
2011-03-09 16:41 873you will have to clear cache an ... -
Acs is enabled or not(test code)
2011-03-08 20:03 1708引用 /*************************** ... -
Tuning the Performance of UCF Content Transfer
2011-03-07 17:04 1298Tuning the Performance of UCF C ... -
无法保存preset
2010-11-15 16:56 861错误图见附件。 解决方法: 确认dm ... -
jobs Window Interval parameter
2010-10-29 10:05 1034"The Window Interval. When ... -
DFC own Administrator permission
2010-10-27 14:54 7331.add user to dm_superusers_dyn ... -
install webtop.dar error
2010-10-17 15:25 1039com.emc.ide.installer.InstallEx ...
相关推荐
dump文件load后数据库访问不了解决办法
SYBASE数据库的DUMP与LOAD[参照].pdf
redis-dump-load 将Redis数据集转储为适合长期存储的格式(当前为JSON),并将数据从此类转储文件加载回Redis。 特征 redis-dump-load: 支持所有Redis数据类型; 转储TTL和到期时间; 可以加载TTL或原始过期...
本篇文章主要介绍了Python Json模块中dumps、loads、dump、load函数介绍,详细的介绍了这几种函数的用法,具有一定的参考价值,感兴趣的小伙伴们可以参考一下
Thread and Monitor Dump Analyzer for Java
分析线程情况 JavaCore 或 ThreadDump文件,即线程的映像,用来分析线程资源锁等情况
今天小编就为大家分享一篇使用pickle存储数据dump 和 load实例讲解,具有很好的参考价值,希望对大家有所帮助。一起跟随小编过来看看吧
IBM Thread and Monitor Dump Analyzer for Java(简称 jca)。它可以识别Java线程中的挂起,死锁,资源竞争,和瓶颈。 使用方法: java -Xmx1000m -jar jca456.jar
主要介绍了Mysql注入中的outfile、dumpfile、load_file,需要的朋友可以参考下
IBM 线程堆栈分析工具,IBM Thread and Monitor Dump Analyzer for java
DumpTool主要用来在用户机器上对目标进程生成dump文件,定位“卡死”、Crash等问题。 (1)MiniDump: 表示生成一个包含必要信息的dump文件,文件大小约200-500k,具体Flag =MiniDumpNormal|...
TMDA
thread and mointor dump analyzer,java线程文件分析工具
IBM Thread and Monitor Dump Analyzer for Java,javacore分析工具,使用方法,在liunx上解压,执行命令java -Xmx500m -jar jca395.jar
The full transcript of Software Diagnostics Services training with 13 step-by-step exercises, notes, source code of specially created modeling applications and selected Q&A. Covers 22 .NET memory dump...
管理员密码获取 ADump.rar
Linux Core Dump 权威书籍
Dump文件编辑中文版 分析DUMP文件数据 修改数据