Customer Portal

Prevent Derby from installing/running

Comments 1

  • Avatar
    admin
    0
    Comment actions Permalink
    Hi Paul,

    Thank you very much for your question. In fact, the Derby instance that you can see in the log file has been initialized for CloverETL Data Profiler.

    This application is maintained independently from the CloverETL Server and a separate database is created for it by default. Even though you are using MySQL DB for CloverETL Server, the CloverETL Profiler is still using the default Derby DB.

    Once neither the Server nor the Profiler uses the Derby DB driver, there is no need to disable the unused Derby database explicitly, the Derby shouldn't start on its own.

    For more information about how to configure Data Profiler DB please see the following page: http://doc.cloveretl.com/documentation/UserGuide/index.jsp?topic=/com.cloveretl.profiler.doc/docs/reporting-console-configuration.html

    I hope the information provided was helpful. Should you have any additional questions, don't hesitate to ask. Have a nice day, Eva

Please sign in to leave a comment.