ALTER STOGROUP ADD VOLUME does not work correct

Georg Peter

ALTER STOGROUP ADD VOLUME does not work correct
Fellow collegues,

in one of our applications (DB2 for OS/390 V6) we have a 32K tablespace that
resides in a separate storage group with one volume.

Application data grows every day. And to avoid upcoming extents we do an
ALTER STOGROUP ADD VOLUME xyz.

But unfortunately DB2 ignores the given additional volume - DB2 builds
extents and these extents are stored in one of our work volumes.

Here's the question: How can we force DB2 to use the additional volume for
storing the data and NOT to built one extent after the other on a "not
deviced" volume ?

Any comments, thoughts, experiences are highly appreciated.

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
Georg H. Peter c/o
-------------------------------------------------------------------
Datenzentrale Baden-Wuerttemberg
Software Development & Technology Center
Knowledge Center Database Systems
Krailenshaldenstrasse 44, 70469 Stuttgart, Germany, Europe
e:mail [login to unmask email]
Phone 0049-711-8108-271
PC-Fax 004971189696071
Internet (only in german language):http://www.dzbw.de
----------------------------------------------------------------------
"Every action is a p o s i t i v e action, even if it has a negative
result."

---------------------------------------------------------------------------------
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

Andy Lankester

Re: ALTER STOGROUP ADD VOLUME does not work correct
(in response to Georg Peter)
Peter,

It may be that you have to do a -STOP/-START to make the ALTER take effect.

Andy

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On Behalf
Of Peter, Georg
Sent: 21 December 2004 13:46
To: [login to unmask email]
Subject: ALTER STOGROUP ADD VOLUME does not work correct


Fellow collegues,

in one of our applications (DB2 for OS/390 V6) we have a 32K tablespace that
resides in a separate storage group with one volume.

Application data grows every day. And to avoid upcoming extents we do an
ALTER STOGROUP ADD VOLUME xyz.

But unfortunately DB2 ignores the given additional volume - DB2 builds
extents and these extents are stored in one of our work volumes.

Here's the question: How can we force DB2 to use the additional volume for
storing the data and NOT to built one extent after the other on a "not
deviced" volume ?

Any comments, thoughts, experiences are highly appreciated.

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
Georg H. Peter c/o
-------------------------------------------------------------------
Datenzentrale Baden-Wuerttemberg
Software Development & Technology Center
Knowledge Center Database Systems
Krailenshaldenstrasse 44, 70469 Stuttgart, Germany, Europe
e:mail [login to unmask email]
Phone 0049-711-8108-271
PC-Fax 004971189696071
Internet (only in german language):http://www.dzbw.de
----------------------------------------------------------------------
"Every action is a p o s i t i v e action, even if it has a negative
result."

----------------------------------------------------------------------------
-----
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

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.2 - Release Date: 20/12/2004


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.296 / Virus Database: 265.6.2 - Release Date: 20/12/2004


---------------------------------------------------------------------------------
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

Phil Grainger

Re: ALTER STOGROUP ADD VOLUME does not work correct
(in response to Andy Lankester)
Is this SMS or non-SMS

I assume it's SMS as in a non-SMS environment DB2 will NEVER allocate on a volume that is knows nothing about. (Check a LISTCAT to see what candidate volumes it has already in use).

If SMS, then check the ACS routines to see if they are overriding the DB2 STOGROUP definitions

Phil Grainger
Computer Associates

-----Original Message-----
From: DB2 Data Base Discussion List on behalf of Peter, Georg
Sent: Tue 21/12/2004 13:45
To: [login to unmask email]
Cc:
Subject: ALTER STOGROUP ADD VOLUME does not work correct



Fellow collegues,

in one of our applications (DB2 for OS/390 V6) we have a 32K tablespace that
resides in a separate storage group with one volume.

Application data grows every day. And to avoid upcoming extents we do an
ALTER STOGROUP ADD VOLUME xyz.

But unfortunately DB2 ignores the given additional volume - DB2 builds
extents and these extents are stored in one of our work volumes.

Here's the question: How can we force DB2 to use the additional volume for
storing the data and NOT to built one extent after the other on a "not
deviced" volume ?

Any comments, thoughts, experiences are highly appreciated.

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
Georg H. Peter c/o
-------------------------------------------------------------------
Datenzentrale Baden-Wuerttemberg
Software Development & Technology Center
Knowledge Center Database Systems
Krailenshaldenstrasse 44, 70469 Stuttgart, Germany, Europe
e:mail [login to unmask email]
Phone 0049-711-8108-271
PC-Fax 004971189696071
Internet (only in german language):http://www.dzbw.de
----------------------------------------------------------------------
"Every action is a p o s i t i v e action, even if it has a negative
result."

---------------------------------------------------------------------------------
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



Horacio Villa

Re: ALTER STOGROUP ADD VOLUME does not work correct
(in response to Phil Grainger)
If it's SMS, then there's no need for ALTER STOGROUP, as far as I know...

Horacio Villa




"Grainger, Phil"
<[login to unmask email] To: [login to unmask email]
.COM> cc:
Sent by: DB2 Data Subject: Re: ALTER STOGROUP ADD VOLUME does not work correct
Base Discussion
List
<[login to unmask email]
ORG>


