dm_blog

In my last few posts, I described how to install a Content Server with distributed filestores. In this blog post, I’ll discuss a few DQL queries to track your files in a distributed setup.

The first set of DQL queries will help you get information regarding storage of content, include its filestore and path:

This query returns the actual file system path to object’s content file. Use this query in conjunction with the second query to find out exactly where your content files are stored on the content server.

To find file system path of an object’s content file:

select file_system_path from dm_location where object_name in (select root from dm_filestore where name in(select a_storage_type from dm_document where r_object_id = ‘object_id’))

To find file store a file is saved on:

Now that you have the file system path, use the following query to identify the file store your file is stored on:

select a_storage_type from dm_sysobject where r_object_id = ‘object_id’

With above two queries, you should be able to zero down on the location of the file.

To find the default file store of a type:

To find out the default filestore for a type (e.g. my_document), use the following query:

select name from dm_store where r_object_id in(select default_storage from dmi_type_info where r_type_id in(select r_object_id from dm_type where name = ‘my_document’))

You can also find the default location for a type via DA. Just log on to DA and go to “Types” in the navigation tree on left. Browse or Search your desired type and check default storage.

To find out disk space used by a particular file store:

select sum(content_size) from dmr_content where storage_id in (select r_object_id from dm_store where name =  ‘file store name’)

Again, this can also be checked via DA (DA->Storage->filestore)

And finally, to find out the root directory of the filestore of particular type i.e. my_document, use the following DQL

select file_system_path from dm_location where object_name in(select root from dm_filestore where r_object_id in(select default_storage from dmi_type_info where r_type_id in(select r_object_id from dm_type where name = ‘my_document’)))

In my next post, I’ll discuss tips and tricks to identify and resolve issues in a distributed setup.

admin Content File Server, Distributed Setup, Documentum, Documentum 6.5, Documentum distributed setup, Remote Content File Server, single repository distributed storage Distributed Filestores, DQL, find location, location, multiple filestores, track files