DOWNTIME REDUCTION FOR ENTERPRISE MANAGER PATCHING

• US 20110138374A1
• Filed: 12/09/2009
• Published: 06/09/2011
• Est. Priority Date: 12/09/2009
• Status: Abandoned Application

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Pal, Suprio
• Application Number:
  US12/634,518
• Publication Number:
  US 20110138374A1
• Time in Patent Office: Days
• US Class Current: 717/169
• CPC Class Codes: G06F 8/656 while running

Abstract

A server identifies a group of patches. The server pushes data indicating the group of patches to each of a group of targets in such a way so that each target recognizes the patches as grouped together. At each target, the received patches are then applied to the target application as a group. As a result, target application downtime is minimized, and the target application need only be brought offline once for the entire group of patches. The patches may be applied to a target application as a single transaction. The server may determine dependencies that are required for a patch. For each target of the patch, the server identifies which of these dependencies should be installed or updated. For each target that lacks the required dependencies, the server further sends, along with the patch data, data and/or instructions that cause the target to install or update the requisite dependencies.

Claims

1. A method comprising:

a server identifying a plurality of patches;

the server identifying a plurality of targets to which the plurality of patches are to be applied;

the server pushing data indicating the plurality of patches to each of the plurality of targets;

at each particular target of the plurality of targets, based on the pushed data, applying the plurality of patches;

wherein the method is performed by a plurality of computing devices in a distributed system comprising the server and the plurality of targets.

2. The method of claim 1, wherein:

two or more patches of the plurality of patches must be applied, at least partially, while the particular target is offline; and

applying the plurality of patches comprises bringing the particular target offline no more than once while the plurality of patches are applied.

3. The method of claim 1, wherein pushing data indicating the plurality of patches to each of the plurality of targets occurs without one or more of the plurality of targets having requested patching.

4. The method of claim 1, further comprising:

for each particular target of one or more targets in the plurality of targets;

the server identifying one or more dependencies required for applying the plurality of patches;

the server pushing dependency data indicating the one or more dependencies to the particular target along with the data indicating the plurality of patches;

the target installing the one or more dependencies based on the dependency data.

5. The method of claim 1,

wherein applying the plurality of patches comprises applying a particular patch at a particular target of the plurality of targets;

wherein applying the particular patch is performed by a patching tool;

wherein the method further comprises, prior to applying the patch;

the server pushing dependency data to the particular target along with the particular patch;

the target updating the patching tool based on the dependency data.

6. The method of claim 1, further comprising, for each particular target of one or more targets in the plurality of targets, sending credential data to particular target, the credential data being required by the particular target for performing one or more actions necessary to apply the plurality of patches to the particular target.

7. The method of claim 1, wherein identifying the plurality of targets comprises the server selecting, from a set of all targets in the distributed system, a subset of targets that are compatible with the plurality of patches.

8. The method of claim 7, further comprising:

each target in the set of all targets sending, to a central repository, metadata describing one or more properties of said target;

wherein selecting the subset of targets comprises consulting the metadata in the central repository.

9. The method of claim 1, wherein each target of the plurality of targets is a different instance of a same application.

10. The method of claim 1, wherein:

two or more of the plurality of targets operate in a single shared disk environment;

the plurality of patches target a particular target application;

the two or more targets of the plurality of targets each execute a separate instance of the particular target application, each separate instance being invoked from shared files in the shared disk environment;

applying the plurality of patches comprises;

at each particular target of the plurality of targets, a first target of the two or more targets terminating each separate instance of the target application;

the first target modifying the shared files in accordance with the plurality of patches; and

the first target re-invoking each separate instance;

wherein the other targets of the two or more targets do not modify the shared files in accordance with the plurality of patches.

11. The method of claim 1, wherein applying the plurality of patches comprises applying each patch in the plurality of patches successfully at a first target and applying at least one patch in the plurality of patches unsuccessfully at a second target, the method further comprising, at each particular target of the plurality of targets:

if each of the plurality of patches is applied successfully, then sending a message indicating that the plurality of patches was applied successfully;

if any one of the plurality of patches is not applied successfully, then (a) reverting any patches in the plurality of patches that were not applied successfully and (b) sending a message indicating that the plurality of patches was not applied successfully.

12. One or more storage media storing instructions which, when executed by one or more computing devices, cause performance of:

a server identifying a plurality of patches;

the server identifying a plurality of targets to which the plurality of patches are to be applied;

the server pushing data indicating the plurality of patches to each of the plurality of targets;

at each particular target of the plurality of targets, based on the pushed data, applying the plurality of patches;

wherein the method is performed by a plurality of computing devices in a distributed system comprising the server and the plurality of targets.

13. The one or more storage media of claim 12, wherein:

two or more patches of the plurality of patches must be applied, at least partially, while the particular target is offline; and

attempting to apply the plurality of patches comprises bringing the particular target offline no more than once while the plurality of patches are applied.

14. The one or more storage media of claim 12, wherein pushing data indicating the plurality of patches to each of the plurality of targets occurs without one or more of the plurality of targets having requested patching.

15. The one or more storage media of claim 12, wherein the instruction, when executed by the one or more computing devices, further cause performance of:

for each particular target of one or more targets in the plurality of targets;

the server identifying one or more dependencies required for applying the plurality of patches;

the server pushing dependency data indicating the one or more dependencies to the particular target along with the data indicating the plurality of patches;

the target installing the one or more dependencies based on the dependency data.

16. The one or more storage media of claim 12, wherein the instruction, when executed by the one or more computing devices, further cause performance of, for each particular target of one or more targets in the plurality of targets, sending credential data to particular target, the credential data being required by the particular target for performing one or more actions necessary to apply the plurality of patches to the particular target.

17. The one or more storage media of claim 12, wherein identifying the plurality of targets comprises the server selecting, from a set of all targets in the distributed system, a subset of targets that are compatible with the plurality of patches.

18. The one or more storage media of claim 17, wherein the instruction, when executed by the one or more computing devices, further cause performance of:

each target in the set of all targets sending, to a central repository, metadata describing one or more properties of said target;

wherein selecting the subset of targets comprises consulting the metadata in the central repository.

19. The one or more storage media of claim 12, wherein:

two or more of the plurality of targets operate in a single shared disk environment;

the plurality of patches target a particular target application;

the two or more targets of the plurality of targets each execute a separate instance of the particular target application, each separate instance being invoked from shared files in the shared disk environment;

applying the plurality of patches comprises;

at each particular target of the plurality of targets, a first target of the two or more targets terminating each separate instance of the target application;

the first target modifying the shared files in accordance with the plurality of patches; and

the first target re-invoking each separate instance;

wherein the other targets of the two or more targets do not modify the shared files in accordance with the plurality of patches.

20. The one or more storage media of claim 12, wherein applying the plurality of patches comprises applying each patch in the plurality of patches successfully at a first target and applying at least one patch in the plurality of patches unsuccessfully at a second target, the method further comprising, at each particular target of the plurality of targets:

if each of the plurality of patches is applied successfully, then sending a message indicating that the plurality of patches was applied successfully;

if any one of the plurality of patches is not applied successfully, then (a) reverting any patches in the plurality of patches that were not applied successfully and (b) sending a message indicating that the plurality of patches was not applied successfully.