Re: Truncating tables in RAC environment

Quoting Mladen Gogala <gogala_at_sbcglobal.net>:

> Trace shows the following:
>
> BEGIN
> BEGIN
> IF
> (xdb.DBMS_XDBZ0.is_hierarchy_enabled_internal(sys.dictionary_obj_owner,
> sys.dictionary_obj_name, sys.dictionary_obj_owner)) THEN
> xdb.XDB_PITRIG_PKG.pitrig_truncate(sys.dictionary_obj_owner,
> sys.dictionary_obj_name);
> END IF;
> EXCEPTION
> WHEN OTHERS THEN
> null;
> END;
> BEGIN
> IF
> (xdb.DBMS_XDBZ0.is_hierarchy_enabled_internal(sys.dictionary_obj_owner,
> sys.dictionary_obj_name, sys.dictionary_obj_owner,
> xdb.DBMS_XDBZ.IS_ENABLED_RESMETADATA)) THEN
> xdb.XDB_PITRIG_PKG.pitrig_dropmetadata(sys.dictionary_obj_owner,
> sys.dictionary_obj_name);
> END IF;
> EXCEPTION
> WHEN OTHERS THEN
> null;
> END;
> END;
>
> Basically, RDBMS is invoking non-documented objects from XDB and only queries
> from SYS owned
> objects. This very package figures prominently in all security advisories as
> well as on Pete
> Finnegan's site. In other words, Oracle started using XML for internal
> operations. Nobody, however,
> explains what that package is.
> --

VERY interesting! Thanks, Mladen.
I wonder if this is Oracle making sure there are no xml appendages to the GTT? As in xml datatypes?

-- 
Cheers
Nuno Souto
from sunny Sydney
--
http://www.freelists.org/webpage/oracle-l