Toad World® Forums

TOAD 12.8.0.49: XMLTYPE proc/fnc parameter causes access violation


#1

Hello,

I freshly installed recent TOAD version 12.8.0.49 64bit and I’m having problems with procedures/functions with XMLTYPE parameter.

once I hit ‘run procedure’ button in schema broswer or ‘set execution parameters’ button in editor toad throws access violation error.

strange thing is that,

11gR2 client + 10gR2 DB - there is no problem

11gR2 client + 11gR2 DB - access violation

Application:

1.3 Version Number : 12.8.0.49

Exception:

2.2 Address : 00000000041A06CB
2.3 Module Name: Toad.exe - (Toad™ for Oracle®)
2.5 Type : EAccessViolation
2.6 Message : Access violation at address 00000000041A06CB in module ‘Toad.exe’. Read of address 000000400000901B.
2.7 ID : 80490000

Active Controls:

4.1 Form Class : Ghost
4.2 Form Text : Toad for Oracle - [SYSTEM@PDMT - Editor (TEST_XML)] (Not Responding)
4.3 Control Class: TtdDScintilla
4.4 Control Text : create or replace procedure test_xml(x xmltype) as
begin
null;
end;

do you have any ideas what might be a problem?

emha.


#2

I can’t reproduce. I tried my 11.2.0.2 database with 11.2.0.3 client. Can you post the entire error log file? It’s named Toad.el and located in Toad’s appdata folder. The appdata location is specified in Options on the General page.

Thanks,

Michael

On 11/12/2015 12:17 PM, emha wrote:

TOAD 12.8.0.49: XMLTYPE proc/fnc parameter causes access violation

Thread created by emha
Hello,

I freshly installed recent TOAD version 12.8.0.49 64bit and I’m having problems with procedures/functions with XMLTYPE parameter.

once I hit ‘run procedure’ button in schema broswer or ‘set execution parameters’ button in editor toad throws access violation error.

strange thing is that,

11gR2 client + 10gR2 DB - there is no problem

11gR2 client + 11gR2 DB - access violation

Application:


1.3 Version Number : 12.8.0.49

Exception:


2.2 Address : 00000000041A06CB

2.3 Module Name: Toad.exe - (Toad™ for Oracle®)

2.5 Type : EAccessViolation

2.6 Message : Access violation at address 00000000041A06CB in module ‘Toad.exe’. Read of address 000000400000901B.

2.7 ID : 80490000

Active Controls:


4.1 Form Class : Ghost

4.2 Form Text : Toad for Oracle - [SYSTEM@PDMT - Editor (TEST_XML)] (Not Responding)

4.3 Control Class: TtdDScintilla

4.4 Control Text : create or replace procedure test_xml(x xmltype) as

                 begin

                 null;

                 end;

do you have any ideas what might be a problem?

emha.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General
notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.


#3

here you are.

emha.
Toad.zip (317 KB)


#4

Thanks. It looks like one of the internal structures representing the parameter is corrupt, but I cannot reproduce. If you compile a new procedure and go to Set Parameters window do you get the AV immediately? Is there anything you must do first like execute the procedure once and on subsequent loads of Set Parameters it crashes?

Thanks,

Michael

On 11/12/2015 04:18 PM, emha wrote:

RE: TOAD 12.8.0.49: XMLTYPE proc/fnc parameter causes access violation

Reply by emha
here you are.

emha.

Attachments:

Toad.zip

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General
notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.


#5

first I noticed the problem on a regular procedure existing in DB for a long time once I needed to run it manually from schema browser.

I thought toad got into some unstable state so I closed it and started anew, just connected to DB and tried to run proc once again, but again got AV.

next attempt was to run it from editor/debugger, the same AV.

next I tried it with another DB of the same 11gR2 release, again AV.

I was about to write a post here, so I tried to make a minimal test case - proc with empty body and with just one XMLTYPE parameter (you may see it in original post). I succesfully compiled it (F9), but when tried to open parameter window, I immediately got AV.

finally I got an idea to test against other DB release (10gR2) - both existing proc and minimal test case proc, both worked fine.

so basically, in my enviromnet (11.2.0.3 client, 11.2.0.4 DB) I get the AV instantly regardless of whether it is existing or brand new procedure.

emha.


#6

It might have something to do with cached data from prior version of Toad not being compatible with recent changes. You could close Toad and rename ToadParams.dat in your User Files folder. Note that there may also be ToadParams.ini. Only rename ToadParams.dat. If that works please email me that file offline: michael.staszewskiquest.com.

Thanks,
Michael

On 11/12/2015 05:16 PM, emha wrote:

RE: TOAD 12.8.0.49: XMLTYPE proc/fnc parameter causes access violation

Reply by emha
first I noticed the problem on a regular procedure existing in DB for a long time once I needed to run it manually from schema browser.

I thought toad got into some unstable state so I closed it and started anew, just connected to DB and tried to run proc once again, but again got AV.

next attempt was to run it from editor/debugger, the same AV.

next I tried it with another DB of the same 11gR2 release, again AV.

I was about to write a post here, so I tried to make a minimal test case - proc with empty body and with just one XMLTYPE parameter (you may see it in original post). I succesfully compiled it (F9), but when tried to open parameter window, I immediately got AV.

finally I got an idea to test against other DB release (10gR2) - both existing proc and minimal test case proc, both worked fine.

so basically, in my enviromnet (11.2.0.3 client, 11.2.0.4 DB) I get the AV instantly regardless of whether it is existing or brand new procedure.

emha.

To reply, please reply-all to this email.

Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.


#7

unfortunatelly it didn’t help

emha.