The JADE 2022 release meets tomorrow’s business demands.
Currently, the RPS log doesn't provide details when a datapump is halted due to SQL error. All we see is something like this:
RDB ODBC Error: Update object;Sql execute - tranId: 130137982; oid: [2242.16291:19]
rps: Sql: {? = call jadeAccountUpdate (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) }
rps: RPS Target Relational DB - SQL operation failed
It would be helpful to log the actual SQL script being run and what is failing rather than bunch of "?". Currently, we have to guess at which field is failing on this particular oid.
Thaban Segaran
What does the log say in these examples? Does it give the actual values?
As of right now, there is helpful RPS logging just like what you want in 7109, any 2018 service pack that might come out, and JADE 2020. In this case, there is no actual sql script as such, this is a stored procedure, and that is the literal sql syntax being executed: (https://docs.microsoft.com/en-us/sql/relational-databases/native-client-odbc-how-to/running-stored-procedures-call-stored-procedures?view=sql-server-ver15). In those versions I mentioned, there is also the ability to take a diagnostic process dump right at the point of failure so we can quickly and easily work that out. Off the top of my head I can't verify it, but there is usually the ODBC error code returned as well, which you can google to give you some hints.