Data ChangeManagement, historization and archiving

The easiest way to log and analyze data during the development process or a software implementation phase. Of course, historization/archiving can also be used continuously in a productive system (assuming there is sufficient storage space).

• The original data structure (table) remains unchanged.
• Data structure changes (origin table) are automatically detected, transferred to the DCM table and marked by an incarnation flag.
• Which DML operation took place is also logged.
• Database user of the DML operation is also saved.
• Related DML operations can be linked for analysis by the transaction ID.

• Historization/archiving can be defined for individual tables or the entire schema.
• The historization/archiving can be temporarily interrupted and started again.
• Age of historization/archiving can be limited to number of days.
• The historization can therefore also be used for data archiving.

Oracle Apex application for graphical management and simple installation.

All process parameters and DCM objects can be edited, including tablespaces for data and indices separately from each other.

Advanced logging including debugging: