My Oracle Support Banner

Oracle Argus Enterprise Edition Cloud Service Requirement for Data Lock Point (DLP) for Argus History (Doc ID 2286907.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Argus Safety Cloud Service - Version 7.0 to 8.0 [Release 7.0 to 8.0]
Information in this document applies to any platform.
Oracle Argus Enterprise Edition Cloud Service current release 8.1, 8.0 and 7.x releases all recommend the deployment of standard configurations so that the highest degree of supportability is possible. Customer specific requests to disable standard configuration settings are discouraged due to added complexity and increased risk of non-compliance.


Document the benefits of Data Lock Point (DLP) for Oracle Argus Enterprise Edition Cloud Service and rationale for requirement to enable it at the database level.


Oracle Argus Enterprise Edition Cloud Service includes Argus Insight, Argus Analytics and Argus Mart.   Argus Mart can be used to generate periodic reports on Argus History data or custom reports, Advance Conditions and Case Series on Argus History for a snapshot of time using time stamps.   Without Argus History data in Argus Mart enabled with Data Lock Point, Oracle cannot support a customer's reporting requirements sufficiently.  Requests to disable Data Lock Point at the database level are discouraged. 

Oracle Argus Enterprise Edition Cloud Service requires that Data Lock Point be enabled at the database level to capture “Argus History” (incremental case data changes) starting from whenever Data Lock Point is enabled.  Data Lock Point is a standard requirement to use Argus Mart.  Argus Mart can be used to generate periodic reports on Argus History and intelligently include data cleanup follow-ups for a snapshot of time.   Argus Mart can also generate custom reports which use Argus History data.  

Even if a customer does not currently require Argus History data, it is required that Oracle Argus Enterprise Edition Cloud Service customers enable Argus Mart to create Argus History data because, in the future, they may decide to generate periodic reports for a snapshot in time, or create custom reports that look into Argus Mart or use Advance Conditions/Case Series on Argus History data.

For customers who want to build Advance Conditions/Case Series on top of Argus History data now, or in the future, there is the 'AI on AM' feature.   This makes Argus Mart data accessible from the Argus Insight user interface.  To use this feature, Argus History data should be available in Argus Mart first.  Keeping DLP enabled at database level is an added advantage.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.