Hey everyone,
I'm the one who originally posted this subject.
I installed 4.1 and applied the 4.1.2 patch.
Then I restored the 3.7.2.database.
My TSM server would't start. I ran an AUDITDB with FIX=NO and got the following
message:
ANR6646I AUDITDB: Auditing disaster recovery manager definitions.
ANR4210I AUDITDB: Auditing physical volume repository definitions.
ANR9999D tb.c(775): Column count mismatch for table MMS.Drives - expected 21,
found 16
ANR0101E pvraudit.c(233): Error 18 opening table "MMS.Drives".
ANR4142I AUDITDB: Database audit process terminated in error.
I then tried the FIX=YES option and it still didn't work.
As a last resort I did a DSMSERV UPGRADEDB..........
It works fine now!!
Thanx everyone,
Jerry Caupain
>>> jon AT IN2P3 DOT FR 01/15/01 04:25pm >>>
Now _there_ is a good idea. Thanks once again, Richard. John
Richard Sims wrote:
> >...Our method of upgrading has always been to install the new
> >version on a new machine, test it thoroughly, then to backup the DB on the
> >old
> >machine and restore it on the new one. This has the _enormous_ advantage
> >that
> >if anything goes wrong, we have only to turn the old machine back on and
> >we're
> >in business again, with a minimal loss of time.
>
> John - Proceeding carefully on a new machine is an excellent approach.
> Given that the approach requires the same amount of db,log space on
> both systems, an alternative to TSM db backup/restore would be to configure
> the db,log space on the two systems to be equivalent, and then do a physical
> copy of the db,log space to the other system, where the dsmserv start-up on
> the new machine will upgrade the db. This should be much faster than a
> logical db backup/restore, and a 3.7 CD would not be an issue.
> Richard Sims, BU
--
________________________________________________________________
________________________________________________________________
| John O'Neall | |
| Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 |
| Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
|
