Errors Processing Space

Hello all, turning to the folks here to see if I can get some guidance.

Starting on Sunday, 3/12 we've started having the daily publishing job fail for our main production space. According the errors in the log, below, its pointing to an invalid column name. However that field/column has not been changed. I have opened a ticket with support, but the suggested solution is to delete and reload. I have a feeling deleting and reloading is just going to reload the same error.

Here are the steps in the log where it fails (from earlier today)

023-03-16 10:24:45,303-0500 ERROR - SQLException during LoadWarehouse load method com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'ICSL$vendno$'.
2023-03-16 10:24:45,319-0500 INFO - Logging step LoadWarehouse [ACORN] for processingGroup [Sales] for iteration 2075, status Failed
2023-03-16 10:24:45,319-0500 ERROR - java.sql.SQLException: SQLException during LoadWarehouse load method java.sql.SQLException: SQLException during LoadWarehouse load method

Is there anything else that can be reviewed? I've never seen this error before, our production space has essentially been down for 3 days, and I'm looking for a path forward.

Thanks

Find more posts tagged with

Birst - General Discussions

Comments

Diane McElhiney

@matthew-bagshaw

Have you traced through from the Modeler/Connect connection and the QBO (viewing in Preview) through validating Scripted Source to publish the extract and other references? Something does have to change for this occurrence. Please start with the connection and QBO.

unknown

We got this same error several times before and it turned out some column type got changed to "None", I would suggest to start checking all the columns type and see if anything got changed.

You also might want to delete the data from the source and import it again and see if any column type changed to "None".

If the import is set to Auto then Birst will define the column type based on the values in the first 1000 rows if there is no data Birst will automatically set it to "None" even though there might be data in the column but not in the first 1000 records evaluated by Birst.

In some scenarios we had to change the setting "Source Data Change Behavior" to Locked to preserve the data type for changing.

We had another situation that couldn't be resolved till we deleted the data from the source completely and then delete the source and bring it back again and import and it got resolved.

Hopefully any of these suggestions can help you resolve your issue.

Diane McElhiney

@ahmed-tahaelsaie

Good direction. I'm directly corresponding with @matthew-bagshaw as in this circumstance is more detailed and unfortunately doesn't fit with your description. The data type and length are confirmed stated. The data extract is through our REST API and not a SQL Database connection. Still working through the details.

Copyright © 2025 Infor. All rights reserved.