| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 942.1 | conversions | IOSG::TYLDESLEY | | Fri Jun 26 1992 13:34 | 13 |
| Andy,
To set the ball rolling, yes, I believe the Profile could be manually
converted with OA$CNV_CONVERT. Use OA$DATA:V24_PROFILE.DAT and you
might need to set the file acls after conversion. The other one to
think about is SM_ACCOUNT_TYPES.DAT which underlies the templates.
Use V24_SM_ACCOUNT_TYPES.DAT. Back up relevant files before you start.
Hope this helps. Can't comment on the overall risk in what you intend
to do.
Cheers,
DaveT
|
| 942.2 | OA$LIB:A1$POSTINSTALL.COM | UTRTSC::SCHOLLAERT | IOS: better than the real thing | Fri Jun 26 1992 13:51 | 10 |
| Andy,
Have a look at OA$LIB:A1$POSTINSTALL.COM for
partition sedding and other 3.0 post install actions...
Regards,
Jan
|
| 942.3 | CM$AUTH$USERS | CESARE::EIJS | All in 1 Piece | Fri Jun 26 1992 14:22 | 14 |
|
Andy,
IF your applications reside in the OA application areas, and your
swapping the ALL-IN-1 system disk (first time I hear about such a disk)
then there should be no implications for CM, apart from:
CM$AUTH$USERS (options CM AM MAP) -> depends on PROFIL
The dataset is new for V3.0, but the contents might differ between systems.
Ciao,
Simon
|
| 942.4 | Offically, I'd recommend the upgrade... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Jun 26 1992 17:07 | 24 |
| .2's suggestion of examining the post install command procedures to see
what it does is a good one.
You'll find that a number of conversions take place, and also various
scripts are run to populate data files.
Also a number of other conversions and ACL settings get done during the
installation, which you'll miss. You might want to review the KISETACLS
and KISETOWNS .COMs in Base saveset A and see if any of those things
need to be done after you've copied your backup across.
A number of datafiles may need to be populated with environment
specific things like disc names etc.
You're probably getting the meessage by now, that I think you should do
the upgrade again on each site. But then I write (well actually my team
do :-) ) the installation code, so the only official advice I can give
you is do it the "right" way.
However I know people who have successfully done it your way!
Good Luck,
Graham
|
| 942.5 | He who lives by the sword dies by the sword | AIMTEC::WICKS_A | DEC Mail Works for ME sometimes | Fri Jun 26 1992 17:28 | 13 |
| Andy,
What about other files that got converted during v3.0 such as ATTENDEE?
and are you sure that there aren't any differences in disknames between
the clusters - for instance if their CM stuff is on FRED$DISK on
cluster 1 will it be there on cluster 2... and then there's things
like the names of the batch queues for the File Cab Server.
Still i guess if/when it goes wrong you'll be ringing us anyhow.
Regards,
Andrew.D.Wicks
|
| 942.6 | names names names! | WOTVAX::DORANA | Mr Ken Shabby | Fri Jun 26 1992 18:34 | 9 |
| Graham,
Do you have any names that you could send me (Andy Doran @OLO) of
people who have 'sucessfully done it my way.' - I promise not to tell
them who told me...!
Cheers,
Andy
|
| 942.7 | Upgrade a COPY of the system disk? | IOSG::TALLETT | Arranging bits for a living... | Mon Jun 29 1992 09:04 | 11 |
|
Hmmm. Sounds risky to me. How about doing an upgrade on a
COPY of the system disk from each of the clusters on your
test-bed machine? You would then have to do some smaller
amount of trickery to re-integrate the system disk back
into the cluster without losing changes that happened
whilst you were doing it. Still risky IMHO, but I would
have thought it safer than thr route you were suggesting.
Regards,
Paul
|