Brute force (dropping, renaming, invalidating, etc.) solution means apps will stop functioning for some time which, in most cases, isn't an option. If so, you could enable:

AUDIT ALL ON your_sequence;

which will audit any statement that accesses sequence using the pseudocolumns CURRVAL or NEXTVAL. You can keep sequence audit enabled for some adequate period of time to collect enough data. But, in general, audit, brute force, etc. are reactive solutions. Correct solution is data modelling and code management system to get answers to this and many other object dependency questions.

SY.

Hello,

we have to keep in mind that dependencies can be used for example to detect that a sequence is used in a procedure or in a trigger (in my opinion this is easier than invalidating a sequence and then identifying other invalidated objects), I wrote this in my first reply, but original question was about "table.column", so also the case of DEFAULT VALUEs…

And unfortunately it seems that default values in dba_tab_columns are just seen as "text" (what's more, stored in a LONG) and there is no dependency… So even if a sequence myseq was dropped, if a column has default value "myseq.nextval", the issue would be seen only when trying to use it (inserting a row without value for the given column).

This is where my second reply, although using a "brute force" query, can help (thanks to the fact that we don't expect thousands of rows in result set). BTW, would there be really many rows, I would spool the output and then edit the spool file, searching "my some 20 sequences".

Best regards,

Bruno