Re: Production DB2 Problem - some more details ..
You want to post your question on the DB2-l listserv as well Robert Galambos Compuware Senior Technical Specialist IBM Certified Solutions Expert - DB2 UDB for OS/390 Database Administration [EMAIL PROTECTED] Tel: +1 905 886 7000 Toll Free: +1 800 263 7189 Fax: +1 905 886 7023 Quebec: +1 877-281-1888 Compuware Canada Service is our best product Les renseignements contenus dans le présent message électronique sont confidentiels et concernent exclusivement le(s) destinataire(s) désigné(s). Il est strictement interdit de distribuer ou de copier ce message. Si vous avez reçu ce message par erreur, veuillez répondre par courriel à l'expéditeur et effacer ou détruire toutes les copies du présent message. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jacky Bright Sent: September 20, 2006 1:44 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Production DB2 Problem - some more details .. I am giving you some more details with regard to my problem... Database Storage Group Definition: CREATE STOGROUP STGP1 VOLUMES(PDB001) VCAT DBSTGP; In the SMS There is storage group named DBSTGP and volumes included under this storage group are PDB001 PDB002 PDB003 PDB004 PDB005 When these 5 volumes got full, I hav added another 2 volumes PDBR006 and PDBR007. However, Simple tablespace could not extend to these newly added volumes and we were getting EXTEND Failed error for tablespace related vsam dataset. After performing REORG tablespace dataset got extended to these newly added volumes(PDBR006,PDBR007). Hi ... I am facing problem in production DB2. 5 Volumes were configured for Database in storage group while creation of tablespace A. Later in 1 month these 5 volumes were full and added another 2 volumes, however Tablespace A could not extend to these newly created volumes. After performing REORG for Tablespace A , Tablespace VSAM dataset got extended to these newly created volumes. Is it necessary to do REORG of Tablespace everytime you add volumes in storage group. Note : Tablespace were created using Storage group and not using volumes parameter. What could be the reason for the same ? Please reply urgently Jacky -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Production DB2 Problem - some more details ..
I am giving you some more details with regard to my problem... Database Storage Group Definition: CREATE STOGROUP STGP1 VOLUMES(PDB001) VCAT DBSTGP; In the SMS There is storage group named DBSTGP and volumes included under this storage group are PDB001 PDB002 PDB003 PDB004 PDB005 When these 5 volumes got full, I hav added another 2 volumes PDBR006 and PDBR007. However, Simple tablespace could not extend to these newly added volumes and we were getting EXTEND Failed error for tablespace related vsam dataset. After performing REORG tablespace dataset got extended to these newly added volumes(PDBR006,PDBR007). Hi ... I am facing problem in production DB2. 5 Volumes were configured for Database in storage group while creation of tablespace A. Later in 1 month these 5 volumes were full and added another 2 volumes, however Tablespace A could not extend to these newly created volumes. After performing REORG for Tablespace A , Tablespace VSAM dataset got extended to these newly created volumes. Is it necessary to do REORG of Tablespace everytime you add volumes in storage group. Note : Tablespace were created using Storage group and not using volumes parameter. What could be the reason for the same ? Please reply urgently Jacky -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Production DB2 Problem - some more details ..
On Wed, 20 Sep 2006 23:13:46 +0530, Jacky Bright [EMAIL PROTECTED] wrote: I am giving you some more details with regard to my problem... Database Storage Group Definition: CREATE STOGROUP STGP1 VOLUMES(PDB001) VCAT DBSTGP; In the SMS There is storage group named DBSTGP and volumes included under this storage group are PDB001 PDB002 PDB003 PDB004 PDB005 When these 5 volumes got full, I hav added another 2 volumes PDBR006 and PDBR007. However, Simple tablespace could not extend to these newly added volumes and we were getting EXTEND Failed error for tablespace related vsam dataset. After performing REORG tablespace dataset got extended to these newly added volumes(PDBR006,PDBR007). Jacky - I am no expert on the subject either but please review what Lizette has offered. I am thinking that for a tablespace that has this error, doing and IDCAMS ALTER ADDVOLUMES(* * * * * * *) will aleviate the problem. We have Stop/X37 here - this will do extending for us. Not sure if you have it in your shop, being it is failing I doubt it. Messages and reason codes would be helpful here. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
FW: Production DB2 Problem - some more details ..
Jacky,
I believe for DB2 stogroups to use SMS the DB2 stogroup should be defined
as VOLUMES('*') for it to work the way you wish with the proper ACS
routines. We are not SMS managed so I am not sure how to accomplish this. I
would try an ALTER STOGROUP STGP1 REMOVE VOLUMES (PDB001) followed by an
ALTER STOGROUP STGP1 ADD VOLUMES('*'). Look it up in DB2 SQL REFERENCE.
This is all speculation on my part. If you had added those volumes to the
DB2 stogroup then it may have worked on the dataset extend since then DB2
would have done an ADDVOL (volser) to the dataset. I guess that DB2 looks at
the DB2 stogroup that the tablespace is defined on and sees which volumes
are in the DB2 stogroup in this case only PDB001 that can accept new extents
and thus fails since it does not have any other volsers that it can do an
IDCAMS ADDVOL statement with. If it sees an '*' for volumes in the DB2
STOGROUP then it passes it off to SMS. The reason that REORG works is that
the SMS ACS routines are probably invoked prior to looking at the DB2
STOGROUP and thus knows which volumes it can be created on without
determining which volumes are in the DB2 STOGROUP the tablespace resides in.
Bob Lawrence
DBA
Boscovs Dept Stores LLC
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Jacky Bright
Sent: Wednesday, September 20, 2006 1:44 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Production DB2 Problem - some more details ..
I am giving you some more details with regard to my problem...
Database Storage Group Definition:
CREATE STOGROUP STGP1 VOLUMES(PDB001)
VCAT DBSTGP;
In the SMS There is storage group named DBSTGP and volumes included under
this storage group are
PDB001
PDB002
PDB003
PDB004
PDB005
When these 5 volumes got full, I hav added another 2 volumes PDBR006 and
PDBR007. However, Simple tablespace could not extend to these newly added
volumes and we were getting EXTEND Failed error for tablespace related vsam
dataset. After performing REORG tablespace dataset got extended to these
newly added volumes(PDBR006,PDBR007).
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: FW: Production DB2 Problem - some more details ..
I seem to remember that DB2 would not alter add volume if the volume was
already in the allocation. I think the crucial error is not having the DB2
stogroup defined as colume (*) - which will never match an existing volume.
That will force it to the SMS allocation.
Mike
On 9/20/06, Robert Lawrence [EMAIL PROTECTED] wrote:
Jacky,
I believe for DB2 stogroups to use SMS the DB2 stogroup should be
defined
as VOLUMES('*') for it to work the way you wish with the proper ACS
routines. We are not SMS managed so I am not sure how to accomplish this.
I
would try an ALTER STOGROUP STGP1 REMOVE VOLUMES (PDB001) followed by an
ALTER STOGROUP STGP1 ADD VOLUMES('*'). Look it up in DB2 SQL REFERENCE.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
