That may be a sensible thing to do.. You do not want escalations to be
firing when that process is running. Since it’s a Remedy native wizard, you
do not have the luxury of completely shutting down the Remedy server. When I
had done this using a DB script I had that luxury..
Joe
-----Original Message-----
From: Boyd, Rebecca
Sent: Thursday, June 16, 2011 9:26 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: Re: Bulk Change of login ID
Did you disable escalations first? I think the official instructions say to
do that.
On Thu, Jun 16, 2011 at 8:38 AM, Michael Burton
<[email protected]> wrote:
**
Morning all,
Just an update on this, I've tested a login ID change using the Data
Wizard
Console on our development platform, and it's a non-starter. I kicked it
off
on Tuesday at around 11:00hrs, and it's still running. Thinking it might
be
that our dev platform is not exactly built for performance, I also ran the
same test for a single user on our Prod system, kicking this off at
17:30hrs
yesterday - that is also still running :(
More investigation required as that doesn't seem quite right to me, as we
have no performance issues on our prod platform, in fact, when we brought
it
in to service. the performance of our boxes actually caused a problem
because they were too fast - this was related to rebuilding Service
Targets
and associated milestones.
Cheers
-
Mike
_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_
--
Rebecca Boyd
Application Administrator
Wake Forest University
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
