Size of all objects within a folder structure

I was recently tasked with adjusting a LiveReport to include a column for "file size." I have 2 questions.

1) Is there a master list for item attributes (ie. name, dataid, and versionnum for dtree or datasize, docid, and version for dversdata)? And if so where would I find it or could you send it to me?

2) I understand that dtree records all items (folders, documents, workflows, etc.) but I have been unable to find the attribute related to the size of those elements (ie. dtree.x where x= size of the item in bytes), similarly with dversdata I understand that it holds the latest version of an item but it only seems to handle documents and other files (ie. dtree.docid) but not folders or workflow maps. How would I write out the sql so that the LiveReport would show the size of folders, workflow maps, etc. in addition to documents, messages and the like?

Find more posts tagged with

Comments

Colin_Schmidt

DTREE contains all core objects.

For objects with versioning, you find those pieces of information in the DVERSDATA table.

It has MIMETYPE, FILESIZE, etc. If you have a DB Tool like SQL Developer, TOAD, ADS for Oracle or Visual Studio for SQL Server, you'll see the columns.

Colin J.

On Tue, Dec 2, 2014 at 4:14 PM, eLink Entry: Content Server LiveReports Forum <livereportsdiscussion@elinkkc.opentext.com> wrote:

Size of all objects within a folder structure Posted bymatthew.waters@lmco.com (Waters, Matthew)On 12/02/2014 04:12 PM

I was recently tasked with adjusting a LiveReport to include a column for "file size." I have 2 questions.1) Is there a master list for item attributes (ie. name, dataid, and versionnum for dtree or datasize, docid, and version for dversdata)? And if so where would I find it or could you send it to me?2) I understand that dtree records all items (folders, documents, workflows, etc.) but I have been unable to find the attribute related to the size of those elements (ie. dtree.x where x= size of the item in bytes), similarly with dversdata I understand that it holds the latest version of an item but it only seems to handle documents and other files (ie. dtree.docid) but not folders or workflow maps. How would I write out the sql so that the LiveReport would show the size of folders, workflow maps, etc. in addition to documents, messages and the like?
[To post a comment, use the normal reply function]
Forum: Content Server LiveReports Forum
Content Server: Knowledge Center

This electronic message contains information from MeadWestvaco Corporation (mwv.com) or subsidiary companies, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify MeadWestvaco immediately at postmaster@mwv.com.

eLink User

OT releases livelink schema to anybody (free.....) who signs a NDA (Non Disclosure) with them it is usually done thru your sales contact.Many people peruse the "knowledge base" or "champion toolkit" in these forums and work through common queries etc to do what they intend to do.People well versed in DB activities can use tools that will show you an ER diagram as well.

Livelink typically can store versionable data like documents(144) in about 3 main things called

SQL like Sharepoint does which is very inefficient
Most companies will put them in a file system called EFS
Some companies will store them in Archive Server.

So given a dataid you should ask dversdata for the providerid then tie

select * from providerdata where providerid in (
select providerid from dversdata where docid in (select dataid from dtree where dataid=741021))

in the above query 741021 is in my system a category and it will show me where in EFS it is located.If I don't need to reconcile the physical file size I can do an aggregate on the filesize in dversdata.

Folders do not consume file space they are found by counting all objects inside them and tabulating them using dtreeancestors or by using CTE's in SQLserver or the trusted "connect by" construct in Oracle.

None of the database queries for file size will reflect what is on disk because livelink uses "copy optimization" by itself so if the same object is copied more than once livelink will only hold that object once and increment or decrement a refcnt so if you run into situation like I counted all objects and it came to 850 MB but on disk it shows 800 where did my difference go that kind could happen.

Lindsay Davies is an OT expert who tries to help people in these forums and I have found his posts very nice and explanatory.This livelink has an awesome search as well.

..Appu

I wonder how one could debug livelink if Fiddler, Wireshark and Softerra LDAP browser was not invented and not free