Weekend Learning: Setting LONGOPS

Almost two years ago I posted about how we started proactively looking for data in the gv$session_longops table for things that could use tuning in our system and now after quite a bit of use I think we have realized that not everything which runs long goes into this table.  How do we fix that?  Enter Ric Van Dyke's article about actually using the DBMS_APPLICATION_INFO package to explicitly have your code enter run information directly into the gv$session_longops table.