REORG to Different VCAT Name

Donald Gormanly

REORG to Different VCAT Name
Hey, all!

I have an SMS DASD pool set up that I want to move an object into. I run
an ALTER statement on the Tablespace and Index to point to the SMS
STOGROUP. Then, I run a DB2 REORG Utility and it fails with an
UNAVAILABLE RESOURCE and the resource is the new dataset I want the old
data set to be moved to. Here's the error from the job output:

- RESOURCE UNAVAILABLE
REASON 00C200E2
TYPE 00000220
NAME IDBIX.DSNDBC.GE00HIPD.GE04HIX1.I0001.A002

This was Partition 2 of a tablespace, hence the A002 at the end.

Here is some output from the DB2 Log:

IEF403I DB2ADMNA - STARTED - TIME=10.39.10
IKJ56228I DATA SET IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001 NOT IN
CATALOG OR CATALOG CAN NOT BE ACCESSED
DSNB207I - DYNAMIC ALLOCATION OF DATA SET FAILED. 860
REASON=17080002. DSNAME=IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
DSNT500I - DSNUGRAR RESOURCE UNAVAILABLE 861
REASON 00C200E2
TYPE 00000220
NAME IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
DSN3201I - ABNORMAL EOT IN PROGRESS FOR USER=DB2ADMN 862
CONNECTION-ID=UTILITY CORRELATION-ID=DB2ADMNA JOBNAME=DB2ADMNA
ASID=0075 TCB=008F9538
IEF450I DB2ADMNA STEP1 - ABEND=S04E U0000 REASON=00E40009 863
TIME=10.39.12

Anyone else ever have this situation?

The weird part of all of this is, if I run a RECOVERY on the Tablespace to
an Image Copy, it allocates it just fine, but I'm stuck with the old VCAT
dataset name now, as well as the new one. Any way around all of this?

Donald Gormanly
DBA
212-314-4076
**********************************************************************

Confidentiality Note: This message and any attachments
may contain legally privileged and/or confidential information.
Any unauthorized disclosure, use or dissemination of this e-mail
message or its contents, either in whole or in part, is prohibited.
If you are not the intended recipient of this e-mail message,
kindly notify the sender and then destroy it.

**********************************************************************


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Matthew Rhea

Re: REORG to Different VCAT Name
(in response to Donald Gormanly)
I had a bunch of objects that I had to move to a different SMS pool. I
stopped the objects and then ran ADRDSSU. For example, to move the DB2
directory objects, I used this JCL. It ran very fast. It copies the
datasets and then deletes the old ones. SMS places the new datasets on
the correct volumes. I didn't have to do any alters.


