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
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
Of Jacky Bright
Sent: Tuesday, September 19, 2006 5:27 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Production DB2 Problem
Hi ...
I am facing problem in production DB2.
5 Volumes were configured for Database
To get to the new volumes are you using DEL/DEFs or letting SMS manage the
space for DB2 using STOGROUPS.
What I know about DB2 and Extending can fit on a pin, however, here goes.
Depending on the VERSION of DB2 if you do an ADDVOL but did not have enough
canidate volumes in the list, they may
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
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
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
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
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
something wrong here - my experience was that db2 would start using any sms
volume as soon as it was enabled.
I would suggest open an incident with IBM.
Some things to check
in DB2 the STOGROUP should have volumes (*)
the priquty and secqty for the db2 tablespace and index spaces should be
9 matches
Mail list logo
