Toad supports unicode starting with Toad 10. One of the changes we had to make
is to use the Unicode-enabled OCI methods. Unfortunately, the OCI has a few bugs
with Unicode. This is one of them.
You can work around it like this:
SELECT T.XMLTEXT.GetClobVal() as XMLTEXT
FROM TEST_TABLE2 T
This workaround will be automatic in Toad 10.5’s schema browser.
You’ll still have to code it manually in the editor though.
I am not aware of any privilege or role named DEBUG. Please advise.
you need to :
GRANT DEBUG CONNECT SESSION TO your_user;
The privilege is "debug connect session"
Cheers,
Norm. [TeamT]
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Thanks. But running that query, even though there’s now no error, just produces a blank (null) cell. The query returns data ok through the other clients I’ve tried.
When I run that query, I see a cell with in it. If I double-click
it, then I see the data.
If I go to Options -> Data Grids -> Data, and check “Preview CLOB
and LONG data”, then I see the first 20 characters or so followed by
’.…’ and then I can again double-click to see the rest.
‘Deferred Lob Read’ is supposed to delay fetches of LOB values until
you scroll to them in the grid. If there is more than a screen full of
data, it will reduce initial fetch time. But it should not cause what you are
seeing. What Oracle client version do you have? I am not sure offhand if
this is a factor, but it is worth checking. I am using an 11g client, and
I’m not seeing null regardless of the option settings.
Toad Version 10.5
Hi, is this the same explanation as to why I am getting (HUGECLOB) displayed in my xmltype column, when I try to view the contents of my table via the Schema Browser ? If I try to click on HUGECLOB, it displays my xml in one line only.
If i do a select * from
, the data grid displays my xmltype data in a formatted manner and easily readable.
I’ve tried the options the others mentioned in this thread, which doesn’t really fix how its displayed in the schema browser…
Some Oracle clients would crash when you look at XML Data. So I made a change
in the schema browser to always return XML as CLOBS by changing the query using
the GetClobVal function.
Later, we learned that 11g clients do not have the problem. So I made a
change in the 10.5 patch (and current beta) to stop using GetClobVal if you have
an 11g client.
Short version – get the latest Toad patch and this will go away.
I have not been able to get this working for a couple of months and have had to revert back to TOAD 9.7.2. I have installed TOAD 10.5 and I have Oracle 11.1.0.6 client on my desktop. I still get the OCI error.
I reread the thread, and tried it again. I am able to reproduce the problem
even with the latest 10.5 patch and an 11g client. I should have been more
thorough before I replied the first time. Sorry about that.
I also tried it with the beta – it gets a little better there – I
only get an error one time in the beta, and after that, it works! I’m
not sure what is going on, but I think the problem is coming from our 3rd party
Oracle access components. I will send your test case to them and see what
happens.
I opened a case with our 3rd party component developer, they are saying that it
is a bug in the OCI, which happens for XMLTYPEs with binary storage and OCI in
the Unicode mode (in 9.7 and prior, there was no Unicode).
So I’m afraid all I can tell you is what you already know – you can
work around it in 10.x by not using the binary storage options for XMLTYPE.
SOLVED: Yo tambien tuve ese problema y despues de revisar el tema y varios foros encontre que algunas tblas en las cuales tenia campos xmltype, sucedia el error y en otras no.
revise y detecte que las tablas que no habia error tenian la sig declarción:
ALTER TABLE WF_USUARIO
ADD (COBERTURA XMLTYPE);
y las que no tenian error:
ALTER TABLE WF_USUARIO
ADD (COBERTURA SYS.XMLTYPE);
entonces, recree el campo con la definicion completa a sys.xmltype y toad funciono correctamente