//SMSMOVE1 EXEC PGM=ADRDSSU,PARM='UTILMSG=YES'
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DATASET ( INCLUDE ( -
HLQ.DSNDBC.DSNDB01.** -
) ) -
CAT ALLE ALLD(*) DELETE PURGE SPHERE
/*



On Thu, 7 Dec 2006 14:53:35 -0500, Donald Gormanly <[login to unmask email]
EQUITABLE.COM> wrote:

>Hey, all!
>
>I have an SMS DASD pool set up that I want to move an object into. I run
>an ALTER statement on the Tablespace and Index to point to the SMS
>STOGROUP. Then, I run a DB2 REORG Utility and it fails with an
>UNAVAILABLE RESOURCE and the resource is the new dataset I want the old
>data set to be moved to. Here's the error from the job output:
>
>- RESOURCE UNAVAILABLE
> REASON 00C200E2
> TYPE 00000220
> NAME IDBIX.DSNDBC.GE00HIPD.GE04HIX1.I0001.A002
>
>This was Partition 2 of a tablespace, hence the A002 at the end.
>
>Here is some output from the DB2 Log:
>
>IEF403I DB2ADMNA - STARTED - TIME=10.39.10
>IKJ56228I DATA SET IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001 NOT IN
>CATALOG OR CATALOG CAN NOT BE ACCESSED
>DSNB207I - DYNAMIC ALLOCATION OF DATA SET FAILED. 860
>REASON=17080002. DSNAME=IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
>DSNT500I - DSNUGRAR RESOURCE UNAVAILABLE 861
> REASON 00C200E2
> TYPE 00000220
> NAME IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
>DSN3201I - ABNORMAL EOT IN PROGRESS FOR USER=DB2ADMN 862
>CONNECTION-ID=UTILITY CORRELATION-ID=DB2ADMNA JOBNAME=DB2ADMNA
>ASID=0075 TCB=008F9538
>IEF450I DB2ADMNA STEP1 - ABEND=S04E U0000 REASON=00E40009 863
> TIME=10.39.12
>
>Anyone else ever have this situation?
>
>The weird part of all of this is, if I run a RECOVERY on the Tablespace to
>an Image Copy, it allocates it just fine, but I'm stuck with the old VCAT
>dataset name now, as well as the new one. Any way around all of this?
>
>Donald Gormanly
>DBA
>212-314-4076
>**********************************************************************
>
>Confidentiality Note: This message and any attachments
>may contain legally privileged and/or confidential information.
>Any unauthorized disclosure, use or dissemination of this e-mail
>message or its contents, either in whole or in part, is prohibited.
>If you are not the intended recipient of this e-mail message,
>kindly notify the sender and then destroy it.
>
>**********************************************************************
>
>
>--------------------------------------------------------------------------
-------
>Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at DB2-L-
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm
>

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Mike Bell

Re: REORG to Different VCAT Name
(in response to Matthew Rhea)
Your subject specifies a new VCAT name which is an attribute of the DB2
stogroup not the SMS stogroup.

Assuming you really want to change the VCAT let me lay out some boundries.

1. You have to stop the object to change the stogroup (either indexspace or
tablespace)
2. As soon the ALTER TABLESPACE dbname.spname USING STOGROUP xxxx is
committed, DB2 expects to use the new dataset name.
3. This is a tablespace/index option not partition. Once you commit the
ALTER all the partitions need the new name.
4. This is not an area that DB2 helps you very much with. Once you get
started, it is hard to figure out what DB2 is actually doing.

If you stopped the tablespace, altered the stogroup to the new DB2 stogroup
with the new VCAT and commit, DB2 expects you to rename the dataset before
the start spacenam.
The resource unavailable is for the existing dataset.
The next step at this point is IDCAMS ALTER NEWNAME to change the names of
the datasets and redo the start spacename to retry the allocation.

If you run a RECOVER, DB2 does not need the old dataset, won't fail if the
new VCAT dataset doesn't exist, just allocates a new dataset and does the
recover. This is probably the source of your one new VCAT dataset. Note -
DB2 will never delete the old VCAT datasets, they don't exist to DB2
anymore. IDCAMS DEL for the old VCAT after the recoveries are complete.

Other methods you can use.
1. Instead of IDCAMS ALTER NEWNAME, you can use DFDSS COPY
COPY DS(INC(IDBIX.DSNDBC.GE00HIPD.GE04HIX1.I0001.*))
OUTDDNAME(somevl) -
RENAMEU(IDBIX.**) -
INDDNAME(DASD1) DEL CATALOG
I have done this myself but it is a MVS utility not DB2 so you really need
to know how it works. It will reallocate to the new SMS stogroup if that is
what you need to do.


Mike
HLS Technologies


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Donald Gormanly
Sent: Thursday, December 07, 2006 1:54 PM
To: [login to unmask email]
Subject: [DB2-L] REORG to Different VCAT Name


Hey, all!

I have an SMS DASD pool set up that I want to move an object into. I run an
ALTER statement on the Tablespace and Index to point to the SMS STOGROUP.
Then, I run a DB2 REORG Utility and it fails with an UNAVAILABLE RESOURCE
and the resource is the new dataset I want the old data set to be moved to.
Here's the error from the job output:

- RESOURCE UNAVAILABLE
REASON 00C200E2
TYPE 00000220
NAME IDBIX.DSNDBC.GE00HIPD.GE04HIX1.I0001.A002

This was Partition 2 of a tablespace, hence the A002 at the end.

Here is some output from the DB2 Log:

IEF403I DB2ADMNA - STARTED - TIME=10.39.10
IKJ56228I DATA SET IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001 NOT IN
CATALOG OR CATALOG CAN NOT BE ACCESSED
DSNB207I - DYNAMIC ALLOCATION OF DATA SET FAILED. 860
REASON=17080002. DSNAME=IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
DSNT500I - DSNUGRAR RESOURCE UNAVAILABLE 861
REASON 00C200E2
TYPE 00000220
NAME IDBTS.DSNDBC.GE00HIPD.GE04HIXT.I0001.A001
DSN3201I - ABNORMAL EOT IN PROGRESS FOR USER=DB2ADMN 862
CONNECTION-ID=UTILITY CORRELATION-ID=DB2ADMNA JOBNAME=DB2ADMNA
ASID=0075 TCB=008F9538
IEF450I DB2ADMNA STEP1 - ABEND=S04E U0000 REASON=00E40009 863
TIME=10.39.12

Anyone else ever have this situation?

The weird part of all of this is, if I run a RECOVERY on the Tablespace to
an Image Copy, it allocates it just fine, but I'm stuck with the old VCAT
dataset name now, as well as the new one. Any way around all of this?

Donald Gormanly
DBA
212-314-4076

**********************************************************************

Confidentiality Note: This message and any attachments
may contain legally privileged and/or confidential information.
Any unauthorized disclosure, use or dissemination of this e-mail
message or its contents, either in whole or in part, is prohibited.
If you are not the intended recipient of this e-mail message,
kindly notify the sender and then destroy it.

**********************************************************************



----------------------------------------------------------------------------
----- Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page
select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences at
http://conferences.idug.org/index.cfm


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm