Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / April 2006

Tip: Looking for answers? Try searching our database.

redistribute nodegroup

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Visu - 13 Apr 2006 08:26 GMT
DB2 v7.2 EEE on AIX

I am trying to redistribute the data for a table that is skewed and
wondering if the output of db2gpmap is optimized or is it just
displaying the current information? I also read some where that LOAD
can be used in analyze mode?

Is there a way to redistribute just one table in the nodegroup? I have
mutiple tables in a nodegroup and i don't see any commands other than
REDISTRIBUTE NODEGROUP

Thanks
Visu
Shashi Mannepalli - 13 Apr 2006 16:34 GMT
If u run the db2gpmap it will give you the current P.MAP information. I
am not sure what do u mean by optimized ?
Once you get the P.MAP you can customize it and then run the
RE-DISTRIBUTE command.

cheers.....
Shashi Mannepalli
Visu - 13 Apr 2006 23:10 GMT
Thanks for the info Shashi.

Do you know if there is a way to re-distribute just one table and not
all tables in the node group
Ian - 14 Apr 2006 07:39 GMT
> DB2 v7.2 EEE on AIX
>
[quoted text clipped - 6 lines]
> mutiple tables in a nodegroup and i don't see any commands other than
> REDISTRIBUTE NODEGROUP

You can run db2atld can be done with MODE=ANALYZE, which will
output a new partition map that will result in even distribution
of the data.

However, you can only redistribute everything in the nodegroup,
because the partition map (pmap) applies to the entire nodegroup.

Theoretically you could create a new nodegroup / tablespace / table
and use a custom pmap -- but this would eliminate the possibility of
colocation on joins (tables being joined have to be in the same
nodegroup to qualify for colocation)

If you have 1 table that is bad, you should validate the partitioning
key that was chosen to make sure it was a good choice.
Visu - 14 Apr 2006 08:22 GMT
Thanks Ian. I bielieve the option of validating the partitioning key
and re-loading the data will be the best choice for me.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.