Is there any known problem with accessing Long Raw fields over a table synonym in oracle?

Specifically, my entities were generated against one database but are now being used to access data in another database, in this other database there is one table which is just a sysnonym that points to the table in the original database.

Fetching an entity appears to work as expected with no errors, apart from one field that contains no data. This problem field is of type Long Raw.

Everything works fine when connecting to the original database. The only difference (as far as i can tell) is the use of the synonym.

I've tried just a quick oledb test to make sure it's not an oracle problem and the data is fetched fine.

Any ideas?

[edit] i just tried another test using an Oracle.DataAccess connection and it has the same problem, so it must be an oracle driver issue. Back to google...

long raw is a type which is I believe the most problematic type there is. A lot of functionality isn't supported on long raw, if I'm not mistaken.

Otis wrote:

long raw is a type which is I believe the most problematic type there is. A lot of functionality isn't supported on long raw, if I'm not mistaken.

This is true and we've been gradually changing all long types but this one still remains and it seems is likely to remain as a long raw.

Seems strange that it works fine with an oledb connection and not an oracle connection though. I haven't been able to find anything specific documenting problems with long raws & synonyms We can live with it for the time being as it's just an in-house problem, it's unlikely that a client will encounter it, until that happens it's just a "minor inconvenience".