Errors with UniDac, Oracle 8.0.5 and Memo-Fields

invent · Post by **invent** » Mon 11 Apr 2011 20:41

Hi,

I just updated UniDac from Version 3.50.0.13 to 3.60.0.16 (Delphi 7 Ent, Oracle 8.0.5, Sql-Server 2008 RC2, Interbase XE).

After that, I have massive problems with Memo-Fields. Here is an example-table:

create table ARTIKELBESCHREIBUNGEN (
ARTIKELID varchar2(15) not null,
BESCHREIBUNG long)

ARTIKELID is Primary Key.

When I read in tables like this, sometimes i get many different errors:

- Net: Unknown Error 1.
- Execption EUniError
- The program hangs
- The program stops
- The DBMonitor shows different ORA-xxxx errors, but sometime the error-number does not exists.
- and much more

I tried to find some rules, when this happens, but I cannot find them. I can reproduce this error in the existing tables, but I cannot give you a code, how to create records with this error. There a no special characters in the Memo-Fields. Some of the datasets are in the database since many years.

I only can tell you this:

No errors with UniDAC 3.60.0.16 and MS Sql-Server.
No errors with UniDAC 3.60.0.16 and Interbase XE.
No errors with UniDAC 3.60.0.16 and Oracle 8.0.5 in Client-Mode.
BIG ERRORS with UniDAC 3.60.0.16 and Oracle 8.0.5 in Direct-Mode.
But no errors with UniDAC 3.50.0.13 and Oracle 8.0.5 in Direct-Mode.

Maybe you can find out, what's the difference betweeen 3.50.0.13 and 3.60.0.16 in Oracle Direct-Mode and perhaps you can find an error.

It's not easy for me to go back to UniDAC 3.50.0.13, so I hope for a fast fix.

Thanks in advance and kind regards,
Gerd Brinkmann
invent GmbH

AlexP · Post by **AlexP** » Tue 12 Apr 2011 08:37

Hello,

I cannot reproduce the problem you've specified
Please provide the script to fill a table, and I will try to reproduce this problem again

Also we had similar problems, and we've already fixed them.
These fixes will be included in the next build.
The next build will be available next week.

invent · Post by **invent** » Tue 12 Apr 2011 09:08

Hi,

I told you, that I can't give you some code to reproduce this error. There is no difference between "wrong" records and "correct" records. The ony fact is, that UniDAC 3.60.0.16 (in Direct-Mode) cannot read this datasets, but UniDAC 3.50.0.13 have no problems. And it only happens in Tables with memofields.

Is ist helpful to send some screenshots from DBMonitor? DBMonitor shows always an error.

Kind regards,
Gerd Brinkmann
invent GmbH

AlexP · Post by **AlexP** » Thu 14 Apr 2011 10:48

Hello,

You can send your screenshots to alexp*devart*com.
But it would be better if you could send a script to fill a table.