PJT_SUM_RUN_HIST
Stores the run history for different requests, projects and run-types.
Details
-
Schema: FUSION
-
Object owner: PJT
-
Object type: TABLE
-
Tablespace: FUSION_TS_TX_DATA
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
ENTERPRISE_ID | NUMBER | 8 | Yes | ENTERPRISE_ID | |
REQUEST_ID | NUMBER | 18 | Enterprise Service Scheduler: indicates the request ID of the job that created or last updated the row. | ||
USER_NAME | VARCHAR2 | 240 | USER_NAME | ||
PARAMETERS | VARCHAR2 | 240 | PARAMETERS | ||
RUN_TYPE | VARCHAR2 | 30 | RUN_TYPE | ||
START_DATE | TIMESTAMP | START_DATE | |||
END_DATE | TIMESTAMP | END_DATE | |||
COMPLETION_TEXT | VARCHAR2 | 240 | COMPLETION_TEXT | ||
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
PJT_SUM_RUN_HIST_U1 | Unique | Default | REQUEST_ID, PARAMETERS |