ADSM-L

DB consolidation

2015-10-04 18:08:47
Subject: DB consolidation
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at ASUPO
Date: 4/2/97 4:22PM
The process should have worked - You add the new volume, then use the reduce
command (which causes the data to be moved), and then delete the DB.  For
example, suppose you have 10 vols, each 100MB, and you want to replace them with
4 250MB vols.  You add the new DBs, then issue a reduce command to reduce the DB
size by 100 MB.  (Loop 9 more times).  at this point the delete command can be
issued for the indvidual data sets.  As I recall, the GUI admin client leads you
through this fairly well.

Jerry Lawson
jlawson AT thehartford DOT com

______________________________ Forward Header __________________________________
Subject: DB consolidation
Author:  INTERNET.OWNERAD at SNADGATE
Date:    4/2/97 4:22 PM


To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: DB consolidation

We tried this yesterday, but it would only allow a one-to-one (or volume-to-
volume) copy.  Our goal is to consolidate 10 little volumes into 4 large
volumes.  Do you know if there is some way we can do a dbcopy of multiple
volumes to one volume.  The DEFINE DBCOPY solution caused me to brag on what
a "piece of cake" this was going to be to our storage management people *:-)
Thanks for your help.

Betsy
*** Forwarding note from OWNERAD1--INTERNET 97/04/02 11:04 ***





TO:         NOREPLY  INTERNET  ADSM-L AT VM.MARIST DOT EDU
FROM:       OWNERAD1 INTERNET  owner-adsm-l AT VM.MARIST DOT EDU
DATE:       04/02/97 11:04
SUBJECT:    DB consolidation
DB consolidation

Betsy,
The process  I have use is much simpler than the DUMPDB/LOADDB commands.

1. Allocate and then DEFINE DBVOLUME for each of the new, larger volumes.  In e
this will dramatically extend the size of your DB>

2. DELETE DBVOLUME for each of the old volumes.  This will cause a real-time mo
DB data from the old to the new volumes.

When step two is finished you can scratch the old volumes and you are done - wi
weekend work and no user service interruption.  Ain't ADSM great!

 My reference is ADSM Administrators Guide (for MVS).  This is an amalgam of ste
the Chapter on "Managing the Database and Recovery Log."  In separate sections
how to extend the DB and reduce the DB.  I just combined the two processes.

There have been much more detailed postings on this process on this list in the
check the archives for more info.

Ted Spendlove
Thiokol, Corp.

>>> "Moir,Elizabeth" <Elizabeth.Moir AT VM.SSW.ABBOTT DOT COM> 04/02/97 07:47am 
>>> >>>
To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: DumpDB and Volume Change I hope somebody can help me with this
question.  We are running Version 1 of the ADSM server on VM.  We 10 volumes of
varying sizes being used by the ADSM database.  The storage administrator here
wants to consolidate these 10 volumes into 4 much larger volumes.  In studying
the documentation we think the DUMPDB and LOADDB commands are what we should
use...Dump the database, define the new volumes, delete the old volumes and Load

the database back on.

In all my reading, however, it seems to be that in order to use the Dump
DB Load DB scenario, the volumes that the database is being loaded back
onto have to be the same size.  Is this true?  If so, does anyone have
any ideas on what we CAN do in order to achieve our ultimate goal of fewer,
larger volumes for the database.

Thanks in advance for any and all suggestions.

Betsy
<Prev in Thread] Current Thread [Next in Thread>