1. Tables and Views for Sales and Fusion Service
  2. ZOE_OL_SSS_REQUESTS

ZOE_OL_SSS_REQUESTS

This table stores the snapshots created for 'requestSnapshot' calls and returns the saved snapshots for every 'querySnapshot' call. For a given 'requestSnapshot' call, it may create multiple snapshot records and the snapshots are maintained using the same Guid but with different sequence numbers. The status, write and read positions of each 'requestSnapshot' call are maintained in a special row called base row of the table for which the sequence=-1 The snaphots are maintained in this table only for the life time of a snapshot request-response(one requestSnapshot call and many querySnapshot calls). All the snapshot entries for a given 'requestSnapshot' call would be removed once all the snapshots are read/retrived using the 'querySnapshot' calls.

Details

  • Schema: FUSION

  • Object owner: ZOE

  • Object type: TABLE

  • Tablespace: Default

Primary Key

Name Columns

ZOE_OL_SSS_REQUESTS_PK

SNAPSHOT_GUID, SNAPSHOT_SEQUENCE

Columns

Name Datatype Length Precision Not-null Comments
SNAPSHOT_GUID VARCHAR2 64 Yes Guid of the requested snapshot file. Forms composite primary key of the table along with SNAPSHOT_SEQUENCE column. The value of Guid would be the same for the snapshots created for a single 'requestSnapshot' call. There may be multiple snapshot records with the same Guid, but the value of SNAPSHOT_SEQUENCE would be different.
SNAPSHOT_SEQUENCE NUMBER 9 Yes Sequence of the requested snapshot files. Forms composite primary key of the table along with SNAPSHOT_GUID column. The value of Guid would be the same for the snapshots created for a single 'requestSnapshot' call. There may be multiple snapshot records with the same Guid, but the value of Sequence would be different.
SNAPSHOT_STATUS VARCHAR2 30 Status of the snapshot request. For a single 'requestSnapshot' call, there would be multiple snapshot records created, status of the given snapshot request is stored in the base row (row with sequence = -1 )
SNAPSHOT_DATA BLOB Stores the snapshot in BLOB form.
SNAPSHOT_WRITE_POSITION NUMBER 9 Write position indicates the position of snapshots created for a given 'requestSnapshot' call, the value starts from 0 and is stored in the base row. Every time a new snapshot is created for a 'requestSnapshot' call, it increment the write position by one and uses that as the sequence for the current snapshot row.
SNAPSHOT_READ_POSITION NUMBER 9 Read position indicates the position of snapshots already retrieved using the 'querySnapshot' calls, the value starts from 0 and is stored in the base row. For a given 'requestSnapshot' call, it might create multiple snapshot records. Every time a snapshot is requested using 'querySnapshot' call, it increment the read position by one and returns the snpashot stored at snapshot_sequence= incremented_read_position.
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
ZOE_OL_SSS_REQUESTS_PK Unique Default SNAPSHOT_GUID, SNAPSHOT_SEQUENCE