Modifying scheduled execution of object modification methods associated with database objects
US-8984514-B2 · Mar 17, 2015 · US
US9626390B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9626390-B2 |
| Application number | US-97917510-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 27, 2010 |
| Priority date | Dec 27, 2010 |
| Publication date | Apr 18, 2017 |
| Grant date | Apr 18, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a program database module configured to define, at a shadow system, a shadow program database including data and a structure collectively defining an upgrade to an original program database on an original system. The computer system can include a basis module configured to define at the shadow system a shadow basis database related to start functionality of the shadow system. The computer system can also include a downtime execution module configured to trigger the shadow system to change from a downstate to an upstate based on a combination of data included in the shadow basis database and the data of the shadow program database.
Opening claim text (preview).
What is claimed is: 1. A computer system including instructions stored on a non-transitory computer-readable storage medium, the computer system comprising: a processor configured to: define, at a shadow system, a shadow program database including data and a structure collectively defining an upgrade to an original program database on an original system; define, at the shadow system, a shadow basis database including information related to start-up functions of the shadow system, the start-up functions including transitioning the shadow system from a downstate to an upstate, the information related to start-up functions including data related to at least one service configured to enable basic functionality of the shadow system, the shadow basis database is defined in shadow system during an upstate of the shadow system and an upstate of the original system, the shadow basis database is defined based on an original basis database associated with the original system, and the shadow basis database is upgraded from the original basis database to the shadow basis database based on differences between the original system and a target system during a downstate of the shadow system and the upstate of the original system; and trigger the shadow system to change from a downstate to an upstate based on a combination of data included in the shadow basis database and the data of the shadow program database. 2. The computer system of claim 1 , wherein the shadow basis database is accessed by a kernel of the shadow system when the shadow system is changed from the downstate to the upstate. 3. The computer system of claim 1 , wherein the processor is configured to change the shadow system from the downstate to the upstate at a first time, to change the shadow system from the upstate to the downstate at a second time before the first time, and to modify the shadow database based on a customization associated with a support package between the first time and the second time. 4. The computer system of claim 1 , wherein the processor is further configured to: modify the shadow database based on a customization associated with a support package before the processor triggers the shadow system to change from the downstate to the upstate. 5. The computer system of claim 1 , wherein a first after import method is triggered for execution at the shadow system while the shadow system is in the upstate, and a second after import method is triggered for execution after the shadow system has been dismantled. 6. The computer system of claim 1 , wherein an enhancement spot method is triggered for execution at the shadow system while the shadow system is in the upstate, and a second enhancement spot method is triggered for execution after the original system has been replaced by the shadow system. 7. The computer system of claim 1 , wherein a shadow user database is defined during an uptime of the original system, and wherein the processor is further configured to: replace a portion of an original user database with the shadow user database after the shadow system has been changed from the downstate to the upstate, and configured to replace the original program database with the shadow program database during a downtime of the original system. 8. The computer system of claim 1 , wherein the processor is further configured to: suspend a batch job of the original system and configured to log-off a user from the original system before a downtime of the original system is initiated. 9. The computer system of claim 1 , wherein the shadow system is configured to operate within hardware of the original system, and wherein the processor is further configured to: replace an original user database with a shadow user database, and configured to replace the original program database with the shadow program database during a downtime of the original system, and dismantle the shadow system from the hardware of the original system before the original user database and the original program database have been replaced. 10. The computer system of claim 1 , wherein a combination of a default shadow program database and a support package program database correspond with the data and the structure of the shadow program database. 11. The computer system of claim 1 , wherein the shadow system includes a set of upgrade executable files associated with the structure of the shadow program database and the data of the shadow program database, the original system includes a set of original executable files, and wherein the processor is further configured to: replace a structure of the original program database on the original system with the structure of the shadow program database on the shadow system, and configured to replace data of the original program database on the original system with the data of the shadow program database on the shadow system; and replace the set of original executable files included in the original system with the set of upgrade executable files included in the shadow system during a downtime of the original system. 12. The computer system of claim 1 , wherein the structure of the shadow program database is defined by a plurality of tables and the data of the shadow program database includes a plurality of program instructions stored within the plurality of tables, the shadow system includes a set of upgrade executable files configured to access the plurality of program instructions from the plurality of tables. 13. A non-transitory computer-readable storage medium storing code representing instructions that when executed are configured to cause a processor to perform a process, the code comprising code to: define, at a shadow system, a shadow program database including data and a structure collectively defining an upgrade to an original program database on an original system; define, at the shadow system, a shadow basis database including information related to start-up functions of the shadow system, the information related to start-up functions including data related to at least one service configured to enable basic functionality of the shadow system, the start-up functions including transitioning the shadow system from a downstate to an upstate, the shadow basis database is defined in the shadow system during an upstate of the shadow system and an upstate of the original system, the shadow basis database is defined based on an original basis database associated with the original system, and the shadow basis database is upgraded from the original basis database to the shadow basis database based on differences between the original system and a target system during a downstate of the shadow system and the upstate of the original system; and trigger the shadow system to change from a downstate to an upstate based on a combination of data included in the shadow basis database and the data of the shadow program database. 14. The non-transitory computer-readable storage medium of claim 13 , wherein the shadow basis database is accessed by a kernel of the shadow system when the shadow system is changed from the downstate to the upstate. 15. The non-transitory computer-readable storage medium of claim 13 , wherein the code further comprises code to change the shadow system from the downstate to the upstate at a first time, to change the shadow system from the upstate to the downstate at a second time before the first time, and to modify the shadow database based on a customization associated with a support package between the first time and the second time. 16. The non-transitory computer-readable s
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title
Database migration support · CPC title
Physics · mapped topic
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.