My Oracle Support Banner

Impact Document for Daylight Saving Time Shift for Enterprise Manager Grid Control (Doc ID 417939.1)

Last updated on MAY 27, 2021

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.2 to 10.2.0.1 [Release 10.1 to 10.2]
Information in this document applies to any platform.
Information in this document applies to any platform.

Purpose

The goal of this document is to provide information to help decide if, when and how to apply the Daylight Saving Patches. For example, if no managed nodes, OMS's or Repositories run in timezones in the United States, Canada, Australia, or other affected territories, and such targets will not be monitored in the future there is no need to apply Daylight Saving Time patches. If however targets are monitored in any an affected area, or a Repository or OMS is in an affected area, decisions will need to be made on when, and in what order, to apply Daylight Saving Time patches.

Scope

This document is aimed at users of Enterprise manager Grid Control who are considering the impact of the changes to the start and end times of DST.  It is not intended to provide patching instructions.  For our quick DST compliance guide see:

 

<Note 457792.1> Quick Start: Checking and Applying DST patches to Grid Control and it's Agents via command line

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 1 Introduction
 
 In addition see:
 1.1 If, When and How to Patch
  2 Patching the Repository and OMS
 2.1 Rolling OMS Patching
 2.2 Consistent Repository and OMS Patching
 * If the Repository or the OMS has an Agent, it may be in a different Oracle Home. If so, that Agent Oracle Home needs to be patched.
 3 Patching Managed Hosts
 3.1 Patching the Operating System
 3.2 Patching AgentsOracle recommends that all Agents in an effected timezone be patched prior to an affected period, e.g. in 2007 this was March 11. Since it may be difficult to patch all agents in large environments, the table below summarizes some of the problems expected if such agents are not patched. Agents not in an affected timezone do not need to be patched and are not considered below.
 Effects of Not Patching Agents in an Affected Timezone
 3.3 Patching Targets
 4 Delayed PatchingIt is recommended that all patches be applied before an affected period, e.g. March 11 2007. Since that may not be possible for all sites, and especially for all Agents, the following section explores the option of patching after March 11.
 4.1 Patching  after an affected period
 4.2 Patching During and Affected Period
 4.2.1 Neither the OS Nor Oracle Software is Patched.
 4.2.2 OS is Patched, Oracle Software NOT Patched
 5 Incomplete Patching
 5.1 Inconsistent OS & Oracle Home Patching
 Behavior of EM Components during an affected period
 5.2 Partial Repository and OMS's Patching
 Appendix A - Specific Daylight Saving Time Shift IssuesAll examples use the US in 2007 but the principles apply to other countries and dates
 Appendix B - Frequently Asked Questions
 Appendix C - Recommendations
 CHANGE LOG (format YYYY-MM-DD)2008-03-14 Updated for 2008 and beyond
2007-03-13 Added FAQ 21
2007-03-09 Added FAQ 20
2007-03-08 Added FAQ 19 and corrected typo in FAQ 14
2007-03-07 Added FAQ 18.
2007-03-07 Added "Do not conduct DST testing" disclaimer -
                    Already in other notes - added for clarity and uniform - impact  None


References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.