Oracle Bug 6136074-ORA-04068/ORA-04065/ORA-06508 resolution

Oracle Bug 6136074-ORA-04068/ORA-04065/ORA-06508 addressed on 10.2.0.3, where a bug may cause compilation or view failure, and the Failure result is not just that the current view or process is not available, instead, the entire data dictionary may be affected, resulting in a ORA-04068 error during execution of the stored procedure. Error message: ORA-04068: existing state of packages has been discarded. ORA-04065: not executed, altered or dropped stored procedure P_PACKAGE.P_PROORA-06508: PL/SQL: cocould not find program unit being called: P_PACKAGE.P_PROORA-06512: at line 1
This problem corresponds to the BUG information: Bug 6136074-ORA-04068/ORA-04065 ORA-06508 on VALID objects [ID6136074.8], the cause is that the time stamps of PLSQL dependent objects are inconsistent during object compilation, resulting in problems. The Oracle document provides the SQL statement to check the problem: select do. obj # d_obj, do. named_name, do. type # d_type, po. obj # p_obj, po. name p_name, to_char (p_timestamp, 'dd-MON-YYYY HH24: MI: ss') "P_Timestamp", to_char (po. stime, 'dd-MON-YYYY HH24: MI: ss') "STIME", decode (sign (po. stime-p_timestamp), 0, 'same', '* DIFFER *') Xfrom sys. obj $ do, sys. dependency $ d, sys. obj $ powhere P_OBJ # = po. obj # (+) and D_OBJ # = do. obj # and do. status = 1/* dependent is valid */ D po. status = 1/* parent is valid */and po. stime! = P_timestamp/* parent timestamp not match */order by; use this script to re-compile the obtained object, which can solve this problem and avoid re-occurrence of the problem, upgrade the database version to 10.2.0.4 or later. ---------------------------------- Present by dylan.