And the real question is why do we sometimes have to do the upgradedb step
and sometimes it happens automagically?
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (719) 260-5991
Email: [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
France, Don G (Pace)
Sent: Thursday, November 16, 2000 4:37 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM 3.7.4.0 Servers Are Out
We've been running 3.7.4 on Solaris for about a month without noticeable
problems; so, we upgraded an AIX box from 3.7.3 to it this past Tuesday,,,
all is going well, so I am now preparing to do it on Win2k server. We need
the fixes for expiration and server crashes we were getting on 3.7.3.
I wonder if things went awry because he tried to start the server without
doing upgradedb at the outset!?! (Sometimes they forget to test the obvious
human-error scenarios.) To confirm that, just restore back to the original
level, re-run smitty to redo the upgrade, but remember to do the upgradedb
1st thing after install.
Don France
Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:[EMAIL PROTECTED]
PACE - http://www.pacepros.com
Bus-Ph: (408) 257-3037
-----Original Message-----
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 16, 2000 2:43 PM
To: [EMAIL PROTECTED]
Subject: TSM 3.7.4.0 Servers Are Out
Shekhar,
So from your email we can see that the 3.7.4.0 servers are out. Hopefully
your upgrade problem isn't an indication of the reliability of the new
code. I think I'll take a wait-and-see attitude.
--
Joshua S. Bassi
IBM Certified- AIX Support, HACMP, SAN
Enterprise Disk(Shark)& Tape Solutions
Tivoli Certified Consultant - ADSM/TSM
[EMAIL PROTECTED]
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Shekhar Dhotre
Sent: Thursday, November 16, 2000 2:29 PM
To: [EMAIL PROTECTED]
Subject: Re: Upgrade
TSM server started but getting following error ..
ANR0916I TIVOLI STORAGE MANAGER distributed by Tivoli is now ready for use.
TSM:TSM>
11-16-00 17:14:32 none[0]:
cl_ipc_write: Sending message to socket 50004 failed on "Error 0"
11-16-00 17:14:52 none[0]:
cl_inform: Sending message to socket 50004 failed on "Error 0"
11-16-00 17:15:02 none[0]:
acs_ipc_write: FATAL_ERROR! cl_ipc_write() failed.
11-16-00 17:15:12 none[0]:
acs_ipc_write: FATAL_ERROR! cl_ipc_write() failed.
"[EMAIL PROTECTED]/P=Internet/A= /C=us" on 11/16/2000
05:18:27 PM
Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @
X400
To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400
cc:
Subject: Re: Upgrade
Issue# dsmserv upgradedb
--
Joshua S. Bassi
IBM Certified- AIX Support, HACMP, SAN
Enterprise Disk(Shark)& Tape Solutions
Tivoli Certified Consultant - ADSM/TSM
[EMAIL PROTECTED]
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Shekhar Dhotre
Sent: Thursday, November 16, 2000 2:00 PM
To: [EMAIL PROTECTED]
Subject: Upgrade
Hi all i just applied patch for Tivoli Storage manager .
to upgrade from 3.7.2 to 3.7.4 , and tried to restart the server
gives following error. where and how i should use UPGRADEDB command?
# dsmserv
ANR7800I DSMSERV generated at 09:50:09 on Oct 17 2000.
Tivoli Storage Manager for AIX-RS/6000
Version 3, Release 7, Level 4.0
Licensed Materials - Property of IBM
5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR0900I Processing options file dsmserv.opt.
ANR0990I Server restart-recovery in progress.
ANR0200I Recovery log assigned capacity is 1100 megabytes.
ANR0201I Database assigned capacity is 500 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0983W The server database was recorded by a down-level version of the
server
program. The UPGRADEDB parameter is required to start the server and
automatically upgrade the database contents to the current server version.
Please refer to installation instructions for precautionary backup
procedures
prior to doing this.
