OraFAQ Forum: Client Tools » XML DOM Mismatch

Home » Other » Client Tools » XML DOM Mismatch (oracle 10g)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

XML DOM Mismatch [message #467262]

Fri, 23 July 2010 02:22

b_chugh
Messages: 68
Registered: August 2005
Location: delhi

Member

Hi All

ORA-31180: DOM Type mismatch in invalid PL/SQL DOM handle

I am getting this error while debugging one of the package in PL/SQL developer or in TOAD. Is there any setting which we need to perform at the database level to debug the packages which have the code related to XML DOM. I am asking as the same code works exactly fine at one of the test database and it gives the above error on the other database.

I have also searched the net before posting this message but could not find much which I can change in the code.

Thanks

Report message to a moderator

Re: XML DOM Mismatch [message #467265 is a reply to message #467262]

Fri, 23 July 2010 02:25

rahulvb
Messages: 924
Registered: October 2009
Location: Somewhere Near Equator.

Senior Member

OCI-31180: DOM Type mismatch in invalid PL/SQL DOM handle

Cause: The specified PL/SQL DOM handle is referencing a DOM Node
whose DOM Type that does not match the one available in the
session. This could happen because the pl/sql handle was reused,
or the original document is no longer available.
 
Action: Ensure that the pl/sql handle for the target node is
valid and try the operation again.

Report message to a moderator

Re: XML DOM Mismatch [message #467268 is a reply to message #467262]

Fri, 23 July 2010 02:31

Michel Cadot
Messages: 68770
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

ORA-31180: DOM Type mismatch in invalid PL/SQL DOM handle
  *Cause:  The specified PL/SQL DOM handle is referencing a DOM Node whose
           DOM Type that does not match the one available in the session.
           This could happen because the pl/sql handle was reused, or the
           original document is no longer available.
  *Action: Ensure that the pl/sql handle for the target node is valid and
           try the operation again.

Regards
Michel

Report message to a moderator

Re: XML DOM Mismatch [message #467273 is a reply to message #467262]

Fri, 23 July 2010 02:43

b_chugh
Messages: 68
Registered: August 2005
Location: delhi

Member

I know the description of the oracle error and sugegsted solution....but I failed to understand that how come the same code works in one database and does not work in the other database. If there is some problem in the code then it should not work in any of the similar databases.

Thanks

Report message to a moderator

Re: XML DOM Mismatch [message #467274 is a reply to message #467273]

Fri, 23 July 2010 02:46

rahulvb
Messages: 924
Registered: October 2009
Location: Somewhere Near Equator.

Senior Member

Please copy and paste the SQL session with Error

[Updated on: Fri, 23 July 2010 02:47]

Report message to a moderator

Re: XML DOM Mismatch [message #467280 is a reply to message #467273]

Fri, 23 July 2010 03:19

Michel Cadot
Messages: 68770
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

Quote:

If there is some problem in the code then it should not work in any of the similar databases.

And how do you expect than we can debug some code that we don't see?

First, I would ask, is there any problem with TOAD which is the most likely point of dfailure. So try to reproduce the same thing with SQL*Plus.

Also to debug a procecdure you must have some privileges like DEBUG CoNNECT SESSION and DEBUG on all objects you want to debug.

Regards
Michel

Report message to a moderator

Re: XML DOM Mismatch [message #467338 is a reply to message #467262]

Fri, 23 July 2010 08:36

b_chugh
Messages: 68
Registered: August 2005
Location: delhi

Member

I am getting the error in both PL/SQL developer as well as in TOAD.

I am able to debug the code but the the error comes after calling the xmldom.appendChild and I am not able to see what is causing that, it directly goes to the exception section after that statement.

lvxmlnText := xmldom.makeNode(xmldom.createElement(in_DOC, in_NODENAME));
lvxmlnNew:= xmldom.appendChild(inout_NODE, lvxmlnText);
xmldom.freenode(lvxmlnText);

Code breaks in the middle line...when doing appendChild...

Thanks

Thanks

Report message to a moderator

Re: XML DOM Mismatch [message #467341 is a reply to message #467338]

Fri, 23 July 2010 08:48

cookiemonster
Messages: 13972
Registered: September 2008
Location: Rainy Manchester

Senior Member

Remove the exception section and you may get more useful information.

Report message to a moderator

Re: XML DOM Mismatch [message #467559 is a reply to message #467262]

Mon, 26 July 2010 00:57

b_chugh
Messages: 68
Registered: August 2005
Location: delhi

Member

The call to the code from where the exception is coming is in one package and the exception handling section is in the other package. So i cannot remove the exception section.

Regards
b_chugh

Report message to a moderator