XML Parse Failure : Diagnostics / workaround requested

Question

Hey people,
I don't know if anyone else has had the issue but I have have hit it several times now and its very frustrating. (Usually as a result of trying to remove incorrect schemas via Enterprise Manager).
If there is ever an invalid XML instance (ie. one that fails to parse) in the XDB views (PATH_VIEW, RESOURCE_VIEW), a select query to return clobs doesn't work. It fails with:
"ORA-31013 XML Parse Failed"
"ORA-19202 : Error occurred during XML processing"
In this case it continues with
"LPX-00234 : namespace 'ts' is not declared
Error at line 5
And some message extension errors and so on and so forth.
A couple of questions...
1) Is it actually necessary to validate the XML to return the CLOB value (or an approximation) of a stored XMLType anyway?
2) Would it be possible to add a validity flag in order be able to restrict against these instances that fail parsing? (For diagnostics / removal purposes).
3) Is there some other way that I am missing for deleting the invalid resource? Every time I try and find the resource or schema record, the XML processing fails and I can't identify it to delete it (manually or otherwise).
Any ideas?
Lachlan

Answer 1

I'd avoid OEM for the moment
From SQLPLUS
call dbms_xdb.deleteResource('path',2) will delete a resource regardless of errors that were encounterd
Also from ftp
quot rm_rf path..
-Mark