# US 2015/0106140 A1 · Zero downtime maintenance with maximum business functionality

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0106140 A1
- Document ID: US20150106140A1
- Status: Published application
- Kind: A1
- Application number: 14/055,650
- Filed: 2013-10-16
- Published: 2015-04-16
- Earliest claimed: 2013-10-16
- Assignees: Sap SE
- Inventors: Lars-Eric Biewald; Volker Driesen; Andrey Engelko; Andre Haferkorn; Martin Hartig; Wieland Hoprich; Heiko Konrad; Christoph Luettge; Martin Mayer; Steffen Meissner; Matthias Mittelstein; Juergen Specht
- Web page: https://patentgrep.com/patent/US20150106140A1

## CPC

- G06Q 10/0631: Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

The present disclosure describes methods, systems, and computer program products for providing multi-level user interface theming. One computer-implemented method includes instantiating a shadow system and database schema for a new version software application in a shared database, the shadow system database schema containing aliases pointing to tables instantiated in a production database schema, instantiating a bridge database schema containing aliases pointing to each database table within the production database schema, preparing a bridge sub-system connected to the bridge database schema aliases, replicating database tables within the production database schema, for use by the bridge sub-system and adjusting the original database tables for structure and content consistent with the new version software application, deploying an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, and connecting an instantiated instance of the new version software application to adjusted database tables.

## Claims

### Claim 1

A computer-implemented method for performing a persistent data upgrade, comprising:
instantiating, by a computer, a shadow system for a new version software application and a shadow system database schema in a database shared with a production system executing a first version software application, the shadow system database schema acting as a database connector and containing aliases pointing to tables instantiated in a production database schema associated with the production system;
instantiating a bridge database schema in the database, wherein the bridge database schema contains aliases pointing to each database table within the production database schema;
preparing a bridge sub-system to execute as a first version software application, the bridge sub-system connected to the aliases contained within the bridge database schema;
replicating database tables within the production database schema, wherein the replicated database tables are used by the bridge sub-system and the original database tables are adjusted for structure and content consistent with the new version software application;
deploying an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, thereby created new version database tables, for the new version software application; and
instantiating an instance of the new version software application and connecting the new version software application to the new version database tables.

### Claim 2 (depends on 1)

The method of claim 1, wherein an alias in the shadow database schema points to a table instantiated in the production database schema containing at least the new version software application.

### Claim 3 (depends on 1)

The method of claim 1, wherein each database table within the production database schema is categorized according to the data associated with the database table.

### Claim 4 (depends on 3)

The method of claim 3, wherein only particular categorized database tables are replicated for use by the bridge sub-system.

### Claim 5 (depends on 1)

The method of claim 1, further comprising stopping the first version software application following rolling all end users from the first version software application to the bridge sub-system.

### Claim 6 (depends on 1)

The method of claim 1, wherein a compensation view is generated for database tables within the production database schema and is associated with an alias within the bridge schema, the compensation view generated for a database table normally accessed using a view.

### Claim 7 (depends on 1)

The method of claim 1, further comprising shutting down the bridge sub-system, deleting the bridge database schema and associated aliases, and deleting the replicated database tables used by the bridge sub-system.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
generating an alias with an alias name to point to a database table;
dropping the alias and renaming the database table to the alias name; and
repeating an access attempt to the alias name after a dynamic or pre-determined time interval if an access attempt is made to the alias or database table prior to completion of the dropping step and a database access error is generated.

### Claim 9

A non-transitory, computer-readable medium storing computer-readable instructions executable by a computer and operable to:
instantiate a shadow system for a new version software application and a shadow system database schema in a database shared with a production system executing a first version software application, the shadow system database schema acting as a database connector and containing aliases pointing to tables instantiated in a production database schema associated with the production system;
instantiate a bridge database schema in the database, wherein the bridge database schema contains aliases pointing to each database table within the production database schema;
prepare a bridge sub-system to execute as a first version software application, the bridge sub-system connected to the aliases contained within the bridge database schema;
replicate database tables within the production database schema, wherein the replicated database tables are used by the bridge sub-system and the original database tables are adjusted for structure and content consistent with the new version software application;
deploy an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, thereby created new version database tables, for the new version software application; and
instantiate an instance of the new version software application and connecting the new version software application to the new version database tables.

### Claim 10 (depends on 9)

The medium of claim 9, wherein an alias in the shadow database schema points to a table instantiated in the production database schema containing at least the new version software application.

### Claim 11 (depends on 9)

The medium of claim 9, wherein each database table within the production database schema is categorized according to the data associated with the database table.

### Claim 12 (depends on 11)

The medium of claim 11, wherein only particular categorized database tables are replicated for use by the bridge sub-system.

### Claim 13 (depends on 9)

The medium of claim 9, further storing instructions to stop the first version software application following rolling all end users from the first version software application to the bridge sub-system.

### Claim 14 (depends on 9)

The medium of claim 9, wherein a compensation view is generated for database tables within the production database schema and is associated with an alias within the bridge schema, the compensation view generated for a database table normally accessed using a view.

### Claim 15 (depends on 9)

The medium of claim 9, further storing instructions to shut down the bridge sub-system, deleting the bridge database schema and associated aliases, and deleting the replicated database tables used by the bridge sub-system.

### Claim 16 (depends on 9)

The medium of claim 9, further storing instructions to:
generate an alias with an alias name to point to a database table;
drop the alias and renaming the database table to the alias name; and
repeat an access attempt to the alias name after a dynamic or pre-determined time interval if an access attempt is made to the alias or database table prior to completion of the dropping step and a database access error is generated.

### Claim 17

A system, comprising:
a memory configured to hold persistent data;
at least one computer interoperably coupled with the memory and configured to:
instantiate a shadow system for a new version software application and a shadow system database schema in a database shared with a production system executing a first version software application, the shadow system database schema acting as a database connector and containing aliases pointing to tables instantiated in a production database schema associated with the production system;
instantiate a bridge database schema in the database, wherein the bridge database schema contains aliases pointing to each database table within the production database schema;
prepare a bridge sub-system to execute as a first version software application, the bridge sub-system connected to the aliases contained within the bridge database schema;
replicate database tables within the production database schema, wherein the replicated database tables are used by the bridge sub-system and the original database tables are adjusted for structure and content consistent with the new version software application;
deploy an upgrade sub-system and tools to complete adjustment of structure and content of the original database tables, thereby created new version database tables, for the new version software application; and
instantiate an instance of the new version software application and connecting the new version software application to the new version database tables.

### Claim 18 (depends on 17)

The system of claim 17, wherein each database table within the production database schema is categorized according to the data associated with the database table, and wherein only particular categorized database tables are replicated for use by the bridge sub-system

### Claim 19 (depends on 17)

The system of claim 17, further configured to:
stop the first version software application following rolling all end users from the first version software application to the bridge sub-system; and
shut down the bridge sub-system, deleting the bridge database schema and associated aliases, and deleting the replicated database tables used by the bridge sub-system.

### Claim 20 (depends on 17)

The system of claim 17, further configured to:
generate an alias with an alias name to point to a database table;
drop the alias and renaming the database table to the alias name; and
repeat an access attempt to the alias name after a dynamic or pre-determined time interval if an access attempt is made to the alias or database table prior to completion of the dropping step and a database access error is generated.
