# Toad crash on tables with XMLTYPE

**URL:** <https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781>\
**Category:** Toad for Oracle & DevOps Toolkit\
**Created:** [February 28, 2019, 11:47am UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781 "2019-02-28T11:47:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rustycoder](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rustycoder](https://forums.toadworld.com/u/rustycoder)\
**Post date:** [February 28, 2019, 11:47am UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781/1 "2019-02-28T11:47:28Z")

</div>

When running queries in TOAD on any table with XMLTYPE fields, it fails with error:  
[Error] Execution (1: 1): Access violation at address 0000000180289580 in module ‘oraclient11.dll’. Read of address 0000000000000010

Is there a fix for this, where can I get an updated DLL?

I’m using TOAD 12.12.0.39, on Windows 7.

---

<div class="post-metadata">

**Author:** ![NormTeamT](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/normteamt/32/53_2.png) [@NormTeamT](https://forums.toadworld.com/u/NormTeamT)\
**Post date:** [February 28, 2019, 12:16pm UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781/2 "2019-02-28T12:16:11Z")

</div>

Morning RustyCoder,

the problem has been around for a while and is documented at  
[Problem with XMLType](https://forums.toadworld.com/t/problem-with-xmltype/31140/2) which may or  
may not help.

The problem is in Oracle’s DLL and that hasn’t, or doesn’t appear to  
have been, updated to fix it. ☹

HTH

Cheers,  
Norm. [TeamT]

---

<div class="post-metadata">

**Author:** ![rustycoder](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@rustycoder](https://forums.toadworld.com/u/rustycoder)\
**Post date:** [February 28, 2019, 5:19pm UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781/3 "2019-02-28T17:19:20Z")

</div>

Thanks NormTeamT for letting me know, I’m dumbfounded this was never truly fixed but I guess I’m in a small minority of users.

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [February 28, 2019, 5:24pm UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781/4 "2019-02-28T17:24:38Z")

</div>

You’re not in as much as a minority as you might think.  
I wish we could do something about this other than tell people to cast it as clob (and do that ourselves when we can). It’s front and center on our radar but our hands are tied. ☹

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [March 18, 2019, 3:13pm UTC](https://forums.toadworld.com/t/toad-crash-on-tables-with-xmltype/45781/5 "2019-03-18T15:13:56Z")

</div>

Next beta, if you cast the XMLTYPE to CLOB with either XMLSerialize or GetClobVal, and include the ROWID in your select statement, then you'll be able to edit the data in the popup editor.