By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,756 Members | 1,721 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,756 IT Pros & Developers. It's quick & easy.

haven't got a clue on this error.

P: n/a
Hey.

I'm toying with a test setup at which I try to let 2 instances work
together as partitions. When I fire up both instances, and I try to
connect to a test database called parttest (a simple 1 table database).
I get the following exception:

2005-05-30-10.12.52.288076+120 I81657G479 LEVEL: Severe
PID : 4406 TID : 16384 PROC : db2agent
(PARTTEST) 0
INSTANCE: instusr NODE : 000 DB : PARTTEST
APPHDL : 0-68 APPID: *N0.instusr.050530081252
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:10
RETCODE : ZRC=0x800201A4=-2147352156=SQLB_AS_NO_MULTIPARTITION_SUPPORT
"Unsupported operation on database with automatic storage."

Since I'm pretty new on partitioning, and only have some practice
reference material and db2ic to educate myself on partitioning, I
haven't got a clue what the above mentioned exception means.
Surely it doesn't mean I can't use automatic storage in a partitioned
environment (does it?). I suspect the exception means I have no
partitioning, if so, I'm really in the dark here.

Does anyone have some good reading on partitioning? (eg url to an e-book).

Thank you for any assistance.

-R-
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Jurgen Haan wrote:
Hey.

I'm toying with a test setup at which I try to let 2 instances work
together as partitions. When I fire up both instances, and I try to
connect to a test database called parttest (a simple 1 table database).
I get the following exception:

2005-05-30-10.12.52.288076+120 I81657G479 LEVEL: Severe
PID : 4406 TID : 16384 PROC : db2agent
(PARTTEST) 0
INSTANCE: instusr NODE : 000 DB : PARTTEST
APPHDL : 0-68 APPID: *N0.instusr.050530081252
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:10
RETCODE : ZRC=0x800201A4=-2147352156=SQLB_AS_NO_MULTIPARTITION_SUPPORT
"Unsupported operation on database with automatic storage."

Since I'm pretty new on partitioning, and only have some practice
reference material and db2ic to educate myself on partitioning, I
haven't got a clue what the above mentioned exception means.
Surely it doesn't mean I can't use automatic storage in a partitioned
environment (does it?). I suspect the exception means I have no
partitioning, if so, I'm really in the dark here.

Does anyone have some good reading on partitioning? (eg url to an e-book).

Thank you for any assistance.

-R-


Okay.. It appears my db2nodes.cfg is the cause of this.
removed node 1 from it and it operates like it should again.
But... Now my setup is a single partitioned one.
(pretty useless).

Back to the drawingboard.

-R-
Nov 12 '05 #2

P: n/a
Jurgen Haan wrote:
Jurgen Haan wrote:
Hey.

I'm toying with a test setup at which I try to let 2 instances work
together as partitions. When I fire up both instances, and I try to
connect to a test database called parttest (a simple 1 table database).
I get the following exception:

2005-05-30-10.12.52.288076+120 I81657G479 LEVEL: Severe
PID : 4406 TID : 16384 PROC : db2agent
(PARTTEST) 0
INSTANCE: instusr NODE : 000 DB : PARTTEST
APPHDL : 0-68 APPID: *N0.instusr.050530081252
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:10
RETCODE : ZRC=0x800201A4=-2147352156=SQLB_AS_NO_MULTIPARTITION_SUPPORT
"Unsupported operation on database with automatic storage."

Since I'm pretty new on partitioning, and only have some practice
reference material and db2ic to educate myself on partitioning, I
haven't got a clue what the above mentioned exception means.
Surely it doesn't mean I can't use automatic storage in a partitioned
environment (does it?). I suspect the exception means I have no
partitioning, if so, I'm really in the dark here.

Does anyone have some good reading on partitioning? (eg url to an
e-book).

Thank you for any assistance.

-R-

Okay.. It appears my db2nodes.cfg is the cause of this.
removed node 1 from it and it operates like it should again.
But... Now my setup is a single partitioned one.
(pretty useless).

