MSC_CACHE_DATA

Table is used for caching a Worksheet data

Details

  • Schema: FUSION

  • Object owner: FUSION

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

msc_cache_data_PK

PLAN_ID, WORKSHEET_ID, SQL_KEY, BIND_KEY, USER_SECURITY_KEY

Columns

Name Datatype Length Precision Not-null Comments
PLAN_ID NUMBER Yes PLAN_ID the plan for which cache will be stored
WORKSHEET_ID NUMBER Yes WORKSHEET_ID the Worksheet for which cache will be stored
SQL CLOB SQL:the SQL the actual query that was cached
SQL_KEY NUMBER Yes SQL_KEY: the HASH key of the query that was executed
BIND CLOB BIND: the binds that were used for the query
BIND_KEY NUMBER Yes BIND_KEY: the HASH key of the binds that are cached
RESULTS CLOB Yes RESULTS: the actual results that were cached
USER_SECURITY_KEY NUMBER Yes USER_SECURITY_KEY : the Hash Key of the User security
CACHE_DATE DATE Yes CACHE_DATE: the date query was executed and cached
EXECUTION_TIME NUMBER Execution_TIME:how long was the execution of the query
DETAILS CLOB DETAILS- comments and other related data
CREATED_BY VARCHAR2 64 Yes Who column: indicates the user who created the row.
CREATION_DATE TIMESTAMP Yes Who column: indicates the date and time of the creation of the row.
LAST_UPDATED_BY VARCHAR2 64 Yes Who column: indicates the user who last updated the row.
LAST_UPDATE_DATE TIMESTAMP Yes Who column: indicates the date and time of the last update of 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
msc_cache_data_U1 Unique Default PLAN_ID, WORKSHEET_ID, SQL_KEY, BIND_KEY, USER_SECURITY_KEY