PB2019R3 - SQLSTATE S1010 - Function Sequence error

Resolved PB2019R3 - SQLSTATE S1010 - Function Sequence error

Issue

Votes

Undo

Pietro Guglielmo
PowerBuilder
Thursday, 21 October 2021 09:11 AM UTC

Hi all, 
we are running migration and compatibility tests from power builder version 9 to 2019 version of a 2-tier application developed 15 years ago.
The application was developed in PB 9.0.1 Build 6533.
We are now testing the same application under PB 2019 R3 build 2728.
Here is the problem, a database query is performed from a datawindow. The query works fine in PB9 but
the same query raises the following error in PB2019R3 "Select Error: SQLSTATE = S1010
[Microsoft] [ODBC Driver Manager] Error in function sequence. "
The application retrieves only a part of the records, on PB9 it retrieves 165 records without errors while on PB2019 it retrieves 140 records raising the error.
Soon after, whatever action is performed on the application causes it to crash.
We are using an ODBC 32-bit connection (in a 64 bit environment) to IBM DB2 database DB2 v11.1.0.1527. 
The odbc driver number is : "DB2 v11.1.0.1527 - 11.01.00.1527 - DB2CLI.DLL 10/06/2016".
We do not know if the problem occurs on other datawindows, because we should check them all to know.
Everything works fine on others DW but on this one it doesn't.
Any idea on the this problem?
Thanks, 
P.

Responses (5)

Pietro Guglielmo Accepted Answer Pending Moderation

Friday, 22 October 2021 13:57 PM UTC
PowerBuilder
# 1

We found the problem,

a particular column of the select was constructed with a series of concatenations between string fields.
"SELECT ....,
coalesce(column1, ' ') ||'/'|| coalesce(column2,' ')||'/'|| coalesce(column3,' ')||'/'||
coalesce(column4, ' ')||'/'||coalesce(column5, ' ')||'/'|| .... etc AS COMPUTED_STRING"
We used DB2 operator "|| ( double pipe ) " which corresponds to the CONCAT function.
By removing this calculated column everything went well.
We haven't tried replacing the || with the CONCAT function yet, but I think the problem is related to this particular operator. It may not be handled correctly by the ODBC driver.
I suppose we should modify the select with a series of :
SELECT CONCAT(CONCAT('colmun1',' '),'column2') AS COMPUTED_STRING
FROM SYSIBM.SYSDUMMY1;
Alternatively we can concatenate the columns via PB script

Comment

Pietro Guglielmo
Friday, 22 October 2021 14:07 PM UTC

However, I don't explain why in PB 9 everything worked while in PB2019 it didn't.

(the ODBC driver is the same)

Also, why does the select work from ISQL while it raises the error from the data window?

(I believe ISQL connects via ODBC)

Helpful 0