470,596 Members | 1,574 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,596 developers. It's quick & easy.

Creating db in 2 partitions out of 8

Hi
I am having a requirement to create a db in 2 out of 8 partitiones.
I have the following doubts.
1. should I create a new instance in 2 partitions alone (the present
instance spans 8 nodes)
2. or is there a way to create the db in 2 out of 8.
If I have to create a new instance, (its a BCU from IBM)
I;d be happy if someone would link a material (1st time I am working
in a partitioned env)
Should I execute db2icrt in each of the nodes??
Please help.

Apr 10 '07 #1
8 1536
On Apr 10, 8:50 pm, arunro...@gmail.com wrote:
Hi
I am having a requirement to create a db in 2 out of 8 partitiones.
I have the following doubts.
1. should I create a new instance in 2 partitions alone (the present
instance spans 8 nodes)
2. or is there a way to create the db in 2 out of 8.
If I have to create a new instance, (its a BCU from IBM)
I;d be happy if someone would link a material (1st time I am working
in a partitioned env)
Should I execute db2icrt in each of the nodes??
Please help.
Hi,

AFAIK with version 8 (LUW);
only option to address your requirement is the first option as already
mentioned by you.
Should I execute db2icrt in each of the nodes??
It depends if you are using single servers or multiple servers;
for a multipartitioned database on a single machine: you only have to
create a single instance (db2icrt) with the relevant entries in $HOME/
sqllib/db2nodes.cfg

Following is a good link to start with:
http://www-128.ibm.com/developerwork.../dm-0507desai/

Cheers
Prakash Gautam

Apr 11 '07 #2

Thanks Prakash. This is a fresh start in new direction for me.

Apr 11 '07 #3
ar*******@gmail.com wrote:
Hi
I am having a requirement to create a db in 2 out of 8 partitiones.
I have the following doubts.
1. should I create a new instance in 2 partitions alone (the present
instance spans 8 nodes)
2. or is there a way to create the db in 2 out of 8.
If I have to create a new instance, (its a BCU from IBM)
I;d be happy if someone would link a material (1st time I am working
in a partitioned env)
You could create the database on all 8 partitions, then adjust the partition
groups to include only the two partitions you want.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany
Apr 11 '07 #4
On Apr 11, 10:10 am, Knut Stolze <sto...@de.ibm.comwrote:
arunro...@gmail.com wrote:
Hi
I am having a requirement to create a db in 2 out of 8 partitiones.
I have the following doubts.
1. should I create a new instance in 2 partitions alone (the present
instance spans 8 nodes)
2. or is there a way to create the db in 2 out of 8.
If I have to create a new instance, (its a BCU from IBM)
I;d be happy if someone would link a material (1st time I am working
in a partitioned env)

You could create the database on all 8 partitions, then adjust the partition
groups to include only the two partitions you want.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany
This is what I am doing now. thank you

Apr 11 '07 #5
Ian
Knut Stolze wrote:
ar*******@gmail.com wrote:
>Hi
I am having a requirement to create a db in 2 out of 8 partitiones.
I have the following doubts.
1. should I create a new instance in 2 partitions alone (the present
instance spans 8 nodes)
2. or is there a way to create the db in 2 out of 8.
If I have to create a new instance, (its a BCU from IBM)
I;d be happy if someone would link a material (1st time I am working
in a partitioned env)

You could create the database on all 8 partitions, then adjust the partition
groups to include only the two partitions you want.
The problem is that you can't really do this. IBMTEMPGROUP is a
"hidden" (in the sense that it doesn't appear in syscat.nodegroups)
database partition group that includes ALL partitions in your instance.
All system temporary tablespaces exist in IBMTEMPGROUP (you can't get
away from this).

So, while you can restrict the data in a database to a single (or pair)
of partitions, your database still spans all partitions in the instance.
And you still need to back up all partitions.

So, your best option is to create a second instance that has only 2
partitions.

Apr 12 '07 #6
Hi All
Thank you for advising me onthis. I have did what you guys told,
put data in a partition map spanning 2 nodes. Now I have different
doubt.
In windows, if I change a db cfg and it needs me to restart - SQL1363W
msg, I can go into control center and actually see if the changes are
'Done' or are 'PENDING'.
Is there a way in linux to do the same?

Thank you
Arun

Apr 12 '07 #7
ar*******@gmail.com wrote:
[...]
In windows, if I change a db cfg and it needs me to restart - SQL1363W
msg, I can go into control center and actually see if the changes are
'Done' or are 'PENDING'.
Is there a way in linux to do the same?
I assume you can do the same with the control center in linux (dont know
though). But here is how you can do it from the shell:

db2 connect to <db>
db2 get db cfg show detail | less -S

You'll get one column for "Current Value", and one for "Delayed Value"

/Lennart

Apr 12 '07 #8
Ian
ar*******@gmail.com wrote:
Hi All
Thank you for advising me onthis. I have did what you guys told,
put data in a partition map spanning 2 nodes. Now I have different
doubt.
In windows, if I change a db cfg and it needs me to restart - SQL1363W
msg, I can go into control center and actually see if the changes are
'Done' or are 'PENDING'.
Is there a way in linux to do the same?
Connect to the database, and

db2 get db cfg for <yourdbshow detail

This will show "current" and "delayed" values. Delayed = value for next
restart.

Or use db2pd -db <yourdb-dbcfg, and compare memory value (active) and
disk value (config file - next restart).
Also, in a partitioned database, remember that the database
configuration is unique for each partition. So make sure you update the
config on all partitions (when applicable).

Apr 12 '07 #9

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Steve | last post: by
5 posts views Thread by Nick J Chackowsky | last post: by
3 posts views Thread by RunLevelZero | last post: by
6 posts views Thread by cantabile | last post: by
11 posts views Thread by Claude Henchoz | last post: by
7 posts views Thread by Gladiator | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.