DataMart FAQs and Troubleshooting Version 7.0.55 and Earlier

My DataMart keeps freezing—how do I resolve this issue?

Ask your IT team to increase your available memory on your DataMart machine. We recommend at least 21 GB of memory. See the Out of Memory troubleshooting section below for more details.

Would SQL Server 2008 Express version work for the DB?

Yes. All 64-bit versions of SQL server between 2008 R2 and 2019 will work.

Windows OS (64-bit required): Can this be Windows server 2008?

Any relatively recent version of Windows will work—including windows 2008—as long as it is 64bit.

10 GB free disk space: will 100 GB be sufficient? How many disk partitions would be required?

DataMart only uses the disk partition on which it is installed, which should have at least 10 GB of free space.

Microsoft SQL Server 2005 / 2008 R2 / 2012 (64-bit versions) (SQL Server 2014 is not supported): should this be standard or enterprise edition?

Either version will work (standard/enterprise).

Two separate installation instances: a production and a test environment for troubleshooting methodologies - Do we need two separate servers for this?

It is recommended they be separate servers because running two instances on the same server will not work due to port conflicts.

DataMart Servers Daily Restart

The DataMart Server is restarted daily at 11:45 am CT. If the DataMart is running during the time of the restart, it will automatically resume its activity after reconnecting to the server.

Is the https://dm.lucernex.com address I see in the screen shots valid? I need something to use for the firewall request. The firewall request will ask for a specific port. What port is this using?

Yes, that is the URL (https://dm.lucernex.com) DataMart will use to fetch data from the Lx Cloud application. Requests are via http to our RESTful web service.

Can I get some more detail around the connection and the transformation of data? Ex. Is it using some type of Web Service, DTS, SSIS, etc? Will our servers be making the request of Lx servers then Lx servers sending us packets?

The DataMart application is a simple web server (using Jetty) that connects (via jdbc) to a local database and also (via http) to the Lx Cloud application. This application has a simple UI for configuration of the database connection and the Lx Cloud authentication as well as viewing the synchronization status. When configured to do so—or when initially configured—the application will fetch the schema from the Lx Cloud application and create those tables and columns in the local database.

Following this, the DataMart application will fetch the corresponding data and populate the local database tables. On a periodic basis the DataMart application will fetch all changes from the last successful fetch and populate that data into the local database to keep the local database in sync with the data in the Lx Cloud application. Note all of the requests are made via RESTful queries to the Lx Cloud application and the local database is updated using jdbc (via a hibernate ORM mapping layer).

Is SA access to SQL required or can it be SQL authentication? If the latter, what access is required?

It can be either SA Access or SQL authentication, but the user must be a database owner.

How can I view my job runs?

You can view your DataMart job runs through the Lucernex application by navigating to Admin > Job Log and searching for the name of your user (usually 'DataMart') that matches the IWMS User Name in your DataMart mapping page. It will show you a historical view of the DataMart files you have run.

Why are "-final" XML files being downloaded in the Execution Events table?

After each record type is imported, Datamart compares the imported Database Record count with the IWMS Record count. If the number of records is the same in both, DataMart will proceed to the next record type. If the number of records is different, Datamart will attempt to import the missing records from the IWMS. This results in the "-final" XML file being downloaded by DataMart.

I am getting an error "Failed Mapping Run. Data Errors Encountered." What are these and how do I correct them?

DataMart looks for valid XML formats as it runs. Due to keying errors in the UI or invalid characters introduced caused by migration of data from a previous database, there may be errors that the DataMart determines cannot be processed.

DataMart must have a successful full run before it can go into Delta mode. It is important to identify and correct these errors within the UI, otherwise, you will find that DataMart will not be able to go into a Delta—changes only—mode, thereby lengthening the amount of time it runs each day as it tries to rebuild the schema and database. On the DataMart Dashboard, there is typically an XML link on each error created on the Dashboard. Review each of these errors, and correct them in your UI. Work with your Lucernex representative if you need further assistance.

Authentication Errors

When the DataMart mapping is set up, it validates the path and login for the source and database targets. An authentication error indicates that one or more of the paths in your DataMart mapping are not valid (or no longer valid). To troubleshoot, open a browser on the server where the DataMart is running, and type in the IWMS Source URL shown in the DataMart mapping, using the same User ID and Password. If it is not successful, it may indicate that your user ID and / or password are expired or otherwise disabled. The DataMart mapping must contain a valid Lucernex user ID and password for the URL environment being used.

"OutOfMemory" Errors

The amount of memory that is allocated to the JAVA HEAP (memory) for use by DataMart needs to be adjusted to accommodate a larger database. To adjust the allocated JAVA memory value, edit the following file:

C:\Program Files\Lucernex\Datamart\bat\datamart.bat

Look for the setting:

set datamart_java_options=-Xmx14g -XX:PermSize=100m -XX:MaxPermSize=500m -Djava.net.preferIPv4Stack=true -DPORT=8080

The -Xmx4g data element specifies the maximum memory that the DataMart is permitted to use. The recommendation is to increase this value to a MAX value of 50% of physical system RAM. After the change is saved, please restart the "Lucernex" service in Windows Services consoles.

SELECT * FROM my_table

I received the "GC overhead limit exceeded" error. What do I need to do to resolve it?

You need to confirm your available memory. There needs to be enough available memory—NOT just total installed memory—on the machine for your record set.

Failed DataMart Mapping Execution — CONNECTION_FAILED error

This error is typically a connection or user account error. We recommend opening a browser on the DataMart server and connecting to the DataMart URL using the DataMart User and Password to verify that the connection and user credentials are valid.