ADSM-L

Re: Upgrade

2000-11-17 13:04:45
Subject: Re: Upgrade
From: Andy Hynes <andrewhynes AT CHUBB DOT COM>
Date: Fri, 17 Nov 2000 17:56:17 +0000
Have you tried defining them as ADSM devices (thru smit option if I
remember correctly) - I think that was how I did it but
it wa 2 years ago and I've not got a manual !!!

Andy




Shekhar Dhotre <Shekhar.Dhotre.B AT BAYER DOT COM>@VM.MARIST.EDU> on 17/11/2000
17:44:23

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  Re: Upgrade


Hi  rebooted the  AIX box , now rmt1 and rmt2 are available and mt0 and mt1
defined ,
how to make them available ? tried adding throgh smit -Tivoli storage
manager
-tape
gives following error.
gives following error.

Command: failed        stdout: yes           stderr: no

Before command completion, additional instructions may appear below.

Method error (/etc/methods/cfgadsmdd):
        0514-047 Cannot access a device.
cfgadsmdd[get_i]: ioctl SCIO(L)INQU first call failed, retry if possible,
errno
= 19
cfgadsmdd[get_i]: SCIO(L)INQU failed w/ unretriable errno=19.
cfgadsmdd[inq..]: free dds.
cfgadsmdd[main ]: error inquiry or building dds,rc=47



medrs2:lsdev -Cc tape
lsdev: 0514-521 Cannot find information in the predefined device
        configuration database for the customized device mt0.
lsdev: 0514-521 Cannot find information in the predefined device
        configuration database for the customized device mt1.
rmt0 Available 10-60-00-5,0 SCSI 4mm Tape Drive
mt0  Defined   20-60-00-3,0 N/A
mt1  Defined   20-60-00-4,0 N/A
rmt1 Available 20-60-00-3,0 Other SCSI Tape Drive
rmt2 Available 20-60-00-4,0 Other SCSI Tape Drive




"DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" on 11/17/2000
11:50:29 AM
Please respond to "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" 
@
X400
To: "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us"@X400
cc:

Subject: Re: Upgrade

        I'm not sure if your cut and paste is truncating, but see   mt0
and mt1      it is not prefixed with 'r'....
        step 1).  maybe rmdev -dl mt0   and    rmdev -dl mt1
        followed by a cfgmgr
        may do it?
        I'll assume that the lsdev -Cc tape indicated device names of rmt0,
mt0 and mt1....
        maybe go ahead and rmdev -dl rmt0 too on step 1....
        FYI Thanks Tim




        Shekhar Dhotre <Shekhar.Dhotre.B AT BAYER DOT COM>
        11/17/2000 10:37 AM
        Please respond to "ADSM: Dist Stor Manager"
<ADSM-L AT VM.MARIST DOT EDU>@SMTP@Exchange
        To:     ADSM-L AT VM.MARIST DOT EDU@SMTP@Exchange
        cc:

        Subject:        Re: Upgrade

         The problem is with rmt1 and rmt2 drives , they are not available
to system
        (AIX) , but mt0 , and mt1 are ..
          So i amtrying to remove rmt1 and rmt2  , but  unable to do so ...
notching my
        hairs  ....
        medrs2:lsdev -Cc tape
        lsdev: 0514-521 Cannot find information in the predefined device

              configuration database for the customized device mt0.

        lsdev: 0514-521 Cannot find information in the predefined device
                configuration database for the customized device mt1.


        rmt0 Available 10-60-00-5,0 SCSI 4mm Tape Drive
        mt0  Available 20-60-00-3,0 N/A
        mt1  Available 20-60-00-4,0 N/A
        medrs2:rmdev -dl mt0
        rmdev: 0514-521 Cannot find information in the predefined device
                configuration database for the customized device mt0.

        medrs2:rmdev -dl mt1
        rmdev: 0514-521 Cannot find information in the predefined device
                configuration database for the customized device mt1.

        medrs2:odmdelete -q name=rmt1 -o CuAt
        0518-307 odmdelete: 0 objects deleted.

        medrs2:set -o vi

        medrs2:odmdelete -q name=rmt1 -o CuDv
        0518-307 odmdelete: 0 objects deleted.
        medrs2:odmdelete -q value3=rmt1 -o CuDvDr
        0518-307 odmdelete: 0 objects deleted.


        medrs2:cfgmgr
        cfgmgr: 0514-612 Unable to configure the mt0 device because
                it either does not exist in the customized device database
or it does no
        t
                have a corresponding entry in the predefined device
database.
        cfgmgr: 0514-612 Unable to configure the mt1 device because
                it either does not exist in the customized device database
or it does no
        t
                have a corresponding entry in the predefined device
database.

        medrs2:id
        uid=0(root) gid=0(system)
groups=2(bin),3(sys),7(security),8(cron),10(audit)
        medrs2:odmget CuAt | grep mt0
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"
                name = "rmt0"

        medrs2:errpt
        IDENTIFIER TIMESTAMP  T C RESOURCE_NAME  DESCRIPTION
        5DFED6F1   1116153600 I O SYSPFS         UNABLE TO ALLOCATE SPACE
IN
FILE SYSTEM
        369D049B   1112150900 I O SYSPFS         UNABLE TO ALLOCATE SPACE
IN
FILE SYSTEM



        shekhar ..







        "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" on
11/17/2000
10:04:44 AM
        Please respond to "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A=
/C=us" @ X400
        To: "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us"@X400
        cc:

        Subject: Re: Upgrade

        THose messages come from a communications problem somewhere between
TSM,
        ssi, and ACSLS.

        *       Make sure that ACSLS is up and you can talk with it via
cmd_proc.

        *       Then make sure that the ssi and mini-el tasks are up.  Make
sure
        they can talk with ACSLS by running lbtest.

        *       If they are OK, then stop and restart TSM.

        *       If you still get those errors, call support.



        > -----Original Message-----
        > From: Joshua S. Bassi [SMTP:jbassi AT IHWY DOT COM]
        > Sent: Thursday, November 16, 2000 5:39 PM
        > To:   ADSM-L AT VM.MARIST DOT EDU
        > 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.
        >
        >
        >
        >
        >
        > "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/P=Internet/A= /C=us" on
11/16/2000
        > 05:18:27 PM
        > Please respond to "DDA.RFC-822=ADSM-L AT VM.MARIST DOT 
EDU/P=Internet/A=
/C=us" @
        > X400
        > To: "DDA.RFC-822=ADSM-L AT VM.MARIST DOT EDU/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
        > jbassi AT ihwy DOT com
        >
        > -----Original Message-----
        > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On
Behalf Of
        > Shekhar Dhotre
        > Sent: Thursday, November 16, 2000 2:00 PM
        > To: ADSM-L AT VM.MARIST DOT EDU
        > 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.
<Prev in Thread] Current Thread [Next in Thread>