We did not have much trouble with the upgrade either, but we hav= n't been
   using LEI too long.

   In your reading, you will come across a section about how they chan= ged
   the memory model (maybe in 6.5.3 or 6.5.4) to be more &quot   ;consistant" 
with the Domino memory model. I was warned by a CE = that
   this memory model might have problems with really large amounts of   records 
and that there is a PTF to switch back to the old memory model   .

   Now the bad part-- I can't find the PTF number. I know that I did= not
   apply it; apparently we don't access enough records.

   Tom
   =====================   ===============
   Tom Kreimer
   Information Alternatives

   -----domino400-bounces+tkreimer=infoalt.com@xxxxxxxxxxxx wrot= e:
   -----

   To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxx= m>
   From: ChadB@xxxxxxxxxxxxxxxxxxxx
   Sent by: domino400-bounces+tkreimer=infoalt.com@midrange.= com
   Date: 10/13/2005 10:53AM
   Subject: LEI 6.5.4 upgrade

   Hello all,

   We are getting ready to upgrade our iSeries Domino servers to 6.5= .4
   from 6.5.1.   I've been through the docs for the se= rver upgrade
   and am
   pretty comfortable, but i'm less comfortable with the LEI piec= e of the
   upgrade.  I'm just now reading the LEIIG.nsf document= .  Are there
   any
   common tricks or pitfalls  that you know of?  I reme= mber when we
   upgraded
   it from 5.0.11 to 6.5.1 we had to rebuild some documen= ts.
    Will everything
   migrate pretty easily with this upgrade?  Our environment= with LEI is
   pretty simple, we are bringing one DB2 customer type file into= a Domino
   app
   so that it's up to date and available.    I'm stil= l reading, so my
   questions may be answered in the doc...

   Thanks for any help!

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.