Access violation at address 000007FEC897C8BA in module 'oraclient12.dll'. Read of address 0000000000000010

I am a long-time user of TOAD and love the tool very much.

Today it is giving me an issue - I am running TOAD 12.12.0.39 64-bit on my work windows laptop. Everything is working great except for querying against a particular table in a particular database.

The database is 11.2.0.3 (I know, ancient). The query is a simple select against this table below which does have one atypical column - that XMLTYPE.

SQL> desc rgdh.assay_detail
Name Null? Type


ASSAY_ID NOT NULL NUMBER(10)
ABBREVIATED_SUMMARY VARCHAR2(2000 CHAR)
FULL_SUMMARY VARCHAR2(4000 CHAR)
INFO_XML XMLTYPE STORAGE BINARY

As soon as I execute anything like

select* from rgdh.assay_detail;

or

select * from rgdh.assay_detail where assay_id = 40751;

TOAD throws the access violation and hangs.

I can do the query fine in SQL+ on the host server.

If I list the columns in TOAD, it works. It only fails on the select *. Weird, eh?

I see other similar issues where the suggestion is to load a newer oracle client (I’m running a 12c client, so I don’t think that’s the problem) or recreate my toad.ini (everything else works fine, so seems unlikely that is corrupted.

Suggestions welcome. Thanks.

-Lisa

That is a known issue with TOAD...

On Thu, Mar 22, 2018 at 12:23 PM, ltansey bounce-ltansey@toadworld.com wrote:

Access violation at address 000007FEC897C8BA in module 'oraclient12.dll'. Read of address 0000000000000010

Thread created by ltansey
I am a long-time user of TOAD and love the tool very much.

Today it is giving me an issue - I am running TOAD 12.12.0.39 64-bit on my work windows laptop. Everything is working great except for querying against a particular table in a particular database.

The database is 11.2.0.3 (I know, ancient). The query is a simple select against this table below which does have one atypical column n- that XMLTYPE.

SQL> desc rgdh.assay_detail
Name Null? Type


ASSAY_ID NOT NULL NUMBER(10)
ABBREVIATED_SUMMARY VARCHAR2(2000 CHAR)
FULL_SUMMARY VARCHAR2(4000 CHAR)
INFO_XML XMLTYPE STORAGE BINARY

As soon as I execute anything like

select* from rgdh.assay_detail;

or

select * from rgdh.assay_detail where assay_id = 40751;

TOAD throws the access violation and hangs.

I can do the query fine in SQL+ on the host server.

If I list the columns in TOAD, it works. It only fails on the select *. Weird, eh?

I see other similar issues where the suggestion is to load a newer oracle client (I'm running a 12c client, so I don't think that's the problem) or recreate my toad.ini (everything else works fine, so seems unlikely that is corrupted.

Suggestions welcome. Thanks.

-Lisa

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle Forum notifications altogether.

Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.

There is a workaround:

Find the table in the Schema Browser, or do a CTRL+D (for describe), type in the table name, and enter.

Then go to the data tab. You can use the view/edit query to see how to select binary xml safely. The only catch is you can’t edit it in the grid.

-John

Thank you, Niel and John!

Maybe it will get fixed in a later version.

In the meantime, selecting the columns explicitly, using SQL+, or doing John’s schema browser data table workaround will all suffice. It’s just unfortunate as I don’t know there’s an XML type column in the table until it crashes TOAD so any work I had going in my other sessions and tabs because inaccessible.

Good to know that it’s not just me, though! Thanks again.

Something I started doing ( took a good couple of weeks before it was habbit ), is to every time I need to select an XMLTYPE column, use

XMLSERIALIZE (CONTENT xml_payload AS CLOB INDENT SIZE = 2)

It not only makes it selectable but also nicely formats it for human eyes...

Just a thought

Niel

On Fri, Mar 23, 2018 at 10:13 AM, ltansey bounce-ltansey@toadworld.com wrote:

RE: Access violation at address 000007FEC897C8BA in module 'oraclient12.dll'. Read of address 0000000000000010

Reply by ltansey
Thank you, Niel and John!

Maybe it will get fixed in a later version.

In the meantime, selecting the columns explicitly, using SQL+, or doing John's schema browser data table workaround will all suffice. It's just unfortunate as I don't know there's an XML type column in the table until it crashes TOAD so any work I had going in my other sessions and tabs because inaccessible.

Good to know that it's not just me, though! Thanks again.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle Forum notifications altogether.

Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.