How to deal with invalid objects monitored by Oracle every day in the production environment?

Every day in the production environment Oracle How to deal with the monitored invalid objects ?

---

Take the answer 1：

If it is Oracle Inside , For example, daily statistical information tasks occasionally collect oracle All objects that need to be deleted urgently in the future , We usually monitor and alarm this situation .
If it is an invalid stored procedure or function involved in the application , If the program is no longer used , Will contact the developer to delete .
If it is a program, it will also use , Generally, add a recompile command to the monitoring script , The premise will definitely analyze why it fails .

---

Other answers 1：

If it is Oracle Inside , For example, daily statistical information tasks occasionally collect oracle All objects that need to be deleted urgently in the future , We usually monitor and alarm this situation .
If it is an invalid stored procedure or function involved in the application , If the program is no longer used , Will contact the developer to delete .
If it is a program, it will also use , Generally, add a recompile command to the monitoring script , The premise will definitely analyze why it fails .

Other answers 2：

If these invalid objects are related to the application , Then you need to recompile and generate this object

Other answers 3：

1、 If it is oracle Internal object , Handle according to the specific situation .

2、 If it is an application object , This needs to be communicated with the project team , Whether this exception needs to be handled .

3、 The above two are ideal solutions , Actually, in our production , Generally, it is to see whether the failure of objects will cause exceptions , If there is no abnormality, it doesn't matter ....