Hi Marco,
Is there any chance to have this patch for 28/mar/06?
Best Regards.

Hi!

We've got the same problem with the TOracelQuery component, though we don't use the rowid column in this case. If we do a select *, we get a access violation in orageneric10.dll, if we select the columns by name everything is fine.

I have not figured out so far, which circumstances are needed for this issue to show up, in some querys it does, in others not. I suspect XMLType-Columns, which we use in some tables.

Maybe this helps in searching.

Is this issue restricted to XMLTYPE columns?

It seems so at the moment, but since we've updatet our clients recently, I can not confirm this at 100%.

We just encountered another Problem resulting in the same Exception while creating a TXMLType instance, but not every time we do it. The same procedure works once, the second time it crashes.

I will try to get some simple scenarios for those issues, as the second problem now is a urgent one for us. If I am successfull with this, I can provide you these scenarios with source.

We had several problems with XMLType columns in 10g R2, we had to step back to 10g R1. Something looks to be changed between those releases, and broke DOA compatibility.

I can provide some more information regarding the issue:

We use Client 10.1.0.2, Servers 10.1.0.4 and 9.2.0.7

on the 9.2.0.7 server, everything seems to be fine.

The exception occurs every time a select on a xmltype column is executed,
but not the first time it is executed in the actual session. The Problem does not occur,
if the table has more than one xmltype column.
This Problem also occurs, if I execute the select with PL/SQL Developer.

It occurs also when a TXMLType-instance is created after one instance was successfully created.
For this Problem, the amount of xmltype columns in the table does not matter.

If I get more information, I'll post it here.

noidic: see my post of March 13th - there is a bug filed in Metaling regarding these issues, but I got no reply here.

I know, this issue was reported by us, but it's another issue regarding only R2 of 10g, not R1. The actual issue shows of in R1.

Hi Marco,

We are talking and talking about this issue since January and no solutions were proposed yet...

So, is there any chance to have this patch for this month? This year? Next milenium?

Please, don't abandon us!

Best Regards.

Hi Marco,

We were supposed that our Annual Service Contract should cover this kind of issue.

We are waiting for a patch since January...and our clients cannot spend more time...they are now bringing us into court!

Is there any change to have your professional help to solve this problem?

Thanks a Lot!

Best Regards.