Thank you. I have not went ahead with anything yet. I was suspicious of
the dsmfmt command because there is no filname to specify with raw volumes!
I inherited 2 old ADSM servers that are using all raw vols for ADSM. I've
never had to work directly with the volumes before and the admin V3 manuals
really don't say much about them. So now would this be the correct
proceedure? Database backup already performed by the way.
1. Move Data from chosen storage pool vols
2. Vary off the volumes I have already chosen from ADSM
Storage pool vols cannot be varied off so I guess move to the next
step?
3. Delete the vols from ADSM
4. In Smitty rename the volumes to reflect new status of DB vols
instead of stg vols
5. Define db vol and copy
6. Extend DB
And it should all be happy?
Jack
-----Original Message-----
From: Cook, Dwight E [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 16, 2001 9:02 AM
To: Palmadesso Jack; [EMAIL PROTECTED]
Subject: RE: Expanding ADSM DB Using Raw Logical Volumes. help please
OOOOOOOPPPPPPPPPPPSSSSSSSSSSSSSSSSSss
with raw logical volumes you can't run dsmfmt against them...
you just do a define dbvol & define dbcopy with the /dev/rblah
I've used raw volumes in the past for db & log vols, that works...
now though, I tend to go ahead and use JFS files for db & log and raws for
storage volumes but I went through a wave of improper handling of raw
volumes in AIX 4.2, you should still be OK in aix 4.1
DWight
-----Original Message-----
From: Palmadesso Jack [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 16, 2001 7:39 AM
To: [EMAIL PROTECTED]
Subject: Expanding ADSM DB Using Raw Logical Volumes. help please
One of our older ADSM servers DB hit 98% over the weekend. I am putting
together a proceedure to grow its DB. As far as I can tell these are the
steps I need to take. First here is the hardware and software levels.
RS6k F30
ADSM 3.1.2 level 40 (has been running smooth as silk for years)upgrade to 4
in progress
AIX 4.1.5 (I know its old)
Breece Hill Q47 w/3 DLT 4000 (attached as standard SCSI Library)
All Storage pools and DB vols are on Raw Logical Volumes.
We use ADSM mirroring for DBs
These are the steps I've come up with.
1. Move Data from chosen storage pool vols
2. Vary off the volumes I have already chosen from ADSM
3. Delete the vols from ADSM
4. In Smitty rename the volumes to reflect new status of DB vols
instead of stg vols
5. Peform DSMFMT for DB on newly renamed vols.
6. Add vols (1 primary and 1 mirror) to ADSM DB
7. Extend DB
Anybody see anything wrong with these steps?
Jack Palmadesso
Siemens Westinghouse Power Corp.
