Documentum Jobs in Accenture (2+ Years)

To learn more about BOF Business object framework

here is the link it contains about 10 of pdf documents talking about
BOF in details

http://www.freewebs.com/documentm/

good luck

 

"Another publish operation is in progress. Could not obtain a lock..."

Our publish job failed due to insufficient disk space. We cleared some
space and server was also rebooted. However now the publish is failing
with the following error: 

"ERROR: Another publish operation is in progress. Could not obtain a
lock after 30 retries...exiting"

I checked the webcache.ini and there are no port locks. Server has
already been rebooted since the publish failed. I have no idea how to
release the lock. Any ideas please ? Thanks in advance... 

 

Can you visit this site and add comments so that i improve , thnks

http://www.freewebs.com/documentm/index.htm

 

Re: "Another publish operation is in progress. Could not obtain a lock..."

Found the answer in the EMC knowledgebase: 

1. Go to DQL editor
2. Select r_object_id, object_name, title, r_modify_date from
dm_webc_config
3. Copy the r_object_id value 
4. SELECT r_object_id FROM webc_lock WHERE object_name =
'r_object_id_from_step_3'
5. Copy the r_object_id
6. Update webc_lock OBJECT set holder = '' WHERE r_object_id =
'r_object_id_from_step_5'

 

Cabinet Permission rights do not propagate to folders, subfolders, and files

When I assign cabinet permission rights to a user, the rights do not 
propagate to the cabinet's folders, subfolders, and files.  Any 
ideas?  Thanks in advance.

 

Index Server Moving to SAN

Group Memmber,
                Currently in our enviornment we have seperate Index 
Server which is on Stand-alone server.
Now a requirement came in to move the index server from stand alone 
server to SAN (Storage Area network).
Do it require to un-install the index server and again re-install it 
and then create the index agents for the docbase?

Please suggest :)

Thanks
Sumeet

 

Re: Cabinet Permission rights do not propagate to folders, subfolders, and files

Documentum assigns ACL to new objects according to default_acl 
attribute of dm_server_config object. There are three possible values 
for this attribute, 1-to assign default ACLs based on Folder, 2 to 
assign based on Object Type, and 3 to assign based on User. Default in 
documentum is 3, or default ACLs are set by user. If you want rights 
to propagate thru folder hierarchy you have to set this attribute to 
1. I am not sure about should you restart docbase after that, but you 
can do it, for every case :). Hope this helps.

Regards

--- In documentum-users@..., "yafinni" <yafinni <at> ...> wrote:
>
> When I assign cabinet permission rights to a user, the rights do not 
> propagate to the cabinet's folders, subfolders, and files.  Any 
> ideas?  Thanks in advance.
>

 

Re: Index Server Moving to SAN

Re: Re: Cabinet Permission rights do not propagate to folders, subfolders, and files