A distributed, transactional database uses timestamps, such as logical clock values, for entry versioning and transaction management in the database. To write to the database, a service requests a timestamp to be inserted into the database with a new version of data. During a backup procedure, a cleanup process is paused, issuing new timestamps is paused, and a backup timestamp is generated, which results in an effective backup copy. During a restore of a backup, a snapshot of the database is loaded and any entries older than the backup timestamp are deleted, which ensures that a consistent restore has occurred.

A memory image can be captured by generating metadata indicative of a state of volatile memory and/or byte-addressable PMEM at a particular time during execution of a process by an application. This memory image can be persisted without copying the in-memory data into a separate persistent storage by storing the metadata and safekeeping the in-memory data in the volatile memory and/or PMEM. Metadata associated with multiple time-evolved memory images captured can be stored and managed using a linked index scheme. A linked index scheme can be configured in various ways including a full index and a difference-only index. The memory images can be used for various purposes including suspending and later resuming execution of the application process, restoring a failed application to a previous point in time, cloning an application, and recovering an application process to a most recent state in an application log.

A distributed, transactional database uses timestamps, such as logical clock values, for entry versioning and transaction management in the database. To write to the database, a service requests a timestamp to be inserted into the database with a new version of data. During a backup procedure, a cleanup process is paused, issuing new timestamps is paused, and a backup timestamp is generated, which results in an effective backup copy. During a restore of a backup, a snapshot of the database is loaded and any entries older than the backup timestamp are deleted, which ensures that a consistent restore has occurred.

The invention relates to a data processing system and a date processing method. The data processing system is configured to perform a hardware transactional memory (HTM) transaction. The data processing system comprises a byte-addressable nonvolatile memory for persistently storing data and a processor being configured to execute an atomic HTM write operation in connection with committing the HTM transaction by writing an indicator to the nonvolatile memory indicating the successful commit of the HTM transaction.

In general, embodiments of the invention relate to a method for enabling enhanced logging. The method includes obtaining historical data for a target entity, determining a steady state error probability of the target entity using the historical data, and enabling, based on the steady state error probability, a first level of enhanced logging on the target entity.

The present disclosure relates to system(s) and method(s) for verifying data loading requirements of an avionics unit. The system receives a request for data loading. The request comprises file data, and data loading requirements associated with the avionics unit. Further, the system obtains target file from a repository based on an analysis of the request. The system further generates valid data set and invalid data set in the target file based on an analysis of the data loading requirements. Upon generation, the system verifies predefined data loading requirements of the avionics unit using the invalid data set from the target file.

Methods and systems of applying retroactive adjustments to financial data. An example method includes: receiving one or more adjustment records associated with a financial account; saving a snapshot of the financial account, the snapshot comprising a plurality of transaction records reflecting previously processed transactions associated with the financial account; merging the adjustment records and the transaction records to produce a plurality of adjusted transaction records; processing adjusted transaction records to produce an updated state of the financial account; comparing the saved snapshot to the updated state of the financial account to produce one or more adjustment events; and processing the adjustment events using one or more event processing rules.

Systems, computer program products, and methods are described herein for dynamically propagating data from a database to a cache. The present invention may be configured to receive metadata associated with updates to data records of a database, obtain, from the database and based on the metadata, the data records that have been updated, and provide the data records that have been updated to a cache. The present invention may be configured to receive, from applications, calls for the data records, obtain, from the cache and based on receiving the calls, the data records, and provide, to the applications, the data records. In some embodiments, the present invention may be configured to monitor the database and generate the metadata associated with the updates to the data records.

Systems and methods are described for matching a corrupted database record with a record of a validated database. The system receives a corrupted record from a first database. The corrupted record is vectorized to create an input data vector. A denoised data vector is generated by applying a denoising autoencoder to the input data vector, where the denoising autoencoder is specific to the first database. The system compares the denoised data vector with each of a plurality of validated data vectors generated based on records of the validated database to determine that a first denoised data vector matches a matching vector. In response, the system trains the denoising autoencoder using a data pair that includes the input data vector and the matching vector. The system also outputs the validated record that was used to generate the first matching vector.

Systems, methods, and computer products are described herein for identifying data inconsistencies within database tables associated with an application. A master data inconsistency evaluator receives data including at least one selection parameter within at least one database table. By the master data inconsistency evaluator evaluates the at least one selection parameter by comparing the at least one selection parameter with other database tables associated with the application to identify data inconsistencies. The master data inconsistency evaluator repairs the data inconsistencies to further facilitate an error free transaction.