Select to view content in your preferred language

SQLITE files being created

783
2
08-23-2023 02:37 AM
CiarainSheridan
Emerging Contributor

Have noticed in our Enterprise setup a large number of .sqlite files being created and causing downtime on our portal and apps. We have a script running to clear these down every night but some files being created during the day are over 8gb and a number of these cause issues before the script runs. 

Is there a way to pinpoint the generation of these sqlite files and reduce their impact?

CiarainSheridan_0-1692783417659.png

 

Tags (2)
0 Kudos
2 Replies
ArchitSrivastava
Frequent Contributor

Hello @CiarainSheridan ,

In order to have a better understanding of this, could you please share the following details:

  • What is the version of ArcGIS Enterprise you are working with?
  • What is the location where the files are being created?
  • Is it possible for you share one of these sqllite files for running a check?

There are multiple things where these could be being utilized but would require some troubleshooting.

-Archit

0 Kudos
GeoffreyAplin
Occasional Contributor

Hi from Australia.
We have similar challenges with these large files that only seem to be created for a single feature class best we can tell by looking at a sample of the files containing objectid and what appear to be the definition for a sql where clause.
1. We're on Arcgis enterprise 10.9.1 and was unaware of these files with earlier versions although it may relate to something added since version upgrade
2. Files are C:\Users\{arcgis service account}\AppData\Local\Temp on each arcgis server operating system drive.
3. I can't share a file as the 'where clause' values are sensitive data. Screenshot shows snip with objectid and primarykeyclause columns and valuessqllite-sampledata.png

Our local distributor support indicates theMakeQueryLayer Python function generates these but we can't identify use of this in our code so it remains a mystery.
We do use MakeFeatureLayer in ArcGIS Pro python code but not for this feature class and we're told that it doesn't apply for that function.

So any clues as to what scenario causes arcgis server to generate these would be appreciated as we're trying to identify cause and possible options to prevent their generation and probable performance impacts of this happening.  Are we missing an attribute index for a join operation or similar perhaps? How else could a web application trigger their generation.

Thanks for any insights.

0 Kudos