Why are Views, Procedures, Triggers being marked as invalid when there has been NO ACTIVITY against the database?
I can correct them today (by recompiling, no changes are necessary); however tomorrow the same Views, Procedures, Triggers will bemarked as invalid.
I can guarantee that there has been NO ACTIVITY in that time frame.

>
Why are Views, Procedures, Triggers being marked as invalid when there has been NO ACTIVITY against the database?
I can correct them today (by recompiling, no changes are necessary); however tomorrow the same Views, Procedures, Triggers will bemarked as invalid.
I can guarantee that there has been NO ACTIVITY in that time frame.
>
What database? What version?

What version of Sql Developer?

Have you confirmed the object status in the database using a different tool? For Oracle use sql*plus and check the status.

Perhaps you are correct about there being no activity in your database to invalidate those objects. But what about dependencies on remote DB objects that could have been invalidated (perhaps dropped and recreated)?

http://docs.oracle.com/cd/B19306_01/server.102/b14220/depend.htm

You may wish to use SQL Developer's object viewer Dependencies tab to check for that possibility. And I wonder about dependency management using timestamps, considering the recent switch to daylight saving time in much of the world.