Discussion:
6.0.5 problem/migration path or ?
Craft, Robert
2005-10-26 16:51:40 UTC
Permalink
Hi folks,



We're using MM 6.0.5 to manage the operations schedule here at our data
center. Until last Friday that is, it was running flawlessly for 5 years
on a P1 w/48 meg of ram as the server. 1 user w/over 100 meg of data in
the db.



The 1st sign of a problem was the client application running on a
"normal" PC crashed w/a memory error & would not launch or sync.



Since then, I've reinstalled the client, checked that db for errors,
installed the client on the server PC, purged the db of all data older
than 5 months, reverted to older copies of the db etc. I've also tried
to get the server running on the form client PC w/o success. (that's the
short version)



The server now reports that "the server or hub is inaccessible" when the
client is run from the server PC. (swap space or memory issue?)



Any suggestions?



And more importantly:



Is it possible to import the scheduling data from 6.0.8 to the current
version and if so, by what means?



Thanks,

BobC





*******************************************
Confidentiality Notice: This e-mail message, including any attachments, from AtlantiCare contains information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED. The information is intended only for the use of the individual named above and may not be disseminated to any other party without AtlantiCare's written permission. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited.
If you have received this e-mail in error, please notify us immediately by telephone at 609 - 569 - 7070 or notify us by e-mail at ***@Atlanticare.org to arrange for the return of these documents to us without cost to you.



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Elizabeth Schwartz
2005-11-07 16:08:26 UTC
Permalink
On 10/26/05, Craft, Robert <***@atlanticare.org> wrote:

> We're using MM 6.0.5 to manage the operations schedule here at our data
> center. Until last Friday that is, it was running flawlessly for 5 years on
> a P1 w/48 meg of ram as the server. 1 user w/over 100 meg of data in the db
>

I'm not an expert but since you didn't get any answers I thought I'd take a
stab at it. What's jumping out at me is that your database is much bigger
than the amount of RAM in the machine. How much free swap space do you have?
My inclination would be to try to find something a little more recent but
running the same version of Windows (A PII with a couple hundred megs ram?)
and see if you can get it going on that...


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Craft, Robert
2005-11-11 20:17:33 UTC
Permalink
It turns out the fix was a variation of your suggestion.

The client side had an large number errors due to a bad memory module
that seemed to have been passed onto the server side.

I deleted the old server, recreated it and then imported the data from
an exported version that was purged down to only 90 days worth of data.
(the db will now undergo weekly purges in the interests of stability)

Now all I have to worry about it getting the auth code from MM since the
old one does not work.

Thanks,
BobC

________________________________

From: Meeting Maker Discussion List
[mailto:MMXP-***@LISTSERV.EMORY.EDU] On Behalf Of Elizabeth Schwartz
Sent: Monday, November 07, 2005 11:08 AM
To: MMXP-***@LISTSERV.EMORY.EDU
Subject: Re: 6.0.5 problem/migration path or ?


On 10/26/05, Craft, Robert <***@atlanticare.org> wrote:


We're using MM 6.0.5 to manage the operations schedule here at
our data center. Until last Friday that is, it was running flawlessly
for 5 years on a P1 w/48 meg of ram as the server. 1 user w/over 100 meg
of data in the db


I'm not an expert but since you didn't get any answers I thought I'd
take a stab at it. What's jumping out at me is that your database is
much bigger than the amount of RAM in the machine. How much free swap
space do you have? My inclination would be to try to find something a
little more recent but running the same version of Windows (A PII with a
couple hundred megs ram?) and see if you can get it going on that...





* MMXP-TALK Web Page:
http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML



*******************************************
Confidentiality Notice: This e-mail message, including any attachments, from AtlantiCare contains information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED. The information is intended only for the use of the individual named above and may not be disseminated to any other party without AtlantiCare's written permission. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited.
If you have received this e-mail in error, please notify us immediately by telephone at 609 - 569 - 7070 or notify us by e-mail at ***@Atlanticare.org to arrange for the return of these documents to us without cost to you.



* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Jose Luis Paredes
2005-12-06 15:23:15 UTC
Permalink
Here at Yale we perform a yearly import/export of our databases and
we keep a year's worth of data after the import. We have been doing
so for now several years and I have been asked to investigate the
risks of postponing the import/export for an yet undetermined amount
of time. As of today the databases hold close to 2 years worth of
data and we have about 5000 users running 7.5.3. Meeting Maker
mentions most companies keep 1-2 years worth of data but I need to
present the wigs with "real" risks of postponing this export. Thanks
for any info

--
"It is the unknown that defines our existence. We are constantly
searching not
just for answers to our questions but for new questions."
Benjamin Sisko


Jose Luis Paredes
System Programmer I
Yale University
Office: (203) 432.6668
http://defiant.its.yale.edu


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Joan Bryan
2005-12-06 17:06:56 UTC
Permalink
Although we have a much smaller meetingmaker base of 500 users on
one server, running 7.3.0, we have not deleted any data whilst
importing or exporting for at least 5 years. (due to management
policy). We do however delete users when they leave. The size of
the database is 100mb.



On Tue, 6 Dec 2005 10:23:15 -0500 Jose Luis Paredes
<***@YALE.EDU> wrote:

> Here at Yale we perform a yearly import/export of our databases and
> we keep a year's worth of data after the import. We have been doing
> so for now several years and I have been asked to investigate the
> risks of postponing the import/export for an yet undetermined amount
> of time. As of today the databases hold close to 2 years worth of
> data and we have about 5000 users running 7.5.3. Meeting Maker
> mentions most companies keep 1-2 years worth of data but I need to
> present the wigs with "real" risks of postponing this export. Thanks
> for any info
>
> --
> "It is the unknown that defines our existence. We are constantly
> searching not
> just for answers to our questions but for new questions."
> Benjamin Sisko
>
>
> Jose Luis Paredes
> System Programmer I
> Yale University
> Office: (203) 432.6668
> http://defiant.its.yale.edu
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

----------------------
Joan Bryan
Unix Systems Administrator
Information Systems
Kings College London


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Raoul Armfield
2005-12-07 14:48:55 UTC
Permalink
Joan Bryan wrote:
> Although we have a much smaller meetingmaker base of 500 users on
> one server, running 7.3.0, we have not deleted any data whilst
> importing or exporting for at least 5 years. (due to management
> policy). We do however delete users when they leave. The size of
> the database is 100mb.
>
>

On a related note, What if any is the impact on another user's calendar
if the deleted employee scheduled a meeting with this user?

--
Raoul Armfield
Support Specialist
IT-Call Center
rarmfield at amnh dot org
American Museum of Natural History
Central Park West at 79th Street
New York, New York 10024-5192
(212) 313-7258

5152 1277 A04B 04C2 BBE4
3EE8 8369 3541 8B93 42DA


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
Loading...