We have a task that runs objectscript code to load data into a linked external table. After upgrading from 2024.1 to 2025.1, the load is throwing an error, with error code -400, and no error message. The data DOES get loaded into the external table in its entirety, so with no meaningful error message, its hard to determine what the issue is. The result is the same with and without the USING clause, so don't let that confuse you.

I'm trying to use the EnsLib.SQL.Operation.GenericOperation component in a production to read a column from a Redshift table that is set up as VARCHAR(65535) and am getting the following error.  

An error was received : ERROR #5023: Remote Gateway Error: JDBC Gateway getClob(0,1) errorRemote JDBC error: Cannot convert the column of type VARCHAR to requested type long..

The query I'm using is a simple 'SELECT column_name FROM table_name'. I've done a little research and it sounds like Redshift doesn't support getClob().

I've been playing with IntegratedML and have created a model and trained the model.  When I try to use PREDICT or PROBABILITY statements in an SQL query, I get the following error:

[SQLCODE: <-400>:<Fatal error occurred>]

  [%msg: <PREDICT execution error: ERROR #5002: ObjectScript error: <OBJECT DISPATCH>%LoadModel+31^%ML.AutoML.TrainedModel.1 *<class 'AttributeError'>: 'str' object has no attribute 'decode' - >]

Here's an example of the sequence of steps I've followed that lead to the error:

CREATE MODEL MyModel PREDICTING (IsError BOOLEAN) FROM Example3.ModelTable

TRAIN MODEL MyModel AS