Derby.log file size growing too fast. Options to enable log rollover or purge of file
Hi,
We have a Dynatrace profile for Development env in CMIC (Church Mutual Insurance Company, WI). It seems that it is configured to use derby DB as default DB for performance warehouse.
The derby.log file grows to 2 GB in few hours.
There is warehouse clean up task running in "Tasks and Monitors" still the derby.log file is getting filled very quickly and is taking huge diskspace.
We will like to know
a) if there is a config setting by which the derby.log filesize can be controlled, rollover or changed to produce minimal logging ?
b) If there is any harm in purging derby.log file ?
CMIC is still using Dynatrace Ver 4.2 and has Ver 5.5 or 5.0 pending.
Thanks for your help in advance.
Regards
Shahab
CMIC/SpiderLogic
Shahab,
The Derby database is not supported for any "real" use. It is used for demo or training only. It is an in-memory database that is easy to corrupt, and which also takes memory/cycles from the dT server itself.
Best bet for you is to move from Derby to a supported RDBMS. If you don't have access to SQL Server, Oracle, or DB2, you can also download Postgres, which is a free, open-source RDBMS and which is supported by dynaTrace as a Performance Warehouse.
This is your best solution to your problem.
Rob
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
