ESRI & ORACLE PERFORMANCE TUNING
Detection of the Problem
Recently, ESRI’s desktop application, ArcMap, has often started to be slow when many users edit with different computers at the same time. Writing data to the ORACLE database, where we keep spatial data with ArcMap, became quite difficult and annoying. Although we made the necessary follow-ups and investigations on the subject and took some precautions, after a while, the slowness in question came to light again, and although the solutions we applied to solve the problem worked in the short term, the slowness started again over time.
Solution of the Problem
Then, predicting that a step towards a solution can be taken by monitoring the problem of slowness directly through the ORACLE database, we started to examine the performance and logs of the relevant schemas on the database side when slowness occurred. When the warning messages received during the time of the slowdown were examined, it was seen that it would be beneficial to increase the cash size (cache size) of the SDE_LOGFILE_LID_GEN sequences (sequence object used in ORACLE) that occurred during the intensive insert (data entry) process. Thereupon, the default cash size value for the relevant SDE_LOGFILE_LID_GEN created on the database by ESRI’s SDE (Spatial Database Engine) was increased from 20 to 10000.
Result
Thus, it seems that the problem experienced by the users during the intensive insertion (data entry) operations with ArcMap has been solved for now.
If you are using ESRI as the GIS platform and ORACLE as the spatial database in your business, it would be beneficial to increase the default cash size value for the SDE_LOGFILE_LID_GEN in question.
Note: I would like to thank the Survey Engineer Hüseyin Cem İNCE and Güneş EROL from the VERIDATA team for their efforts and support regarding the determination and solution of the problem.
