This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
I did some extensive searching here:
http://www-10.lotus.com/ldd/46dom.nsf?OpenDatabase
as/400 upgrade
as400 upgrade
iseries upgrade
and, while I got lots of hits, I didn't see any with a close similar
situation.  I didn't seem to have the problem you are having with the 4.6
-> 5 upgrade.  I have had some upgrades do funny things to my
/QIBM/UserData/LOTUS/LOTUS_SERVERS file.  It changed it from one command
per line to multiple.  I had to parse that out by hand.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Nathan Simpson" <nathansimpson@optusnet.com.au>
Sent by: domino400-admin@midrange.com
07/14/2002 06:48 AM
Please respond to domino400


        To:     <DOMINO400@midrange.com>
        cc:
        Fax to:
        Subject:        Upgrade from 4.6 to 5.0.10 gone wrong


Hi,

We upgraded from 4.6b to 5.0.10 on our V4R5 AS/400 and things seemed to go
wrong.

I know 4.6 wasn't supported on V4R5 but it was working OK for us until we
could upgrade to R5.

We performed all of the preliminary work such as backups, preparation for
AnyMail integration etc.

We ran LODRUN as instructed and chose to install all options except the
Advanced option. Things seemed to go ok except we weren't asked to accept
any license agreement as the documentation mentioned and I never saw a
screen saying it was upgrading our existing server.

The installation completed without any errors so I assumed all was ok.

I tried to start our server with 'strdomsvr server-name' but it came back
with an 'error 8' unknown server name.

Our existing server didn't seem to exist on the system anywhere.

I created a new server, *first, pointing to our old servers information
and
finally managed to get things going.

I have very little Domino experience but this was the only way I could get
it going.

As I say I got our server going but many of the databases weren't upgraded
to the new template designs.

I tried to manually upgrade the Domino Directory to the R5 template
design.
I did a database design replace and it only seemed to take about 1 second
and the design was the same.

Upon further investigation is seems that the template was still the R4
template and the R5 template didn't exist on the AS/400 system. I found
another R5 system (5.0.9) and copied the R5 template across and then did
the
upgrade. It upgraded without a problem.

None of the mail.box, smtp.box were upgraded to the new designs either and
neither were they on the AS/400 system.

What could have gone wrong? Is it ok to install the Domino software over
the
top again?

Could I delete our Domino server (remove the licensed program) and then
reinstall and put our cert.id and names.nsf and mail files in and then
have
a brand new R5 Domino server. If so would this be the best solution?

 I don't know what happened or what would be the best way to fix this. Our
server is up and running but I don't feel that it is running much of the
new
version template designs.

And by the way in DSPSFWRSC it says the version number is V5R1M0 as the
documentation says it should.

TIA

Nathan Simpson
nathan@awh.com.au

_______________________________________________
This is the Lotus Domino on the iSeries / AS400 (DOMINO400) mailing list
To post a message email: DOMINO400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/domino400
or email: DOMINO400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/domino400.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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.