Back to the drawingboard.

-R-

You appear to be on DB2 V8.2.2.
You also apear to have automatic storage tunred on.
Automatic storage, introduced as part of the SAP tuning, is not yet
enabled for DPF.
So what you need to do is turn automatic storage OFF.
Check your DBM CFG and db2set -lr. Something shoudl pop up that talks
about it.

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #3

P: n/a
Serge Rielau wrote:
You appear to be on DB2 V8.2.2.
You also apear to have automatic storage tunred on.
Automatic storage, introduced as part of the SAP tuning, is not yet
enabled for DPF.
So what you need to do is turn automatic storage OFF.
Check your DBM CFG and db2set -lr. Something shoudl pop up that talks
about it.

Cheers
Serge


That's correct, created a database with AUTOMATIC STORAGE YES.
Is there a particular reason that DB2 cannot do this at the moment?
And is it to be implemented any time soon, since it seem we might need it.

-R-
Nov 12 '05 #4

P: n/a
Jurgen Haan wrote:
Serge Rielau wrote:
You appear to be on DB2 V8.2.2.
You also apear to have automatic storage tunred on.
Automatic storage, introduced as part of the SAP tuning, is not yet
enabled for DPF.
So what you need to do is turn automatic storage OFF.
Check your DBM CFG and db2set -lr. Something shoudl pop up that talks
about it.

Cheers
Serge


That's correct, created a database with AUTOMATIC STORAGE YES.
Is there a particular reason that DB2 cannot do this at the moment?
And is it to be implemented any time soon, since it seem we might need it.

-R-

Delivery of this feature was _accelerated_ for SAP. SAPs requiremnet did
not include DPF for FP9.
DPF support is absolutely in plan for "a future release". If you need a
commitment on a specific release or a date you will need to work through
the offical channels.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #5

P: n/a
Serge Rielau wrote:
Delivery of this feature was _accelerated_ for SAP. SAPs requiremnet did
not include DPF for FP9.
DPF support is absolutely in plan for "a future release". If you need a
commitment on a specific release or a date you will need to work through
the offical channels.

Cheers
Serge


Ok... Once again: thank you for you clear reply.

-R-
Nov 12 '05 #6

P: n/a
Someone may have answered this already.
The message seem to indicate that your db was created with the automatic
storage funtion.
This is not yet supported in V8.2.2 (aka V8.1.9) for db's running with DPF
implemented.
HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Jurgen Haan" <ju****@fake.dom> a écrit dans le message de news:
42*********************@news.xs4all.nl...
Jurgen Haan wrote:
Hey.

I'm toying with a test setup at which I try to let 2 instances work
together as partitions. When I fire up both instances, and I try to
connect to a test database called parttest (a simple 1 table database).
I get the following exception:

2005-05-30-10.12.52.288076+120 I81657G479 LEVEL: Severe
PID : 4406 TID : 16384 PROC : db2agent
(PARTTEST) 0
INSTANCE: instusr NODE : 000 DB : PARTTEST
APPHDL : 0-68 APPID: *N0.instusr.050530081252
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:10
RETCODE : ZRC=0x800201A4=-2147352156=SQLB_AS_NO_MULTIPARTITION_SUPPORT
"Unsupported operation on database with automatic storage."

Since I'm pretty new on partitioning, and only have some practice
reference material and db2ic to educate myself on partitioning, I haven't
got a clue what the above mentioned exception means.
Surely it doesn't mean I can't use automatic storage in a partitioned
environment (does it?). I suspect the exception means I have no
partitioning, if so, I'm really in the dark here.

Does anyone have some good reading on partitioning? (eg url to an
e-book).

Thank you for any assistance.

-R-


Okay.. It appears my db2nodes.cfg is the cause of this.
removed node 1 from it and it operates like it should again.
But... Now my setup is a single partitioned one.
(pretty useless).

Back to the drawingboard.

-R-


Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.