Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSADMIN.CHK_INVALID
This view looks for invalid objects in all FPS schemas as well as errors in ADM_LOAD. We must use dbf_xxx views here because dbf_objects does not include triggers and synonyms in other schemas and we need to check if those are invalid. Then because we must use dbf_xxx views and Oracle does not allow grant select on views using dbf_xxx and we need to grant permission on CHK_INVALID to other users, our solution is to refresh a table with this data which we can grant.
|
Column |
Comment |
|---|---|
|
ERR_SORT |
|
|
OWNER |
|
|
OWNER_SORT |
|
|
OBJECT_NAME |
This could be an object name (we will disable loading of that object in the scheduled jobs), a load job (we will disable loading of all objects in that scheduled job), an FPSAPP prefix (we will disable loading of all objects with that prefix), a constraint (we can explain why it is permanently disabled), or a trigger (technically an object so we can get away with omitting this from the column name and also to explain why it is permanently disabled). (* inherited from FPSADMIN.CFG_DISABLED) |
|
OBJECT_TYPE |
|
|
COMPONENT |
|
|
STATUS |
|
|
PROBLEM |
|
|
ALERT |
|
|
SQL_QUERY |