Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Is there any way to see what DBMS_MVIEW.REFRESH is actually doing? I want to investigate partition change tracking (PCT) and verify that it is indeed only updating modified partitions.

share|improve this question
Enable event 10046 at level 4 (bind values output) and then manually fire off a refresh. When you analyze the trace file (preferable using something like Orasrp), it will show you all the fun things that happen in the refresh. make sure you that in your session. – Raj Oct 30 '13 at 12:28
can you explain how to do that? – wrschneider Oct 30 '13 at 13:31
alter session set events '10046 trace name context forever, level 4' / exec dbms_mview.refresh('blah'); commit; exit; Then analyze tracefile using orasrp (since it shows you the call tree very nicely) or tkprof the old workhorse. However, tkprof will not show you bind values used, orasrop OTOH will. The output won't be pseudo code, but based on sequence of sqls, you will have to infer what is happening in the execution phase. – Raj Oct 31 '13 at 17:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.