topic Odbc read failed in Progress database in QlikView

Odbc read failed in Progress database

lalitinmbd — Tue, 27 Mar 2012 05:01:27 GMT

Dear All,

I am presently working on progress database and i am facing a problem while extracting the data from db.

When i reload my extraction application at some points in some tables it pops up an error odbc read failed

when i do ok it reloads but some data gets missed. i.e QlikView doesnot pulled all data from db. I have figured

out that there are some fields in those tables due to which this error occurs. when i comment these fields QV

pulls all data from db. I looked into the dump of one table provided by db team and found that the culprit field

has data in it which exceeds the coloumn size. But i cant comment that field as it is required in the reports.

Do any body have any idea how to tackle the situation.

Thanks in Advance.

Regards

Lalit

Odbc read failed in Progress database

rbecher — Tue, 27 Mar 2012 05:42:35 GMT

Hi Lalit,

maybe a left(<fieldname>, <fieldsize>) on this field could help.

- Ralf

Re: Odbc read failed in Progress database

Tue, 27 Mar 2012 07:10:21 GMT

Lalit,

I had the same problem. In my case the problem was the SQL Width.

You can fix this with a tool called dbtool.

Jeroen

Odbc read failed in Progress database

etl_tools — Tue, 27 Mar 2012 08:29:06 GMT

You an increase the limit by tweaking odbc parameters

Mike

http://www.etl-tools.com/

Odbc read failed in Progress database

lalitinmbd — Wed, 28 Mar 2012 07:35:29 GMT

Do i need to tweek the parameters in QlikView?

How to do it?

I am getting the below error while fetching the data.

Error: QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState:S1000, ErrorCode: 4294757284, ErrorMsg: [DataDirect][ODBC Progress OpenEdgeWire Protocol driver][OPENEDGE]Column address-1 in table PUB.address has value exceedingits max length or precision.address << INLBE 1 lines fetched

Thanks in Advance.

Odbc read failed in Progress database

lalitinmbd — Wed, 28 Mar 2012 07:38:19 GMT

How does this db tool actually works???

Odbc read failed in Progress database

Wed, 28 Mar 2012 08:02:32 GMT

You can find more information on dbtool in the Progress Knowledge Base.

http://progresscustomersupport-survey.force.com/OpenEdgeKB/articles/Article/P24496?retURL=%2Fapex%2FKnowledgeSearch&popup=false

Odbc read failed in Progress database

etl_tools — Wed, 28 Mar 2012 08:20:49 GMT

No you need to tweak ODBC driver parameters.

Mike

Odbc read failed in Progress database

lalitinmbd — Wed, 28 Mar 2012 09:17:15 GMT

I have checked the odbc driver settings didn't find the screen u shared.

I am using windows xp. If possible please provide me the steps in snapshots..

Odbc read failed in Progress database

etl_tools — Wed, 28 Mar 2012 09:34:37 GMT

Click datasource than you will see it

Mike

Re: Odbc read failed in Progress database

andries_bos — Wed, 28 Mar 2012 11:41:56 GMT

field length could also be checked (if it is correct) if you try to load your records via excel-odbc: it will fail in the same way.

Please read

http://documentation.progress.com/output/OpenEdge102b/pdfs/dmsdv/dmsdv.pdf

to see how to use the dbtool (we used the option 2) by manual execution on a non regular base. I dit noticed this problem as a rebuild did not show all the records i expected. (record extraction count stayed the same ...)

Using this DBTool will solve your problem! On our 5 GByte Progress database, it took about 5 minutes to complete.

Odbc read failed in Progress database

etl_tools — Wed, 28 Mar 2012 11:56:12 GMT

Lalit

Sorry I've got confused between Progress ODBC and Postgres ODBC.

We did work with Progress as well a while ago

Mike

Odbc read failed in Progress database

lalitinmbd — Wed, 28 Mar 2012 12:13:04 GMT

Its Ok Mike.

I am working on Progress database.

Any suggestions on the same issue would be helpful.

Lalit

Odbc read failed in Progress database

Fri, 30 Mar 2012 05:41:06 GMT

We have Progress OpenEdge installed on a server running Linux.

I have a program that I have scheduled to runs once a week this code:

UNIX SILENT VALUE ('dbtool /users/colontw/db/XCOLONTW < /users/test/jeroeno/dbtoolinput.txt 1> /dev/null 2> /users/test/jeroeno/dbtoollog.txt').

dbtoolinput.txt is filled with the options you want to use for dbtool.

for example:

all

and with 1> and 2> you can redirect the output to an other location than your screen.

Odbc read failed in Progress database

Tue, 22 May 2012 14:22:38 GMT

Has any one solved thisproblem?

Odbc read failed in Progress database

rbecher — Tue, 22 May 2012 14:41:56 GMT

Is this problem also related to a JDBC connection? Maybe this could be a solution..

Odbc read failed in Progress database

etl_tools — Wed, 23 May 2012 13:12:18 GMT

Some ODBC drivers are tricky to work with

If there is a JDBC driver you can try it instead together with Ralph's JDBC connector

or you can try our ETL Tools - Qlik View Connector it works with ODBC as well

Mike

Re: Odbc read failed in Progress database

Fri, 15 Jun 2012 12:48:29 GMT

Character fields in progress are variable length and ignore the SQL width setting in the DB schema (there is a start-up parameter where you can force Progress to adhere to it - can't remember it off the top of my head).

One of the records in your address table (field address-1) has more characters in it than the setting of the SQL width for the field.

Two options:

Update the Progress database schema so the SQL width is > the maximum length of the field, or reduce the text in the offending record.

Do a search on "openedge dbtool" - dbtool is a tool supplied by Progress that can update the SQL width settings for you.

Re: Odbc read failed in Progress database

Emmanuelle__Bustos — Mon, 09 Jun 2014 23:13:38 GMT

Lalit Chaudary

Same problem reading a Progress 10.2B Database:

QVX_UNEXPECTED_END_OF_DATA: SQL##f - SqlState: S1000, ErrorCode: 4294757284, ErrorMsg: [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Column num_factura in table PUB.Docs-x-pagar has value exceeding its max length or precision.

What of all the posts is the correct answer?

Re: Odbc read failed in Progress database

lalitinmbd — Sat, 21 Jun 2014 09:52:35 GMT

Dear Emmanuelle,

In progress DB there is no limitation on the length of the characters that can be inserted in the field. e.g Let's say there is a table A in progress which has below fields

Field Name Field1 Field2 Field3 Field4

Length(CHAR) 100 50 50 29

So in progress db you can enter the data which could be of more length then defined....in such cases the mentioned error come. The way to tackle is to increase the length of the fields in the progress db in which the error is coming so ask the db team to increase the length of the field due to which the error is coming..........

Regards

Lalit