Abstract: In an upgrade infrastructure performing an overall upgrade operation comprising multiple upgrade processes being executed, possibly concurrently, on multiple hosts for upgrading one or more software applications hosted by hosts, automated hang detection mechanisms are disclosed for quickly, efficiently, and automatically detecting when one or more of the upgrade process are in a hang state. Different hang detection techniques are described including a metadata-driven hang detection mechanism and a code-driven hang detection mechanism.

Abstract: In an upgrade infrastructure performing an overall upgrade operation comprising multiple upgrade processes being executed, possibly concurrently, on multiple hosts for upgrading one or more software applications hosted by hosts, automated hang detection mechanisms are disclosed for quickly, efficiently, and automatically detecting when one or more of the upgrade process are in a hang state. Different hang detection techniques are described including a metadata-driven hang detection mechanism and a code-driven hang detection mechanism.

Abstract: Embodiments provide techniques for concurrently upgrading one or more software applications hosted by one or multiple hosts. Checkpoint data associated with the upgrade processes executing on the multiple hosts may be generated during the upgrade. The checkpoint data may be stored in a shared storage that can be accessed by the upgrade processes. Each upgrade process running on a host may be adapted to read checkpoint data from the shared storage and write checkpoint data only to a dedicated location on the shared storage. Checkpoint data written by a first upgrade process may be read by a second upgrade process to determine the status and/or progress of the first upgrade process on a given host. In this manner, the checkpoint data enable the multiple upgrade processes to synchronize with each other.

Abstract: In an upgrade infrastructure performing an overall upgrade operation comprising multiple upgrade processes being executed, possibly concurrently, on multiple hosts for upgrading one or more software applications hosted by hosts, automated hang detection mechanisms are disclosed for quickly, efficiently, and automatically detecting when one or more of the upgrade process are in a hang state. Different hang detection techniques are described including a metadata-driven hang detection mechanism and a code-driven hang detection mechanism.

Abstract: In an upgrade infrastructure performing an overall upgrade operation comprising multiple upgrade processes being executed, possibly concurrently, on multiple hosts for upgrading one or more software applications hosted by hosts, automated hang detection mechanisms are disclosed for quickly, efficiently, and automatically detecting when one or more of the upgrade process are in a hang state. Different hang detection techniques are described including a metadata-driven hang detection mechanism and a code-driven hang detection mechanism.

Abstract: Embodiments provide techniques for concurrently upgrading one or more software applications hosted by one or multiple hosts. Checkpoint data associated with the upgrade processes executing on the multiple hosts may be generated during the upgrade. The checkpoint data may be stored in a shared storage that can be accessed by the upgrade processes. Each upgrade process running on a host may be adapted to read checkpoint data from the shared storage and write checkpoint data only to a dedicated location on the shared storage. Checkpoint data written by a first upgrade process may be read by a second upgrade process to determine the status and/or progress of the first upgrade process on a given host. In this manner, the checkpoint data enable the multiple upgrade processes to synchronize with each other.

Abstract: Two computers are respectively programmed to generate descriptions of database objects (such as tables) in a first database, and compare the generated descriptions to corresponding schema objects in a second database. Objects in the second database are changed to conform to the first database if differences are found during comparison. The just-described differences in objects may arise due to changes being made to a software program that uses data contained in the objects.

Abstract: Two computers are respectively programmed to generate descriptions of database objects (such as tables) in a first database, and compare the generated descriptions to corresponding schema objects in a second database. Objects in the second database are changed to conform to the first database if differences are found during comparison. The just-described differences in objects may arise due to changes being made to a software program that uses data contained in the objects.