It is the same situation.
Filed a tar and support asked me to investigate invalid objects.
They are present and of type xml schema but they can 't be related to
valid schemas in dba_xml_schemas. It looks like these are objects
whose references etc are gone.
My original problem with xsql not working when selecting too much data
is still there because the data is prepared correctly in the table despite
the ora-0600 (See ora-0600.ora-code.com) only the output of the result table fails when done in xsql
page. At this time we are trying to build a testcase for support.
I found out this problem is probably related to the use of xml type
column because when we select the data as a clob we get xml out
beyond the limit we had previously. Does this sound familiar for anybody?
Tnx,
Jeroen
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --