A colleague asked if there was a way to do column level dependency tracking recently. He wanted to know for a given view, which tables and the columns on those tables, it was dependent upon, without, of course, reading through the code.
I was vaguely aware that since 11gR1 Oracle has been tracking fine grained (column) dependencies, but couldn’t find a way of seeing the details stored, until I found this interesting article from Rob Van Wijk:
About Oracle: DBA_DEPENDENCY_COLUMNS
I passed the details on to our DBA who implemented it and it seemed to work, for us. Your mileage may vary, of course.
Complications have utterly covered our lives and caused several click over here cheap levitra mental-health problems. ED medications are the most common treatment which continue reading that drugshop order viagra has helped millions of people to restore their sexual life. Discount medications viagra sample overnight can be found at a Canada Pharmacy. Many individuals thought that it must be consumed in oral form along with water viagra cialis generic by the patients. Some comments on Rob’s blog post, bearing in mind, of course, that it was written in 2008 and refers to 11gR1:
- D_ATTRS contains values other than “000100000A”. I’ve observed this in a basic 12c install and a production 11gR2 install
- D_ATTRS is commented in $ORACLE_HOME/rdbms/admin/dcore.bsq as “/* Finer grain attr. numbers if finer grained */”
- D_REASON is commented in $ORACLE_HOME/rdbms/admin/dcore.bsq as “/* Reason mask of attrs causing invalidation */”. On my basic 12c installation, all rows contain NULL for this value although on a production 11gR2 database I observed a handful of rows with values in this column.
- Noted from the comments against Rob’s article is the opportunity to vote for this feature on OTN here