Skip to main content
Solved

Geodatabase lock error when uploading to Google Drive

  • November 21, 2020
  • 2 replies
  • 24 views
damian6105
Participant
Forum|alt.badge.img

I'm trying to export feature layers from ArcGIS Online to Geodatabase, then upload the Geodatabase to Google Drive. I'm using a 'Choice with Alias (multiple)' user parameter to select and export one or more feature layers. If I select one feature layer my FME script works fine. If I select more than one layer then I get a geodatabase lock error while uploading the Geodatabase to Google Drive. This is the error message:

 

PermissionError: [Errno 13] Permission denied: 'C:\\\\MyDirectory\\\\MyGeodatabase.gdb\\\\_gdb.JD2344.18360.9116.sr.lock'

Error encountered while calling method `input'

GoogleDrive_Geo_CALLER (PythonFactory): PythonFactory failed to process feature

 

I'm hoping someone can suggest a solution. My FME script is attached.

Regards, Damian

Best answer by hkingsbury

The .lock file indicates that the GDB is open. Could you try putting a featureHolder or Decelerator after your featureWriter to ensure that FME has fully completed writing to the GDB.

 

Also if you have any other applications/processes accessing the GDB you will need to close these.

View original
Did this help you find an answer to your question?

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+53
  • hkingsburyCelebrity
  • Celebrity
  • Best Answer
  • November 22, 2020

The .lock file indicates that the GDB is open. Could you try putting a featureHolder or Decelerator after your featureWriter to ensure that FME has fully completed writing to the GDB.

 

Also if you have any other applications/processes accessing the GDB you will need to close these.

damian6105
Participant
Forum|alt.badge.img
  • damian6105Participant
  • Author
  • Participant
  • November 24, 2020

Thank you for your suggestions @hkingsbury​ , greatly appreciated. I tried the Featureholder but unfortunately I still got the same error. However the Decelerator did work. I guess the only issue is that I sometimes run the script on up to 80 feature layers, which means I have to set a very long delay time for the Decelerator (2 hours maybe). So if I'm only running a couple of feature layers, I still have to wait all that time for the script to run - unless I calculate a clever variable for the delay time.

Regards, Damian

Reply


Helpful Members This Week

Community Stats

31,148
Posts
118,085
Replies
38,768
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.