Quering a table with xmltype columns gives an Access Violation

[Roeland]

When I query a table with xmltype columns and the recordcount reaches 100 I get an Access Violation and I have to kill PL/SQL Dev.

I could reproduce this consistently.

Roeland

PL/SQL Developer 9.0.0.1607

 

[Marco Kalter]

This is a known problem that we are looking into. We do not yet have a solution.

 

[T-Gergely]

"Real solutions for Oracle developers"
So when can we expect THAT solution?

 

[Roeland]

Do you still have an issue with this?
Are you using the latest version?

I'm using version 9.0.1.1620 now and haven't stumbled on this bug anymore.

Roeland

 

[T-Gergely]

Yeah, still have this bug.

PL/SQL Developer
Version 9.0.2.1621
Windows XP Professional 5.1 Build 2600 (Szervizcsomag 3)

Preferences
Session mode: Multi
OCI Library: C:\orant\home11g-instant\oci.dll
Use OCI7: False
Allow Multiple Connections: False

DLL: C:\orant\home11g-instant\oci.dll
OCI: version 11.1
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0

Character Sets
Character size: 1 byte(s)
CharSetID: 32
NCharSetID: 871
Unicode Support: True
NLS_LANG: AMERICAN_AMERICA.EE8ISO8859P2
NLS_CHARACTERSET: EE8ISO8859P2
NLS_NCHAR_CHARACTERSET: UTF8

 

[T-Gergely]

Version 9.0.6.1661 still has this bug.

 

[T-Gergely]

Yoohoo! Version 9.0.6.1665 still has this bug.

 

[T-Gergely]

This is a known problem that we are looking into. We do not yet have a solution.

Dear Marco!

Can you tell me why this is so difficult to solve?
It's very easy to reproduce this bug. You only have to select 100 rows.
Your program ask OCI_ATTR_ROW_COUNT with OCIAttrGet. When that function returns 100, it calls OCIObjectFree (presumably, with invalid parameters; the call is at offset 0x0057acee for version 9.0.6.166) and crashes.

 

[Roeland]

Hi T_Gergely,

What is your client version? I think that my errors vanished when upgrading my client version from 11.1 to 11.2.

Marco,

What I notice is that the Query waits several seconds after reaching multiples of 100 and then resumes the operation. If this could be improved, that would be fine!

Settings:

Using
Home: OraClient11g_home1
DLL: D:\Oracle\product\11.2.0\client\bin\oci.dll
OCI: version 11.1
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0

Character Sets
Character size: 4 byte(s)
CharSetID: 873
NCharSetID: 2000
Unicode Support: True
NLS_LANG: DUTCH_BELGIUM.AL32UTF8
NLS_CHARACTERSET: AL32UTF8
NLS_NCHAR_CHARACTERSET: AL16UTF16

PL/SQL Developer 9.0.6.1665

 

[T-Gergely]

Hello Roeland,

"Using
Home: HOME11
DLL: c:\orant\home11g-instant\oci.dll
OCI: version 11.1
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0

Character Sets
Character size: 1 byte(s)
CharSetID: 32
NCharSetID: 871
Unicode Support: True
NLS_LANG: AMERICAN_AMERICA.EE8ISO8859P2
NLS_CHARACTERSET: EE8ISO8859P2
NLS_NCHAR_CHARACTERSET: UTF8"

My tables have multiple xmltype columns. If I select only one column, PD may not crash. But the waits you noticed might be due to the same bug. Having the source code of PD, it would be very easy to find that OCIObjectFree call I'd mentioned - I don't know why they ignore this bug.

 

[T-Gergely]

The correct version number is 9.0.6.1665 for my post where I found the OCIObjectFree call at offset 0x0057acee.

 

[T-Gergely]

Hello Marco,

If we pay for a 5 user Annual Service Contract, will you please fix Xmltype handling NOW?

On my new PC, it got still worse.

Instead of the results I get .
Then PD freezes and even killing the task is quite difficult.

PL/SQL Developer
Version 9.0.6.1665
Windows 7 (64-bit) 6.1 Build 7601 (Service Pack 1)

Physical memory : 4