expected 'sys_id', found 'priority' in first column of table 'incident' about sndml3 HOT 11 CLOSED

It should be in either src/main/resources or src/test/resources.
This page might help: https://github.com/gflewis/sndml3/wiki/Log4j2

from sndml3.

Same is the case for sync as well. I can confirm the table is present and has sys_id as first column in target MSSQL database.

from sndml3.

This is strange. SNDML must be having difficulty reading the table schema. My recommendation is to modify the log4j configuration file and set the threshold level to "trace". This should cause SNDML to dump the table schema as it is processed.

SNDML will put sys_id in the first column when it creates the table. There must always be a sys_id column. However, to the best of my recollection, there is no real reason (other than the code that is aborting) that sys_id has to be in the first column. If the schema is read correctly, but the columns are in the wrong order, then you could try commenting out lines 65 through 69 of ColumnDefinitions.java. Then rebuild the package, and see if it works.

from sndml3.

Thanks @gflewis looking at the error, it seems like SNDML is able to read the schema ( observe it says PRIORITY is the first column or contract and its first column in below case) but the column order is not correct.

Exception in thread "DPRUN0001012" java.lang.RuntimeException: expected 'sys_id', found 'contract' in first column of table 'customerservice_case'
at sndml.datamart.ColumnDefinitions.(ColumnDefinitions.java:67)
at sndml.datamart.DatabaseTableWriter.open(DatabaseTableWriter.java:51)

where is the configuration file for log4j, sorry I can't find it

from sndml3.

Here is another thought: I see that we are using mssql-jdbc version 8.2.2 (pom.xml line 122). I wonder if this issue would be fixed by upgrading the JDBC driver to 8.4.1?

from sndml3.

Here is an issue with a column order in the 8.2.2 driver:
microsoft/mssql-jdbc#1332

from sndml3.

I would try upgrading the JDBC driver first. I think it looks like our issue. Do you have Maven installed, such that you can rebuild the JAR and see if it fixes the problem?

from sndml3.

sorry I do not have. facing issues to rebuild the package after changing the version to 8.4.1.jre8.

can you please point me to instructions to rebuild

from sndml3.

First you need to install Apache Maven. If you are on a Mac, then I recommend you install it using HomeBrew. If you are on Windows or Linux then you may want to Google "install maven".

Then you go into the directory where you have cloned the repo. The file pom.xml should be in that directory. Then type this command:

mvn package

This should cause it to download all the necessary libraries and rebuild the JAR files in the target directory.

from sndml3.

Thank you @gflewis after updating the jdbc driver, the column sys_id issue is gone. Thank you so much for unblocking me.

from sndml3.

Thank you @jonathangull for identifying this issue and testing the fix.
mssql-jdbc has been upgraded to 8.4.1 in v3.4.5

from sndml3.