XLA_ONLINE_TXN_PROCS
This table represents the collection of processes running the online transaction engine. Each row will map to a single concurrent request identifier which is the primary key to this table.
Details
-
Schema: FUSION
-
Object owner: XLA
-
Object type: TABLE
-
Tablespace: REFERENCE
Columns
| Name | Datatype | Length | Precision | Not-null | Comments |
|---|---|---|---|---|---|
| CRID | NUMBER | 18 | Yes | Primary key and concurrent request identifier for process. | |
| ENGINE_NAME | VARCHAR2 | 30 | Yes | Name of the engine that is running. | |
| ENGINE_LANGUAGE | VARCHAR2 | 1 | Yes | Implementation languages are [C], [J] Java, or [P] PL/SQL. | |
| SPECIALIZATION_ZONE | NUMBER | 18 | Yes | Used to segregate requests for performance default 0 *. | |
| PROCESS_STATUS | VARCHAR2 | 10 | Yes | Process status value for online accounting processing. | |
| ERR_MSG | VARCHAR2 | 2000 | Error message name for online accounting processing. | ||
| MEMTOP | NUMBER | Not currently used. | |||
| TXN_COUNT | NUMBER | Count of transaction by online accounting processing. | |||
| PARENT_CRID | NUMBER | 18 | Concurrent request identifier of process that this process is replacing. | ||
| CHILD_CRID | NUMBER | 18 | Concurrent request identifier of process that is replacing this process. | ||
| OTE_CACHE_INVALIDATION_EVENTS | VARCHAR2 | 2000 | This column will hold notifications about the events that invalidate OTE cache, for example GL period opened or closeed. OTE engines will monitor events that were stamped in this column and replace themselves to force refresh their cache. An event stamped in this column will have the following pattern: #EVENT_TYPE_CODE#EVENT_TIMESTAMP#EVENT_PARAMETER1_EVENT_PARAMETER2; For example, for a GL period Sep-11 closed event that happened on Oct 17 11:48 AM, we would have a event stamp as: #GL_PERIOD_CLOSE #17-OCT-11 11:48:27.363747 AM#1#Sep-11; #1 is for ledger_id = 1. If there are multiple cache invalidation events happen in a very close short period of time before an engine was able to detect an invalidation and changes its status, the events would be concatenated. | ||
| 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. | |
| 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_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. | |
| ESS_REQ_ID | NUMBER | 18 | Identifier of the online engine request. | ||
| LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. |
Indexes
| Index | Uniqueness | Tablespace | Columns |
|---|---|---|---|
| XLA_ONLINE_TXN_PROCS_N1 | Non Unique | FUSION_TS_TX_DATA | PROCESS_STATUS, SPECIALIZATION_ZONE |
| XLA_ONLINE_TXN_PROCS_N2 | Non Unique | FUSION_TS_TX_DATA | CHILD_CRID |
| XLA_ONLINE_TXN_PROCS_N3 | Non Unique | FUSION_TS_TX_DATA | PARENT_CRID |
| XLA_ONLINE_TXN_PROCS_U1 | Unique | FUSION_TS_TX_DATA | CRID |