Abstract: The present disclosure relates to a method for enabling access to data of a data analysis system by a set of one or more external database systems. The data analysis system comprises a source database system and target database system. The data analysis system is configured for synchronizing the data in the source database system with the target database system using a primary source transaction log in the source database system. The method comprises: creating a secondary transaction log. Data changes applied at the target database system may be received from the target database system. At least one log entry that represents each received data change may be creating in the secondary transaction log. The secondary transaction log may be used by the set of external database systems for applying data changes according to the secondary transaction log, thereby storing the data in the set of external database systems.

Abstract: According to one embodiment, a method, computer system, and computer program product for performing data synchronization between a source DBMS, comprising a trusted database, and a target DBMS, comprising an untrusted datastore and a trusted datastore, is disclosed. The present invention may include upon the source DBMS performing an update to an object in the trusted source database, sending the object change to a trusted data replication engine, encrypting the object change, sending the encrypted object change with a related decryption key to the target DBMS, upon receiving the encrypted object change and the related decryption key at the target DBMS, searching an object related to the object change in the untrusted target data store, identifying a decryption key for the searched object, replacing the identified decryption key by the received decryption key, and integrating the encrypted object change in encrypted form into the untrusted target data store.

Abstract: The present disclosure relates to a method for enabling access to data of a data analysis system by a set of one or more external database systems. The data analysis system comprises a source database system and target database system. The data analysis system is configured for synchronizing the data in the source database system with the target database system using a primary source transaction log in the source database system. The method comprises: creating a secondary transaction log. Data changes applied at the target database system may be received from the target database system. At least one log entry that represents each received data change may be creating in the secondary transaction log. The secondary transaction log may be used by the set of external database systems for applying data changes according to the secondary transaction log, thereby storing the data in the set of external database systems.

Abstract: In an approach, a processor receives a data manipulation request on a target database. A processor sends the data manipulation request to a source database. The source database attempts to persist a data manipulation action relating to the data manipulation request. Responsive to a successful attempt to persist the data manipulation action: the source database sends a log position of the data manipulation action to a data replication engine; a processor replicates the data manipulation request triggering the data manipulation action in the target database; and a processor confirms to the target database that the data manipulation action in the target database has been completed.

Abstract: A technique for logging tasks in a computer system. Tasks are logged into the computer system by executing at least one task at the computer system. A set of log metadata and a set of log levels of log records of the at least one task may be determined from an execution log output of the at least one task. Execution outputs of a further task may be determined according to the determined set of log metadata and associated set of log levels.

Abstract: In an approach, a processor receives a data manipulation request on a target database. A processor sends the data manipulation request to a source database. The source database attempts to persist a data manipulation action relating to the data manipulation request. Responsive to a successful attempt to persist the data manipulation action: the source database sends a log position of the data manipulation action to a data replication engine; a processor replicates the data manipulation request triggering the data manipulation action in the target database; and a processor confirms to the target database that the data manipulation action in the target database has been completed.

Abstract: A technique for logging tasks in a computer system. Tasks are logged into the computer system by executing at least one task at the computer system. A set of log metadata and a set of log levels of log records of the at least one task may be determined from an execution log output of the at least one task. Execution outputs of a further task may be determined according to the determined set of log metadata and associated set of log levels.

Abstract: The present disclosure relates to a problem management method for a user system. A method may include detecting an error in the user system. A signed package may be provided in accordance with the detected error, wherein the package comprises at least a script. The user system may verify the authenticity of the package using a signature of the package, and may execute the script if the package is authentic.

Abstract: Creating at a target database system, a target table and a history table each having a set of attributes of a source table in addition to at least one time attribute, wherein the time attribute of a record indicates the time when the record is valid. Receiving a request for applying a change of the source table to the target table. The request comprises a time value generated by the source database system indicating a time of the change. The change to the target table and the time value may be assigned to the time attribute of the current version and previous version of the record. The previous version of the record may be stored in the history table. The target table and the history table may be used to process a redirected query comprising a selection criterion on the time attribute.

Abstract: Creating at a target database system, a target table and a history table each having a set of attributes of a source table in addition to at least one time attribute, wherein the time attribute of a record indicates the time when the record is valid. Receiving a request for applying a change of the source table to the target table. The request comprises a time value generated by the source database system indicating a time of the change. The change to the target table and the time value may be assigned to the time attribute of the current version and previous version of the record. The previous version of the record may be stored in the history table. The target table and the history table may be used to process a redirected query comprising a selection criterion on the time attribute.

Abstract: A method for processing an unsupported data type in a database is disclosed. The method for processing an unsupported data type in a database comprises detecting, while copying data from a primary to a secondary database, a table for data comprising a data type that is unsupported by the secondary database. Furthermore, the method comprises generating a base table in the secondary database as a copy of the detected table of the primary database without the data of the unsupported data type, generating an additional table in the secondary database for data of the unsupported data type, and linking the additional table to the base table in the secondary database via a row-identifier relationship. Additionally, the method comprises accessing data of the unsupported data type via the additional table while performing queries against the secondary database.

Abstract: The present disclosure relates to a problem management method for a user system. A method may include detecting an error in the user system. A signed package may be provided in accordance with the detected error, wherein the package comprises at least a script. The user system may verify the authenticity of the package using a signature of the package, and may execute the script if the package is authentic.