论坛上一个朋友的帖子，自己使用sql_trace 跟踪了dbms_logmnr.end_logmnr的后台执行过程。。

http://www.itpub.net/thread-1326195-1-1.html

自己做了一下。。关键部分如下：

=====================
PARSING IN CURSOR #1 len=137 dep=1 uid=0 ct=47 lid=0 tim=10262706437 hv=4235843831 ad='30e2795c' sqlid='a603td7y7mq7r'
DECLARE  BEGIN    sys.dbms_logmnr_internal.delete_table_inclusion_rule();    sys.dbms_logmnr_internal.delete_user_inclusion_rule();  END;
END OF STMT
PARSE #1:c=125000,e=251939,p=3,cr=646,cu=0,mis=1,r=0,dep=1,og=4,tim=10262706433
=====================
=====================
PARSING IN CURSOR #6 len=41 dep=2 uid=0 ct=7 lid=0 tim=10262733241 hv=555114787 ad='2f63f95c' sqlid='4vrf4pnhjcs93'
DELETE FROM SYSTEM.LOGMNR_GT_TAB_INCLUDE$
END OF STMT
PARSE #6:c=31250,e=26385,p=0,cr=96,cu=0,mis=1,r=0,dep=2,og=1,tim=10262733236
EXEC #6:c=0,e=67,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=1,tim=10262733493
STAT #6 id=1 cnt=0 pid=0 pos=1 bj=0 p='DELETE  LOGMNR_GT_TAB_INCLUDE$ (cr=0 pr=0 pw=0 time=0 us)'
STAT #6 id=2 cnt=0 pid=1 pos=1 bj=1017 p='TABLE ACCESS FULL LOGMNR_GT_TAB_INCLUDE$ (cr=0 pr=0 pw=0 time=0 us cost=2 size=0 card=1)'
=====================
=====================
PARSING IN CURSOR #4 len=42 dep=2 uid=0 ct=7 lid=0 tim=10262739121 hv=2565574379 ad='2f6447b8' sqlid='9c552h2cfr3rb'
DELETE FROM SYSTEM.LOGMNR_GT_USER_INCLUDE$
END OF STMT
PARSE #4:c=0,e=5157,p=0,cr=23,cu=0,mis=1,r=0,dep=2,og=1,tim=10262739116
EXEC #4:c=0,e=73,p=0,cr=0,cu=0,mis=0,r=0,dep=2,og=1,tim=10262739380
STAT #4 id=1 cnt=0 pid=0 pos=1 bj=0 p='DELETE  LOGMNR_GT_USER_INCLUDE$ (cr=0 pr=0 pw=0 time=0 us)'
STAT #4 id=2 cnt=0 pid=1 pos=1 bj=1018 p='TABLE ACCESS FULL LOGMNR_GT_USER_INCLUDE$ (cr=0 pr=0 pw=0 time=0 us cost=2 size=0 card=1)'
=====================


可以看出 执行了dbms_logmnr.end_logmnr之后，数据库清除与logminr有关的动态性能视图所包含的事务变化内容。。