32k limit on Oracle BLOBs

[350Zed]

Hi,

I'm having problems with Oracle BLOBs using 10g.

On one machine they can be accessed and read fine with no problems. On another machine when they are read they are limited to 32Kb and I cant work out why.

Both machines are using the Oracle in OraClient10_home1 ODBC at version 10.02.00.01 and the ODBC is configured the same on both machines.

If I use a file that is less than 32Kb in size then both machines work fine. It is only larger files that cause the problem.

It is clearly something to do with the setup of the client PCs, but I've been hunting high and low to see if I can find information on configuring BLOBs in the ODBC or on the client PC and cant find anything.

I'm now running out of options and wondered if anyone out there could help.

Thanks in advance.

 

[Thargy]

I don't have a technical fix, but how about trying this...

Get the client PC that works, and use it to read the database that "doesn't work". If it has no problem with the 32K, then the problem clearly is with the client PC.

If the problem is client, and the client can't be readily fixed, why not duplicate the known good PC (using something like Acronis True Image) and get around the problem that way. An exact duplicate of the working machine must also work, right?

I know this isn't an analytic solution, but at least you can get on with the job, whilst researching the problem. If you want to box clever, you might also image the faulty client, and deliberately build a dud box later on, so that you can do lengthy investigations, without impacting on immediate work needs.

Regards

Tharg

Grinding away at things Oracular

 

[350Zed]

Thanks for the response Tharg.

Unfortunately the two client PCs are used by different people in different deparments so in addition to the client app with the problems they have other software on there specific to their jobs so cloning one over the other wasn't an option.

However I have found the problem. It's hidden in the Borland Builder config settings. I didn't realise there was a Borland installation on the PCs, (I'm new here, that's my excuse and I'm sticking to it!!), anyway hidden in the administration settings of the install is a "BLOB SIZE 32" value. Changing this to something more sensible has resolved the issue.

Thanks for the help.