Topics: |
This section provides maintenance recommendations for the Omni-HealthData™ database.
The following table lists and describes the tables that can be archived in the Omni-HealthData™ database.
Table |
Table Name |
Description |
Archive Strategy |
---|---|---|---|
Measures |
os_measure |
Operational status information (usually timed) about processes that take place in the system (deploying a bundle, starting a service, merging, and so on). |
As needed. |
Work Orders |
os_work_orders |
A list of Work Order tasks generated by the system for execution. |
As needed. |
Work Order Items |
os_work_order_item |
A list of Work Order Items that represent the individual operations that take place during the execution of a Work Order. |
As needed. |
Change Data Capture (If enabled) |
os_cdc_change |
Captures changes that take place to subjects within the system. |
As needed. |
Change Data Capture Subscription |
os_cdc_subscription |
A list of subscribers to change data capture events. |
|
Change Data Capture Trace |
os_cdc_trace |
Detailed information on a change data capture event. |
|
Ramp Control |
os_ramp_control |
A list of subject operations that load data into the system from the relational on ramp. |
All logs and system-generated information is stored in the omnigen/OmniGenData directory. The following list describes the location, purpose, and archiving recommendations of the system logs and deployment logs.
omnigen/OmniGenData/logs/{command, controller, server, OmniDesignerRepository, …etc}
System logs are separated into subdirectories by application name.
omnigen/OmniGenData/deployment
The following list describes the general maintenance recommendations for common database systems.
Tools: Oracle Database Resource Manager
Maintenance: Many of the generic maintenance tasks can be automated to run automatically during specific maintenance intervals.
Tools:
Cron scripts, Windows Task Scheduler, and check_postgres are available for monitoring database health and reporting unusual conditions.
Maintenance:
The PostgreSQL VACUUM command has to process each table on a regular basis for the following reasons:
Tools: SQL Server Management Studio (SSMS)
Maintenance:
The Maintenance Plan Wizard can be started from SSMS and can be found in the Management section of the SSMS tree. It creates scheduled jobs, which are run by the SQL Server Agent and can perform the following tasks:
Omni-HealthData™ systems maintain some runtime data, which diminishes over time. This data resides in a relational database as follows:
The following server-based runtime settings are available to control purge events:
https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm
The following Omni-HealthData™ server-based runtime settings are available to control the purging of inactive user data:
When a SETUP_DELETE_STALE work order becomes active, a corresponding DELETE_STALE work order is issued for each subject in the model that is populated with data. In a DELETE_STALE work order, all inactive records of a given subject that were last updated before the value specified by the Purge Inactive Age setting are deleted. This includes source, instance, master, history, and master-master reference records.
You can access these runtime settings from the Runtime tab, located under Configuration on the left pane of the Omni Console, as shown in the following image.