Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

That said, as John pointed out, these are SMALL tables which should let you query them from any CSDK version, even Windows 32bit. Try John's debugging ideas.

Art

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

It seems that the position of the ROWID in the query influences

cmd.CommandText = String.Format(@" SELECT benefis.ROWID,ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

works without problems,change the ROWID from the end to the beginning of the query

That said, as John pointed out, these are SMALL tables which should let you query them from any CSDK version, even Windows 32bit. Try John's debugging ideas.

Art

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Hello,

I wonder about the motivation to get large tables by default in V15...

onconfig

    TABLE_SIZE    SMALL

should be the default, so that existing apps using 32bit rowids are not broken.

I guess it's to late now to change the server defaults.

Maybe this could be addressed with a question during the installation?

Seb

It seems that the position of the ROWID in the query influences

cmd.CommandText = String.Format(@" SELECT benefis.ROWID,ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

works without problems,change the ROWID from the end to the beginning of the query

That said, as John pointed out, these are SMALL tables which should let you query them from any CSDK version, even Windows 32bit. Try John's debugging ideas.

Art

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Sebastian:

If you upgrade an existing instance to v15.0 it starts in "compatibilty mode" which does not even support LARGE tables at all. Once you migrate the instance to the expanded mode you can certainly set TABLE_SIZE to SMALL yourself. Only when you install a new instance does v15.0 start in its expanded mode with LARGE table support. Personally I think that is a good compromise.

Art

Hello,

I wonder about the motivation to get large tables by default in V15...

onconfig

    TABLE_SIZE    SMALL

should be the default, so that existing apps using 32bit rowids are not broken.

I guess it's to late now to change the server defaults.

Maybe this could be addressed with a question during the installation?

Seb

It seems that the position of the ROWID in the query influences

cmd.CommandText = String.Format(@" SELECT benefis.ROWID,ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

works without problems,change the ROWID from the end to the beginning of the query

That said, as John pointed out, these are SMALL tables which should let you query them from any CSDK version, even Windows 32bit. Try John's debugging ideas.

Art

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

It seems that the position of the ROWID in the query influences

cmd.CommandText = String.Format(@" SELECT benefis.ROWID,ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

works without problems,change the ROWID from the end to the beginning of the query

That said, as John pointed out, these are SMALL tables which should let you query them from any CSDK version, even Windows 32bit. Try John's debugging ideas.

Art

Eduardo:

As far as I know, 32bit clients are no longer supported! There is no 32bit Windows CSDK any longer. You will have to use the 64bit CSDK.

Art

hello John Lengyel 

I ran the instructions and got the following

> select *, hex(rowid) from tab1;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

> select *, hex(rowid) from tab2;

         c1 c2                   (expression)

          1 fff                  0x0000000000000101
          2 fff                  0x0000000000000102

2 row(s) retrieved.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1; does not return any results

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0; returns my tables

It is worth mentioning that I am working with programs compiled for 32-bit C++ and C#. I searched FixCentral but I cannot find the V15 client for 32-bit.

I'm concerned the large/small table theory may be off, because removing rowid from the query wouldn't lead to correct results in that case.

Eduardo, you can determine for certain which tables are large with the following SQL:

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 1;

That will return the names of all tables in your current database that are large.

select tabname from systables where sysmaster:bitval_bigint(flags, '0x4000') = 0;

That will return the names of all tables in your current database that are small.

I'm assuming all tables in your query are small, in which case no client should have trouble accessing them, selecting rowids from them, etc. If any tables in your query are large, it should return error -21569 whether you select rowid or not.

As an experiment would it be possible to use only the latest V15 client libraries when compiling your test program, to see if that gives you different behavior? As I said, you should get sane behavior even when using older client libraries: the query should either work properly or if any tables are large it should return an error.

If all else fails it might be helpful to use SQLIDEBUG, to see the client/server conversation in detail.

Eduardo:

I agree with Hedwig, the problem is that the benefis table is likely a LARGE table and you have compiled the application with CSDK v4.10 which has no way to process a 64bit ROWID. Likely in the code it is not checking for errors (or maybe it only checks for specific errors, so it is hung in a FETCH that cannot return or something similar.

I don't know for sure because the dbschema output you posted was not made with the "-ss" option so it does not show whether the tables are LARGE or SMALL, unless they were created LARGE by default.

Bottom line, as already mentioned, you can only access LARGE tables with code that was compiled with the latest v15.00 CSDK.

Art

Eduardo:

And are the tables (benefis, entidades, & municipios) all SMALL tables or LARGE tables or a mixture? Especially the benefis table? What does the dbschema -ss output for that table look like?

Art

Hello Art Kagel

I mean, when I include the ROWID from my query in C#, I run the debug, but the program stops responding and doesn't send any errors. I monitor my session ID and get the following:
    tid     name       rstcb      flags             curstk status
11708 sqlexec 5755c4b8 Y--P--- 3856 cond wait netnorm -
C# when filling the datatable it freezes: cmd.CommandText = String.Format(@" SELECT ben_benef,
ben_pater,
ben_porcen,
ben_fecha,
ben_entfed,
ent_nombre,
ben_municiO,
mun_nombre,
ben_coloni,
ben_codpos,
benefis.ROWID
FROM benefis,entidades,municipios WHERE
ben_socio = ? AND ben_entfed = ent_number AND mun_entfed = ben_entfed 
AND ben_munici = mun_numero ORDER BY ben_fecha DESC"); 
cmd.Parameters.Clear(); 
cmd.Parameters.Add(new OdbcParameter("@partner", PartnerNum)); 
dadap.SelectCommand = cmd; 
dadap.Fill(Beneficiaries);

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks

Hello everyone

Recently, as you may know, version 15 of IDS was released. I was running some tests, and among the issues that arose was the use of the ROWID by clients, especially from C# and/or ODBC. It turns out that when I include the line in the SELECT statement, it doesn't seem to respond; otherwise, I remove the line and it works correctly. It's worth mentioning that the ROWID isn't the best practice, but several of my programs depend on it.
Informix SDK 4.10. C16W
IDS: 15.0.0.0WE with the parameter: TABLE_SIZE SMALL

Thanks