Question about table space rebalance

[James]

I am not sure whether users can access data or insert new data into
tables who belong to a rebalanced table space after new containers are
added? (DB2 version is 8.x) What I know is user can not insert new
data into tables who belong to a rebalanced table space. Is the any
way to avoid this?

Thanks

James

[Artur]

On 6 Cze, 07:30, James <[e-mail]:

I am not sure whether users can access data or insert new data into
tables who belong to a rebalanced table space after new containers are
added? (DB2 version is 8.x) What I know is user can not insert new
data into tables who belong to a rebalanced table space. Is the any
way to avoid this?

Thanks

James

James,

Rebalancing is not restricting users from modifying data in the
rebalanced tablespace, but it can excessively load your system.
Excessively in extreme cases means that nobody can work on the system
because of 100% IO wait, or poor response time (eg. rebalancing on
peak load with undersized storage).
But you can add new containers with new stripe set, which means no
reballancing will occur:

ALTER TABLESPACE space1 BEGIN NEW STRIPE SET (FILE 'file1'' 4 G)

Of course, the natural way of adding a new space is just extending
existing containers.

-- Artur Wronski

[James]

On Jun 6, 2:41 pm, Artur <[e-mail]:

On 6 Cze, 07:30, James <[e-mail]:

I am not sure whether users can access data or insert new data into
tables who belong to a rebalanced table space after new containers are
added? (DB2 version is 8.x) What I know is user can not insert new
data into tables who belong to a rebalanced table space. Is the any
way to avoid this?

Thanks

James

James,

Rebalancing is not restricting users from modifying data in the
rebalanced tablespace, but it can excessively load your system.
Excessively in extreme cases means that nobody can work on the system
because of 100% IO wait, or poor response time (eg. rebalancing on
peak load with undersized storage).

But you can add new containers with new stripe set, which means no
reballancing will occur:

ALTER TABLESPACE space1 BEGIN NEW STRIPE SET (FILE 'file1'' 4 G)

Of course, the natural way of adding a new space is just extending
existing containers.

-- Artur Wronski

After I added a new container and this table space was rebalancing, I
found that the total page increased, but free page of this table space
was still zero. When would new value of free page be shown, after
rebalance?

Thanks.

[spider007]

On Jun 6, 11:41 am, Artur <[e-mail]:

On 6 Cze, 07:30, James <[e-mail]:

I am not sure whether users can access data or insert new data into
tables who belong to a rebalanced table space after new containers are
added? (DB2 version is 8.x) What I know is user can not insert new
data into tables who belong to a rebalanced table space. Is the any
way to avoid this?

Thanks

James

James,

Rebalancing is not restricting users from modifying data in the
rebalanced tablespace, but it can excessively load your system.
Excessively in extreme cases means that nobody can work on the system
because of 100% IO wait, or poor response time (eg. rebalancing on
peak load with undersized storage).

But you can add new containers with new stripe set, which means no
reballancing will occur:

ALTER TABLESPACE space1 BEGIN NEW STRIPE SET (FILE 'file1'' 4 G)

Of course, the natural way of adding a new space is just extending
existing containers.

-- Artur Wronski

Artur,

If we add new containers with new strip set, all the new data would go
in that stripe set and will not be spread across the other containers.
Moreover, there is no way we can distribute the data once a new stripe
set is defined as adding one more container would add on the new
stripe set. So, the entire motive of distribution data goes for a
toss. So we cannot rebalance the tablespace. Correct me if I am
wrong.!

Saurabh