Enabling additional logging for Analyze reports helps capture the SQL queries that Analyze runs against the BDNA_PUBLISH database. This allows the queries to be executed directly on the BDNA_PUBLISH database for validation or troubleshooting purposes.
- On the User Console server, open File Explorer and navigate to
'...\BDNA\User Console\Tools\Tomcat\webapps\bdna\WEB-INF\classes'. - Open the file Log4j2.xml in a text editor (e.g., Notepad, Notepad++, etc.).
- Look for the sections containing SQLLOG, and uncomment them by removing
<!--and-->.
Original:
After uncommenting:</RollingFile> <!--<RollingFile name="SQLLOG" fileName="${basePath}/mondrian_sql.log" filePattern="${basePath}/mondrian_sql.%d{yyyy-MM-dd}-%i"> <PatternLayout pattern="${LOG_PATTERN}"/> <Policies> <TimeBasedTriggeringPolicy interval="1" modulate="true" /> </Policies> <DefaultRolloverStrategy max="1"/> </RollingFile> -->
Original:</RollingFile> <RollingFile name="SQLLOG" fileName="${basePath}/mondrian_sql.log" filePattern="${basePath}/mondrian_sql.%d{yyyy-MM-dd}-%i"> <PatternLayout pattern="${LOG_PATTERN}"/> <Policies> <TimeBasedTriggeringPolicy interval="1" modulate="true" /> </Policies> <DefaultRolloverStrategy max="1"/> </RollingFile>
After uncommenting:</Logger> <!--<Logger name="mondrian.sql" level="DEBUG"> <appender-ref ref="SQLLOG"/> </Logger>--></Logger> <Logger name="mondrian.sql" level="DEBUG"> <appender-ref ref="SQLLOG"/> </Logger> - Save the changes made to the file.
- Restart the Flexera User Console Service for the changes to take effect.
- After the service restarts, open the User Console application, create a simple report, and wait for the results to populate.
- Using File Explorer, navigate to
'...\BDNA\User Console\Logs'. You should now see a new log file named mondrian_sql.log. - Open the log file and scroll to the bottom to find the latest SQL query executed. Use this query to run against the database directly.
NOTE: If the log file does not appear, restart the machine and try again. After gathering the necessary queries, consider commenting out the section in step 3 to disable extra logging. The log file can grow significantly, so you may want to disable the option or manually clear the mondrian_sql.log file periodically.
Related Articles
Enable debug level logging for Flexera Kubernetes Inventory Agent 46Number of Views Enable Debug Logging for Code Insight or Compliance Library Installer Issues 5Number of Views Clean old data from Analyze Reports 29Number of Views Enable debugging mode in Snow Inventory Oracle Scanner 65Number of Views Enable logging for a running SVM Daemon 36Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago