It's running on Solaris (library=ADIC scalar 100, drive=sony)
Server Version 4, Release 2, Level 1.15
we are running two servers on one box. and I fond the messsages below on the master
server.
When I checked the ADIC library, drive0/6/9/13 were off.
tsm: SM058>q dr f=d
Drive Name: DRIVE0 Device: /dev/rmt/1mt
Drive Name: DRIVE1 Device: /dev/rmt/2mt
Drive Name: DRIVE10 Device: /dev/rmt/12mt
Drive Name: DRIVE11 Device: /dev/rmt/11mt
Drive Name: DRIVE12 Device: /dev/rmt/14mt
Drive Name: DRIVE13 Device: /dev/rmt/13mt
Drive Name: DRIVE14 Device: /dev/rmt/16mt
Drive Name: DRIVE15 Device: /dev/rmt/15mt
Drive Name: DRIVE16 Device: /dev/rmt/18mt
Drive Name: DRIVE17 Device: /dev/rmt/17mt
Drive Name: DRIVE18 Device: /dev/rmt/20mt
Drive Name: DRIVE19 Device: /dev/rmt/19mt
Drive Name: DRIVE2 Device: /dev/rmt/3mt
Drive Name: DRIVE3 Device: /dev/rmt/4mt
Drive Name: DRIVE4 Device: /dev/rmt/5mt
Drive Name: DRIVE5 Device: /dev/rmt/6mt
Drive Name: DRIVE6 Device: /dev/rmt/8mt
Drive Name: DRIVE7 Device: /dev/rmt/7mt
Drive Name: DRIVE8 Device: /dev/rmt/9mt
Drive Name: DRIVE9 Device: /dev/rmt/10mt
ROOT:/dev/rmt # for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
> do mt -f /dev/rmt/${i}mt status
> done
/dev/rmt/1mt: Unknown error
/dev/rmt/2mt: Resource temporarily unavailable
/dev/rmt/3mt: Resource temporarily unavailable
/dev/rmt/4mt: Resource temporarily unavailable
/dev/rmt/5mt: Resource temporarily unavailable
/dev/rmt/6mt: Resource temporarily unavailable
/dev/rmt/7mt: Resource temporarily unavailable
/dev/rmt/8mt: Unknown error
/dev/rmt/9mt: Resource temporarily unavailable
/dev/rmt/10mt: Unknown error
/dev/rmt/11mt: Resource temporarily unavailable
mt: Invalid argument
/dev/rmt/13mt: Unknown error
/dev/rmt/14mt: Resource temporarily unavailable
mt: Invalid argument
/dev/rmt/16mt: Resource temporarily unavailable
/dev/rmt/17mt: Unknown error
/dev/rmt/18mt: Resource temporarily unavailable
/dev/rmt/19mt: Resource temporarily unavailable
/dev/rmt/20mt: Resource temporarily unavailable
burak.demircan@DAIMLERC
HRYSLER.COM To: [EMAIL PROTECTED]
Sent by: cc:
[EMAIL PROTECTED] Subject: Re: Please help me
------ ANR9999D & ANR2121W alert?
23/05/2002 21:43
Please respond to
ADSM-L
what is your tsm version?
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
23.05.2002 15:40
Please respond to ADSM-L
To: [EMAIL PROTECTED]
cc:
Subject: Please help me ------ ANR9999D & ANR2121W
alert?
Hi, All
I rebooted TSM server around 3 pm as the servers were dead with some reason.
But unusally I've to 4 unavailable drives as soon as rebooted, which I've
never seen before.
And I tried to update all the unavailable drives.....then "q dr" command hung
up and makes netcool alerts continuously.
I know 9999 is critical message but in this case I don't know how to respond.
The set of messages below has been repeating since the reboot.....worried....T_T
ANR2017I Administrator QUERY issued command: QUERY DRIVE
ANR9999D mmstxn.c(219): ThreadId<104> Lock acquisition (sLock) failed for MMS
universe lock.
ANR2033E QUERY DRIVE: Command failed - lock conflict.
Could it have a bad impact on backup process tonight?
Also this attention alert is also my concern.
Does that mean "backup db" schedule finished with failure and I need to run
it manually now?
tsm: SM057>q act search='ATTENTION' begint=-04:00
Date/Time Message
--------------------
----------------------------------------------------------
05/23/02 16:58:12 ANR2121W ATTENTION: More than 1553.95 MB of the
database
has changed and the last database backup was more than
24
hours ago. Use the BACKUP DB command to provide for
database recovery.
05/23/02 17:58:12 ANR2121W ATTENTION: More than 1553.95 MB of the
database
has changed and the last database backup was more than
24
hours ago. Use the BACKUP DB command to provide for
database recovery.
05/23/02 18:58:12 ANR2121W ATTENTION: More than 1553.95 MB of the
database
has changed and the last database backup was more than
24
hours ago. Use the BACKUP DB command to provide for
database recovery.
05/23/02 19:58:12 ANR2121W ATTENTION: More than 1554.08 MB of the
database
has changed and the last database backup was more than
24
hours ago. Use the BACKUP DB command to provide for
database recovery.
Thanks in advance,
Meensun
--
This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
