Is this info helpful?
weboadsm: / # lsvg
rootvg
clariion_hd3
clariion_hd4
clariion_hd5
clariion_hd6
clariion_hd2
weboadsm: / # lsvg -L clariion_hd3
VOLUME GROUP: clariion_hd3 VG IDENTIFIER: 00002922ae030c06
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 476 (7616
megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 2 USED PPs: 476 (7616
megabytes)
OPEN LVs: 2 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
weboadsm: / # lsvg -L clariion_hd2
VOLUME GROUP: clariion_hd2 VG IDENTIFIER: 000029224f7a5c39
VG STATE: active PP SIZE: 64 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 521 (33344
megabytes)
MAX LVs: 256 FREE PPs: 1 (64 megabytes)
LVs: 2 USED PPs: 520 (33280
megabytes)
OPEN LVs: 2 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
weboadsm: / # lsvg -L clariion_hd4
VOLUME GROUP: clariion_hd4 VG IDENTIFIER: 00002922ae035f75
VG STATE: active PP SIZE: 16 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 476 (7616
megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 2 USED PPs: 476 (7616
megabytes)
OPEN LVs: 2 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
weboadsm: / # lsvg -L clariion_hd5
VOLUME GROUP: clariion_hd5 VG IDENTIFIER: 00002922ae03ecee
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 923 (236288
megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 10 USED PPs: 923 (236288
megabytes)
OPEN LVs: 10 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
weboadsm: / # lsvg -L clariion_hd6
VOLUME GROUP: clariion_hd6 VG IDENTIFIER: 00002922ae042985
VG STATE: active PP SIZE: 256 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 461 (118016
megabytes)
MAX LVs: 256 FREE PPs: 0 (0 megabytes)
LVs: 5 USED PPs: 461 (118016
megabytes)
OPEN LVs: 5 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 32
Marc Levitan
Storage Manager
PFPC Global Fund Services
"Davidson,
Becky" To: [EMAIL PROTECTED]
<Becky.Davidson cc:
@SLBG.COM> Subject: Re: server won't come back up!
Sent by: "ADSM:
Dist Stor
Manager"
<[EMAIL PROTECTED]
ST.EDU>
03/04/2002
01:33 PM
Please respond
to "ADSM: Dist
Stor Manager"
vary on/off volume_name wait=yes/no
Try doing a lsvg -p on the volume groups that contain your tsm db and log
volumes to make sure that the volumes are available. Did you boot the box
between the shutdown and start up of TSM?
Becky
-----Original Message-----
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 12:09 PM
To: [EMAIL PROTECTED]
Subject: Re: server won't come back up!
What is the syntax for the ADSM VARY ON command?
I think I might have to manually start the lun.
Marc Levitan
Storage Manager
PFPC Global Fund Services
"PINNI,
BALANAND To: [EMAIL PROTECTED]
(SBCSI)" cc:
<[EMAIL PROTECTED] Subject: Re: server won't come
back up!
OM>
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
RIST.EDU>
03/04/2002
11:09 AM
Please
respond to
"ADSM: Dist
Stor Manager"
If u did not extend db that should not matter to come up .I think u need to
use dsmserv audit db cmd line with fix=yes option.
-----Original Message-----
From: Marc Levitan [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 04, 2002 9:57 AM
To: [EMAIL PROTECTED]
Subject: server won't come back up!
I get the following message when trying to start the TSM server:
weboadsm: /usr/tivoli/tsm/server/bin # 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.
ANR0259E Unable to read complete restart/checkpoint information from any
database or recovery log volume.
weboadsm: /usr/tivoli/tsm/server/bin #
The only thing that I can think of is that I added space(defined and
extended) to the RECOVERY log. I also DEFINED additional space for my
database but have NOT yet actually extended the database to use the new
space.
Do I have to somehow show TSM my changes???
Does anyone have more info on the ANR0259E error?
Thanks,
Marc Levitan
Storage Manager
PFPC Global Fund Services
