On Nov 27, 5:35 pm, Ian <ianb...@mobile audio.comwrote:
>
Indeed, the filesystem is full, but i added a new filesystem and db2
don't use it to add more conteiners.
You may need to deactivate / activate the database for this to occur.
The doc is not very clear on when the storage is available (it says,
"Existing regular and large table spaces using automatic storage will
not initially use these new paths. The database manager might choose to
create new table space containers on these paths only if an out-of-space
condition occurs.")
I recall reading that DB2 evaluates the storage paths upon database
activation.
Hi,
It's actually just temporary tablespaces that evaluate the storage
paths upon database activation. As pointed out above, for regular/
large tablespaces, the paths won't be considered unless an "out of
space" condition occurs on one of the existing storage paths. That
said, it sounds like this is the situation and DB2 should be creating
a new stripe set (which should include the newly added path).
Just to be clear, is the tablespace in question actually an automatic
storage tablespace? Can you do a "get snapshot for tablespaces on
<databaseName >" and look for the following lines (for the tablespace
in question)?
Using automatic storage = Yes
Auto-resize enabled = Yes
Also, can you show the storage path information from a database
snapshot? This will tell us for sure how much space DB2 is seeing on
the paths.
db2 update monitor switches using bufferpool on (this collects
extra information)
db2 get snapshot for database on <databaseName >
For example:
Number of automatic storage paths = 2
Automatic storage path = C:\SP1
File system ID = 2691985332
Storage path free space (bytes) = 13048266752
File system used space (bytes) = 39183147008
File system total space (bytes) = 52432740352
Automatic storage path = D:\SP2
File system ID = 1552810699
Storage path free space (bytes) = 17006305280
File system used space (bytes) = 30588035072
File system total space (bytes) = 47594340352
Regards,
Kelly