Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSADMIN.ADM_ACCESS
This view shows what sessions are accessing certain objects. For some reason, V$LOCKED_OBJECT often does not show when objects are being accessed that prevents DDL changes but this shows that. This must be filtered on access_object otherwise it will be miserably slow.
|
Column |
Comment |
|---|---|
|
ACCESS_OWNER |
|
|
ACCESS_OBJECT |
|
|
ACCESS_TYPE |
|
|
PROBLEM |
|
|
LOGON_TIME |
|
|
PREV_EXEC_START |
|
|
USERNAME |
Field that uniquely identifies a user. (* inherited from FPSINPUT.GEN_USERS) |
|
SID |
|
|
STATUS |
|
|
MACHINE |
|
|
PROCESS |
Process defines what occurs at a step. Different steps can share the same process if they are identical. Process should normally determine allowed tools and recipe although it can be overridden by step, route, prd, lot, and experiment for exceptions. Each process is dynamically assigned to one or more eqp_type-process_family combinations with use_pct. One process_family is determined to be primary. If grouping is done correctly, a process should only be one eqp_group with no crossover. (* inherited from FPSINPUT.RTG_PROCESSES) |
|
SPID |
|
|
OSUSER |
|
|
MODULE |
Modules are departments of people who manage certain areas of the fab. The modules are assigned ownership of a set of tools to operate and maintain as well as steps on the route that they are responsible for executing. Since many of our tables include tool and step information together, we must distinguish between the owner of the step (WIP_MODULE), the owner of the operation of the tool (EQP_MODULE), and the owner of the maintenance of the tool (MNT_MODULE). WIP_MODULE is used to credit moves and set goals. Each route-step is assigned to a process family and then its wip_module is defined by the process family. EQP_MODULE is used to group tools particularly for tool performance reporting. Similar to WIP, each tool is dynamically assigned to a process family based on its assignments and then its eqp_module is defined by the process family. MNT_MODULE is usually the same as EQP_MODULE but unlike EQP_MODULE is not dependent on assignments but only on the EQP hierarchy. Each tool is assigned to an eqp_type and each eqp_type is assigned to a mnt_family and each mnt_family is assigned to a mnt_module. (* inherited from FPSINPUT.GEN_MODULES) |
|
USED_UBLK |
|
|
USED_UREC |
|
|
OWNER |
|
|
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 |
|
|
OPNAME |
|
|
TARGET |
|
|
PROGRESS |
|
|
ROWS_PROCESSED |
|
|
DISK_READS |
|
|
LAST_UPDATE_TIME |
|
|
ELAPSED_SECONDS |
|
|
CPU_USED |
|
|
MEMORY_USED_IN_MB |
|
|
READ_MB |
|
|
WRITE_MB |
|
|
PROGRAM |
|
|
SQL_ID |
|
|
SQL_TEXT |
|
|
SQL_FULLTEXT |