The easiest thing to do would be a DIFF between the current storage file system and new then disregard new writes. Thick client consistency checker was good as you would get a report of what was missing and where. The web based version just shows content missing / exceptions but not in a usable format. Your other option is to use the API and call validate content, for anything that fails attempt to retrieve the content and an exception will be thrown providing the full path of where the document should be. Or as you are working on restoring to a new system which should also include the GCD unless you already have a mirrored system then run these checks.
Original Message:
Sent: Mon August 11, 2025 11:39 AM
From: Mick Doyle
Subject: P8 Content location from DB
Hi all
Found this response from 2023 - Get Content Path of Document in Filenet | Content Management and Capture it is identical to what I am trying to achieve. So it looks like the info is not available directly into the DB... we are looking at a DB restore now and use API to 'report/show' content location. Will provide update if that works
Thanks
------------------------------
Mick Doyle
Original Message:
Sent: Mon August 11, 2025 10:35 AM
From: Stephen Weckesser
Subject: P8 Content location from DB
In the current release the location is obfuscated. In past versions the filename and the docid were related - that might help if it's an older version.
The consistency tool (xcheck) is no longer a standalone app but if you have an older version, you could try. xcheck reports the id's of the files and their location if they are missing. The output will be unwieldly but you can convert it to a csv using the below. (it's my site, the SSL cert is expired, ignore that)
https://www.applied-logic.com/reformat-consistency-check-reports/
One could deobfuscate the location but any such effort would be version specific and would not decrypt the content if encryption was enabled. It might be easier to restore the system and use the API to export the docs. It's not fast, but it solve the decryption (and/or deduplication).
BTW, DocVersion does not contain all the metadata. There's list of string, list of dates, etc.
------------------------------
Stephen Weckesser
Original Message:
Sent: Fri August 08, 2025 10:37 AM
From: Mick Doyle
Subject: P8 Content location from DB
Customer has deleted a few 000 documents on FileStore which has removed content and DB references, However they have backups of both.
Customer wants to restore old DB to ProdServer2 and query docversion table direct to get metadata but does NOT want to restore FileStore in its entirety.
Question: Is the actual location (full path) of the content extractable from P8 tables at an individual file level?
If so, customer can them simply restore the files needed and re-import them again later.
Mick Doyle
------------------------------
Mick Doyle
------------------------------