BOM objects are showing timestamp mismatch
Hi,
Invalid objects exist after patching. Manually recompiled most of them.
Original issue was with BOMTBICX trigger. It looks it is an issue now.
Customer was asked to execute the below query in the previous SR and BOMTBICX was listed in the output.
select do.name dname, po.name pname, p_timestamp, po.stime p_stime
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 does not match*/
order by 2,1;
select do.name dname, po.name pname, p_timestamp, po.stime p_stime
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 does not match*/
order by 2,1;
Tagged:
0