Database Updates

The order content is stored in the plan_item_data database.

Note: The database tables given here are for the PostgreSQL. Similarly, you can refer to the <OM_HOME>/db/dbscripts/oracle path for the Oracle database values.

The impacted tables are as follows:

Order_Data

This table stores the information regarding orders.

Column Name in Database Data Type Description
partitiondate Date Stores the partition date of the order.
orderid Varchar (128) Stores the order Id.
orderref Varchar (128) Stores the order ref of the order.
order_ser Text Stores the latest order request. In case of amendment, this stores the latest order request submitted during the amendment.
plan_ser Text Stores the plan generated by the AOPD. This plan does not reflect the latest statuses of plan and plan items.
org_order_ser Text In case of amendment, this column stores the original order request submitted during the submit order request.
tenantid Varchar (128) Stores the tenant id to which this order belongs.
planid Varchar (128) Stores the plan id of the order.
status Varchar (128) Stores the order status.
data Text

Stores the state machine of the order in XML format. This does not represent the entire state machine of the order. Individual Plan Item state machines are saved in the plan item data table.

The data type of this column has been changed to CLOB (Character Large Object)/Text.

instance_id Varchar (250) Stores the instance Id to which these orders belong.
pre_amendment_scxml Text Stores the interim sc XML required during amendment processing.
sequencing_enabled Boolean Whether the order is sequenced based on the order sequencing feature.
customer_key Varchar (250) Stores the customer key of the sequenced order.
feasibility_request_retry_count Integer Stores the feasibility retry count of the order.
businesstransactionid Varchar (128) Transaction Id generated by Order Management Server.

Plan_Item_Data

It comprehensively stores all the necessary information related to the plan item of an order.

Column Name in Database Data Type Description
id Varchar (524) Serves as the unique identifier for the plan item. It is generated by concatenating the orderId, tenantId, and planItemId.
orderid Varchar (256) Stores the order id to which this plan item belongs.
tenantid Varchar (256) Stores the tenant id to which this plan item belongs.
planitemid Varchar (256) Stores the plan item id of the plan item.
data Text Stores the state machine of the plan item in XML format.
dependentplanitemids Text Stores the plan item Ids of other plan items whose milestones are dependent on this plan item.
partitiondate Date This field holds the creation date of the data partition.
status Varchar (256) This column represents different stages like pending, completed, execution, and more.
execute_request_retry_count Integer Indicates how many attempts have been made to retry an execution request.
suspend_request_retry_count Integer This field tracks the retry attempts for a suspension request.

Order_Event

This table stores the information regarding the messages or events received by the orchestrator on EMS. It tracks incoming messages or events in case an Orchestrator instance goes inactive. These messages are reassigned to another active instance by the Broker Service.

The older order_event table is renamed as order_event_temp table. This table is no longer required by the orchestrator. Previously, it contained the names of events that failed to acquire a lock. Until 5.1.0 and 6.0.0 releases, PendingOrderProcessor retrieves pending events from this table. After it has been renamed, you can trigger a migration API to transfer these events back to EMS. After migration, you can drop order_event_temp table.

Column Name in Database Data Type Description
partitiondate Date Date of partition
tasktrackingid Varchar (250) Stores the unique identifier of this message. This is used to purge the message once it is processed by the Orchestrator.
originator Varchar (10) Stores the instance id to which this order belongs.
orderid Varchar (250) Stores the order id of the order.
tenantid Varchar (250) Stores the tenant id of the order.
message Text Stores the entire message or event received by the Orchestrator.
creationtime Numeric Marks the moment the order event is initiated.
nodeid Varchar (250) Identifies the specific node associated with the order event uniquely.
status Varchar (10) This column represents different stages such as pending, completed, and execution.

The following tables remain unchanged:

  • order_in_sequence

  • order_in_play

  • notification

  • order_amendment

  • order_messages

  • time_scheduler

  • Time_scheduler_error

The following tables are dropped as they are no longer required by the orchestrator:

  • order_lock

  • dead_order_event