ORA-4068 ORA-4065 ORA-06508 Errors Signalled For Valid Objects
(Doc ID 456338.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.3 [Release 10.2]Information in this document applies to any platform.
Symptoms
When loading certain PL/SQL packages the database continuously reports ORA-04068 errors.
Restarting database does not help. Flushing shared pool does not help.
We can see timestamp discrepancies exist for valid objects.
set pagesize 10000
column d_name format a20
column p_name format a20
select do.obj# d_obj,do.name d_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*') X
from sys.obj$ do, sys.dependency$ d, sys.obj$ po
where P_OBJ#=po.obj#(+)
and D_OBJ#=do.obj#
and do.status=1 /*dependent is valid*/
and po.status=1 /*parent is valid*/
and po.stime!=p_timestamp /*parent timestamp not match*/
order by 2,1;
Output would look like:
RADAR_SALES_ORDER_API 11 VEHICLE_STOCK_API 08-JUN-2007 13:27:06 15-JUN-2007 19:03:05 *DIFFER*
SALES_SALES_OBJ_ITEMS_API 11 SALES_BUSINESS_DEALS_API 15-JUN-2007 18:45:09 15-JUN-2007 19:03:07 *DIFFER*
column d_name format a20
column p_name format a20
select do.obj# d_obj,do.name d_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*') X
from sys.obj$ do, sys.dependency$ d, sys.obj$ po
where P_OBJ#=po.obj#(+)
and D_OBJ#=do.obj#
and do.status=1 /*dependent is valid*/
and po.status=1 /*parent is valid*/
and po.stime!=p_timestamp /*parent timestamp not match*/
order by 2,1;
Output would look like:
RADAR_SALES_ORDER_API 11 VEHICLE_STOCK_API 08-JUN-2007 13:27:06 15-JUN-2007 19:03:05 *DIFFER*
SALES_SALES_OBJ_ITEMS_API 11 SALES_BUSINESS_DEALS_API 15-JUN-2007 18:45:09 15-JUN-2007 19:03:07 *DIFFER*
Also the problematic packages/procedures reported in the error exists and have status VALID in dba_objects view.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |
| This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |