Documentum几个常见的异常

最新推荐文章于 2022-10-12 18:08:36 发布

haha7

最新推荐文章于 2022-10-12 18:08:36 发布

阅读量1.5k

点赞数

分类专栏： DOCUMENTUM 文章标签： security string object workflow action thread

本文链接：https://blog.csdn.net/haha7/article/details/5442295

版权

DOCUMENTUM 专栏收录该内容

10 篇文章 0 订阅

订阅专栏

[DM_STORAGE_E_MKDIR_FAILED]

01 Apr 2010 10:45:04,600 DfException:: THREAD: ExecuteThread: '82' for queue: 'weblogic.kernel.Default'; MSG: [DfException Occured in Class:AttachWorkFlow Method:startWorkFlow():DfException:: THREAD: ExecuteThread: '82' for queue: 'weblogic.kernel.Default'; MSG: [DM_SYSOBJECT_E_CANT_SAVE]error: "Cannot save sysobject."

01 Apr 2010 10:45:04,600 [DM_STORAGE_E_MKDIR_FAILED]error: "Cannot create storage directory /xxx/xx/xx/xx/xx/content_storage_01/00011e75/80/0a/ce, Method dmSetUpFile(), Operating system error: errno: 2, message: No such file or directory, Retry Count = 2"

[DM_STORAGE_E_MKDIR_FAILED]

Severity: ERROR

Message: Cannot create storage directory %s

Cause: This error is given whenever an error is encountered during the create index step of blobstore creation. It alerts the user that the index creation will fail if another blobstore exists with a similar store name.

Action: Check to see if the blobstore being created has a unique name. Also check the database error given by the previous error message for more information on the create-index failure.

For our app,the cause for the exception is the desk of the content server is full，thus,use can't upload

any file and attach it to workflow.

我今天遇到这个问题，原因是content server的磁盘空间不足，导致用户不能把文件添加到相应的workflow,所以sysobj

的保存也失败了。

[DM_OBJECT_W_SET_ATTR_STRING_TOO_LONG]

"attempt to assign string of excessive length to attribute %i"

CAUSE: Program executed a Set operation to assign a string that is longer than the maximum size allowed for the attribute.

ACTION: No action.

PARAMETERS: The number of the attribute being set.

向目标字段存储的string太长了，超长的部分会被截掉。比如attribute name 是 string(2),但你的update 语句是update xx object set name= 'CSDN'....那么'DN'会被截掉，只有'CS'会被保存。

DM_SYSOBJECT_E_CANT_CHANGE_PERMITS

Severity: ERROR

Message Text: Only the %s sysobject owner, superuser, and anyone with the write and change_permit permits can change permits.

Cause: A user, other than a superuser or sysobject owner, tried to change security permits In ACL security mode, anyone with the WRITE and CHANGE_PERMIT permits are allowed to change security permits.

Action: None.

权限不足是不能够改变sysobject的权限的

D M_SYSOBJECT_E_CANT_CHANGE_OWNER

Severity: ERROR

Message Text: Must be a superuser/owner or anyone with the write and change_owner permits to change the owner_name to '%s'."

Cause: Only a superuser can change the owner_name attribute of a sysobject. In ACL mode, we allow anyone with the write and change_owner permits to change the owner of the object.

Action: None.

权限不足是不能够改变sysobject的owner的.但是即使你是这个sysobject 的owner但不是superuser ，调用setOwnerName还是要小心。

IDfSysObject obj = (IDfSysObject) getDfSession().newObject(<object_tpyp_name>);

obj.set。。。

obj.setOwnerName("XX");

obj.set。。。

obj.save();

上边这个逻辑是会抛出异常的。所以得这样修改

IDfSysObject obj = (IDfSysObject) getDfSession().newObject(<object_tpyp_name>);

obj.set。。。

obj.save();

obj.setOwnerName("XX");

obj.set。。。

obj.save();

为了防止出现其他错误使得obj的保存不完整，还得加上事务处理@@!