21/12/2004 10:56
Please respond to
DB2 Database
Discussion list
at IDUG





Is this SMS or non-SMS

I assume it's SMS as in a non-SMS environment DB2 will NEVER allocate on a
volume that is knows nothing about. (Check a LISTCAT to see what candidate
volumes it has already in use).

If SMS, then check the ACS routines to see if they are overriding the DB2
STOGROUP definitions

Phil Grainger
Computer Associates

-----Original Message-----
From: DB2 Data Base Discussion List on behalf of Peter, Georg
Sent: Tue 21/12/2004 13:45
To: [login to unmask email]
Cc:
Subject: ALTER STOGROUP ADD VOLUME does not work correct



Fellow collegues,

in one of our applications (DB2 for OS/390 V6) we have a 32K
tablespace that
resides in a separate storage group with one volume.

Application data grows every day. And to avoid upcoming
extents we do an
ALTER STOGROUP ADD VOLUME xyz.

But unfortunately DB2 ignores the given additional volume -
DB2 builds
extents and these extents are stored in one of our work
volumes.

Here's the question: How can we force DB2 to use the
additional volume for
storing the data and NOT to built one extent after the other
on a "not
deviced" volume ?

Any comments, thoughts, experiences are highly appreciated.

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
Georg H. Peter c/o

-------------------------------------------------------------------
Datenzentrale Baden-Wuerttemberg
Software Development & Technology Center
Knowledge Center Database Systems
Krailenshaldenstrasse 44, 70469 Stuttgart, Germany, Europe
e:mail [login to unmask email]
Phone 0049-711-8108-271
PC-Fax 004971189696071
Internet (only in german language):http://www.dzbw.de

----------------------------------------------------------------------
"Every action is a p o s i t i v e action, even if it has a
negative
result."


---------------------------------------------------------------------------------

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

---------------------------------------------------------------------------------
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

Linda Billings

Re: ALTER STOGROUP ADD VOLUME does not work correct
(in response to Horacio Villa)
There's probably some confusion about storage groups here. Both SMS and DB2
use the term storage group for its DASD playgrounds. An ALTER STOGROUP...
for DB2 would not touch SMS. It adds a volume for what is defined in DB2
for a DB2 storage group. If your DB2 is using SMS, then you need not do
anything in DB2. Your storage people need to add a volume to your SMS
storage group that is being used by DB2.

HTH,
Linda Billings
Database Administrator
State of Wisconsin
Department of Administration
Division of Enterprise Technology
Bureau of Development and Operations
[login to unmask email]

"If you had to identify, in one word, the reason why the human race has not
and never will achieve its full potential, that word would be 'meetings.' "
- Dave Barry



-----Original Message-----
From: Horacio Villa [mailto:[login to unmask email]
Sent: Tuesday, December 21, 2004 2:52 PM
To: [login to unmask email]
Subject: Re: ALTER STOGROUP ADD VOLUME does not work correct


If it's SMS, then there's no need for ALTER STOGROUP, as far as I know...

Horacio Villa




"Grainger, Phil"
<[login to unmask email] To:
[login to unmask email]
.COM> cc:
Sent by: DB2 Data Subject: Re: ALTER STOGROUP
ADD VOLUME does not work correct
Base Discussion
List
<[login to unmask email]
ORG>


21/12/2004 10:56
Please respond to
DB2 Database
Discussion list
at IDUG





Is this SMS or non-SMS

I assume it's SMS as in a non-SMS environment DB2 will NEVER allocate on a
volume that is knows nothing about. (Check a LISTCAT to see what candidate
volumes it has already in use).

If SMS, then check the ACS routines to see if they are overriding the DB2
STOGROUP definitions

Phil Grainger
Computer Associates

-----Original Message-----
From: DB2 Data Base Discussion List on behalf of Peter, Georg
Sent: Tue 21/12/2004 13:45
To: [login to unmask email]
Cc:
Subject: ALTER STOGROUP ADD VOLUME does not work correct



Fellow collegues,

in one of our applications (DB2 for OS/390 V6) we have a 32K
tablespace that
resides in a separate storage group with one volume.

Application data grows every day. And to avoid upcoming
extents we do an
ALTER STOGROUP ADD VOLUME xyz.

But unfortunately DB2 ignores the given additional volume -
DB2 builds
extents and these extents are stored in one of our work
volumes.

Here's the question: How can we force DB2 to use the
additional volume for
storing the data and NOT to built one extent after the other
on a "not
deviced" volume ?

Any comments, thoughts, experiences are highly appreciated.

Thanks in advance.

With kind regards - mit freundlichen Gruessen,
Georg H. Peter c/o

-------------------------------------------------------------------
Datenzentrale Baden-Wuerttemberg
Software Development & Technology Center
Knowledge Center Database Systems
Krailenshaldenstrasse 44, 70469 Stuttgart, Germany, Europe
e:mail [login to unmask email]
Phone 0049-711-8108-271
PC-Fax 004971189696071
Internet (only in german language):http://www.dzbw.de

----------------------------------------------------------------------
"Every action is a p o s i t i v e action, even if it has a
negative
result."


----------------------------------------------------------------------------
-----

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

----------------------------------------------------------------------------
-----
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

---------------------------------------------------------------------------------
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