Thanks Shyam, Darren, and Matt. VERY useful information. I'll share with
our tools team (our folks who manage Netcool).
At this point, even if we could get a compatible gateway client (or
test/prove that the current client actually will work with 7.x), , we don't
have enough time for testing necessary for the 7.x upgrade. My users are
swamped with new business - and will be for the foreseeable future
(months).
For us, we can live with the DST issue, upgrade from 6.0 to 6.3 and break
FTS, or upgrade to ARS 7 with limited/no UAT and hope that no problems are
uncovered (or that we can identify and dispose of them quickly).
I'm pushing BMC a little harder for both a 6.0 patch as well as a more
specific description of what will and what will not work properly after the
DST change on 03/11 on a pre-DST-fix release (such as our 6.0.1, patch
1398). So far, I've only discovered that our Account Manager no longer
works for BMC.
BMC's impact statement is very bland/non-descriptive - "Certain scheduled
workflow rules may not fire. Time may be off by 1 hour.".
David Easter's input acknowledges that "There is a library within AR System
that does not use the system clock to make its DST calculations", but
further qualifies it with "The library in question is used by some
auxiliary functions within AR System (e.g. the API and parts of the
Mid-Tier)." To be fair, he also added that BMC is doing dome additional
testing.
As of 02:00 this morning, we have less than 2 months until the change.
Mike White
Office: 813-978-2192
E-mail: [EMAIL PROTECTED]
"Shyam Attavar"
<[EMAIL PROTECTED] To: [email protected]
L.NET> cc:
Sent by: "Action Subject: Re: Daylight savings
time and Remedy system restarts
Request System
discussion
list(ARSList)"
<[EMAIL PROTECTED]
ORG>
01/10/2007 17:36
Please respond to
arslist
Mike,
One other thing I would also keep an eye on - connecting from an older (pre
7.x) version of the AR API to a 7.x version of the AR Server, there have
been reports of memory leaks where the memory of the AR Server grew
drastically in a very short period of time. The memory leaks may or may not
impact your environment based on the number of records created in Remedy
from Netcool. I did get confirmation from BMC Support that this was
actually
an issue on certain flavors of *NIX. Later on, I was also told by BMC
Support that these are now fixed and available in a 7.x AR Server patch.
However, I have not really tested this yet.
Also, I have an oustanding call with Micromuse (IBM) for getting an updated
version of the Remedy Gateway, just to be on the safe side and I recently
heard that there may be a newer version of the Netcool Gateway compiled
against the 7.x AR API. In any case, I would like to get my hands on the
new
gateway and the latest patch with the memory leak fix to test it on a
sandbox/test environment before proceeding any further.
HTH,
--
Shyam
----- Original Message -----
From: "Mike White" <[EMAIL PROTECTED]>
Newsgroups: gmane.comp.crm.arsystem.general
Sent: Wednesday, January 10, 2007 9:53 AM
Subject: Re: Daylight savings time and Remedy system restarts
> David. Easter, listers,
>
> I'd like to throw another log on this fire.
>
> We're ARS 6.0.1 users. We also use Full Text Search (FTS) as well
as
> a Netcool/Remedy bi-directional gateway. FTS is not available in ARS
6.3,
> and is re-introduced in ARS 7.0. The problem is that the most-current
> supported Remedy release for the Netcool gateway is ARS 6.3. Catch-22.
>
> ARS 6.0 is still supported - and will be until ARS 7.5 is released
> (well past the 03/11 time change), right?
>
> I've sent this to my account manager asking for his help or to
> escalate. Do any of you have any more insight in this area?
>
> Mike White
> Office: 813-978-2192
> E-mail: [EMAIL PROTECTED]
>
>
>
> "Easter, David"
> <[EMAIL PROTECTED] To:
> [email protected]
> .COM> cc:
> Sent by: "Action Subject: Re: Daylight
> savings time and Remedy system restarts
> Request System
> discussion
> list(ARSList)"
> <[EMAIL PROTECTED]
> ORG>
>
>
> 01/05/2007 16:04
> Please respond to
> arslist
>
>
>
>
>
>
> **
>> That means we are immune to daylight savings time problems.
>
> Patch 020 should still be loaded on 6.03 systems. As previously posted,
> if
> the patch is not loaded, the time calculations of operations that occur
on
> days between the new DST date and the old DST date may be off by one hour
> depending on where in the system the time is calculated. There is a
> library within AR System that does not use the system clock to make its
> DST
> calculations. The patch updates this library to conform to the new DST
> rules put forward by the Bush administration in 2005. Since the AR
System
> server itself does use the system clock, many customers may be unaffected
> by the DST change. The library in question is used by some auxiliary
> functions within AR System (e.g. the API and parts of the Mid-Tier).
>
> BMC is doing some additional testing to determine what operations within
> AR
> System would be affected were customers not to load the patch. Once that
> information is compiled, a notice will be sent to AR System customers and
> made available as a Technical Bulletin.
>
> You are correct that you would not be affected by the secondary issue of
> workflow not firing during the actual change over to DST (2am - 3am) -
> since the server would be turned off anyway. I would strongly recommend
> testing your configuration in a lab environment to see the full effects
of
> not loading AR System 6.03 Patch 020 if you choose not to load it.
>
> Thanks,
>
> -David J. Easter
> Sr. Product Manager, Service Management Business Unit
> BMC Software, Inc.
>
> From: Action Request System discussion list(ARSList)
> [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook
> Sent: Friday, January 05, 2007 12:36 PM
> To: [email protected]
> Subject: Re: Daylight savings time and Remedy system restarts
>
> **
> Unless there are escalations that run during that hour (2:00 - 3:00 am)
> that is either duplicated or not encountered at all. As an aside, this
> would include database backups, sync scripts with AD or other outside
data
> sources, etc.
>
> So if you shut it down at say, 1:00 am to do a Db backup that ran from
> 1:15
> to 1:45 am, then didn't restart until after 3:00, I think you'd probably
> be
> in the clear. Someone can correct me if I'm wrong.
>
> Rick
>
> On 1/5/07, Dwayne Martin <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I understand from past discussions (see "Daylight savings time
> again") that there may or may not be problem with Remedy and
> daylight savings time, but patches are on the way.
>
> Every morning we shut down our Remedy system in order to back
> up the database. Then we restart the system. My guess/hope
> is that when we restart the system, Remedy will set its clock
> by the computer clock, and as long as the computer clock is
> right, Remedy should be too. That means we are immune to
> daylight savings time problems.
>
> Am I right?????
>
> ARS 6.3 patch 014, HPUX 11 db, Oracle 9.2 db
>
> Dwayne Martin
> Computing Support
> James Madison University
> __20060125_______________________This posting was submitted with HTML in
> it___
> __20060125_______________________This posting was submitted with HTML in
> it___
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
