Abstract:
Implementations can include providing a snapshot table, replacing, in a first access schema, a first projection view with a union view, creating, in a second access schema, a snapshot projection view, a second projection view, and a set of database triggers, and during execution of an upgrade procedure that results in changes to records of the data table: recording the changes to the records of the data table in the snapshot table, for each record of the data table changed, providing the record in the snapshot table in an unchanged state through at least one database trigger and the snapshot projection view, and returning a set of records through the union view in response to a query, the set of records including a first sub-set of records of the data table and a second sub-set of records of the snapshot table.
Abstract:
Embodiments described herein relate to an improved technique for maintaining a consistent state during data migration operations in an active database system. Data can be copied from database table(s) of the active database system into a corresponding database table(s) in the shadow system. Snapshots of the active system can be taken at a specified point in time and used to establish a point of consistency. Later, the snapshot data can be compared with the data in the shadow database system. If the data matches, then the active and shadow database systems are at a consistent state and the data migration process completes. If the data does not match, embodiments are configured to restore the consistent state at the specified point in time by copying the snapshot data into the shadow database table(s).
Abstract:
Various techniques are described for precisely locking database objects within a database during a system upgrade with the use of database freeze triggers. Some database freeze triggers can be utilized to lock transport requests while other database freeze triggers can be utilized to lock database objects such as exchange tables. For transport requests, techniques describe the use of a whitelist identify transport objects or transport object types which shall remain unblocked. As a result, a database freeze trigger can be generated for transport objects or transport object types that are not included in the whitelist. For database objects, techniques describe the identification of a tool or service which has been allowed during the upgrade. Database objects which can be modified during execution of the tool or service can be identified. Database freeze triggers can be generated for the database objects besides those identified.
Abstract:
Embodiments described herein relate to an improved technique for maintaining a consistent state during data migration operations in an active database system. Data can be copied from database table(s) of the active database system into a corresponding database table(s) in the shadow system. Snapshots of the active system can be taken at a specified point in time and used to establish a point of consistency. Later, the snapshot data can be compared with the data in the shadow database system. If the data matches, then the active and shadow database systems are at a consistent state and the data migration process completes. If the data does not match, embodiments are configured to restore the consistent state at the specified point in time by copying the snapshot data into the shadow database table(s).
Abstract:
A system and method for database migration is provided. In an example embodiment, the database migration technique may include execution modules having a first connection to a source database and a second connection to a target database, and orchestration modules adapted to identify first and second subsets of statements from a single storage table, wherein the first and second subsets of statements are executed by the execution modules during an uptime period of the source database.
Abstract:
Methods, systems, and computer-readable storage media for applying corrections during an upgrade procedure of a software management system include actions of receiving a set of white-listed object types, receiving a set of corrections to be imported, the set of corrections including a set of objects, to which corrections are to be applied during the upgrade procedure, determining a set of object types included in the set of corrections, the set of object types including one or more object types, and selectively permitting one or more transport requests to effect corrections of the set of corrections to be issued during the upgrade procedure based on the set of object types and the set of white-listed object types.
Abstract:
Methods, systems, and computer-readable storage media for applying corrections during an upgrade procedure of a software management system include actions of receiving a set of white-listed object types, receiving a set of corrections to be imported, the set of corrections including a set of objects, to which corrections are to be applied during the upgrade procedure, determining a set of object types included in the set of corrections, the set of object types including one or more object types, and selectively permitting one or more transport requests to effect corrections of the set of corrections to be issued during the upgrade procedure based on the set of object types and the set of white-listed object types.
Abstract:
Various techniques are described for precisely locking database objects within a database during a system upgrade with the use of database freeze triggers. Some database freeze triggers can be utilized to lock transport requests while other database freeze triggers can be utilized to lock database objects such as exchange tables. For transport requests, techniques describe the use of a whitelist identify transport objects or transport object types which shall remain unblocked. As a result, a database freeze trigger can be generated for transport objects or transport object types that are not included in the whitelist. For database objects, techniques describe the identification of a tool or service which has been allowed during the upgrade. Database objects which can be modified during execution of the tool or service can be identified. Database freeze triggers can be generated for the database objects besides those identified.