Question

Diretory and File Pathnames check file gdb for locks

  • 16 December 2019
  • 3 replies
  • 9 views
D
Badge

I am trying to implement a workflow that will check a specified FDGB directory for the presence of .lock files and use the ownership information of those lock files to email the users to disconnect so the data can be updated. The problem is that the path_ownername attribute is not being returned by the Directory and File Pathnames reader. I have tested this in multiple FGDBs and the only time I get a value for path_ownername is when I change the extension to .atx (which doesn't help) or when I use a directory that has some older (orphaned?) lock files with last modification dates of a day or more. What method does the reader use to harvest these attributes ? Perhaps there could be a security related interference or a default permissions problem

3 replies

david_r
Rank
Userlevel 4

As per the documentation, you need to activate "Retrieve file properties" on the reader for this attribute to be set:

See: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/path/Feature_Representation.htm

Be aware that activating this option will slow down the reader a little bit for each returned file.

D
Badge

As per the documentation, you need to activate "Retrieve file properties" on the reader for this attribute to be set:

See: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/path/Feature_Representation.htm

Be aware that activating this option will slow down the reader a little bit for each returned file.

That is already set and it still does not return anything for current .sr_lock files.

david_r
Rank
Userlevel 4

That is already set and it still does not return anything for current .sr_lock files.

In that case it's probably something linked to the underlying technology and user permissions on that particular network share. You may want to discuss this with your IT department.

Reply


Community Stats

28,731
Posts
109,530
Replies
36,567
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.