DBEnvironmentProperties in ‘serverconfig.ini’ of AIMS 2013

By Partha Sarkar

If you have installed AIMS 2013, it's worth taking a look into the 'Server Configuration File' (serverconfig.ini) and you will see a new section "DBEnvironmentProperties" added to 2013 release. Let me copy the relevant section as-it-is from the 2013 release of ‘serverconfig.ini’ –

[DBEnvironmentProperties]

****************************************************************

DB ENVIRONMENT

This section is to set DB Environment.

Determine the best sizes to improve the Server performance.

Property Name                    Description

—————————————————————————–

LibraryCacheSize                 The size for library cache size in MB

SessionCacheSize                 The size for session cache size in MB

DBPageSize                       The size for library DB page in KB

DBXMLPageSize                    The size for library DBXML page in KB

LibraryLogBufferSize             The size for library log buffer in MB

SessionLogBufferSize             The size for session log buffer in MB

DBMaxTransactions                The max number of DB transactions

SessionDBPageSize                The size for session DB page in KB

SessionDBXMLPageSize             The size for session DBXML page in KB

DBTimeout                        The time out for lock and transaction in second

DBMaxLockers                     The max number of DB lockers

***************************************************************

LibraryCacheSize                       = 32

SessionCacheSize                      = 2

DBPageSize                                = 32

DBXMLPageSize                         = 32

LibraryLogBufferSize                 = 12

SessionLogBufferSize               = 1

DBMaxTransactions                  = 1000

SessionDBPageSize                  = 2

SessionDBXMLPageSize           = 0.5

DBTimeout                                 = 0.2

DBMaxLockers                          = 1000 

#***************************************************************

If you have encountered an error message / exception like this – 'DB_LOG_BUFFER_FULL :In-memory log buffer is full' while uploading large package (mgp files) in 2012 or earlier release of MapGuide Enterprise, you could try changing the values of DBMaxLockers and DBMaxTransactions. Increasing the default values of these variables might help to resolve that exception in your setup.

These new set of variables are from Berkley DB settings. In 'serverconfig.ini' (AIMS 2013) you will see a default value is assigned to them. These default values do not suggest any minimum / maximum range as every situation / configuration will be unique to your requirement and environment. You should try changing them and setting values what is appropriate in your setup / environment for your application. I would suggest you to keep a copy of 'serverconfig.ini' before you start changing the values in it.  And, rememeber to restart the service to make the changes effective.


Comments

4 responses to “DBEnvironmentProperties in ‘serverconfig.ini’ of AIMS 2013”

  1. I’m working with MG2011 and i don’t see any DBMaxLockers and DBMaxTransactions variable in my serverconfig file.
    How can we solve this issue. I’m encountering this log message since i have a big number of layers in my map (300). Thanks for your help

  2. Hi Ludovic,
    DBMaxLockers and DBMaxTransactions are new in AIMS 2013. You could try using AIMS 2013 and set the appropriate values for these and see if it helps in your dataset / project.
    Thanks,
    Partha

  3. Hi Partha
    I have tried, but error is same, can you please specifically tell me which parameter i need to configure, my problem is that i have 20000 points coming from db. when i try to select the all points at once, it gives me DB_LOG_MEMORY_BUFFER FULL.
    PLEASE ADVICE WHICH parameter i need to reconfigure
    thanks

  4. Hi Mobin,
    Please see the list of the variable and what they are related to from the above blog post. You might have to play around with them to see what gives you best result. It’s difficult for me to pin-point the variable / value which will fix the issue in your set-up, sorry.
    Thanks,
    Partha
    ADN

Leave a Reply