I have a developer with the following problem:
He tries to create a table with a long row definition and is told by DB2
that he needs a tablespace with 8K pages. He wants to use the default
tablespace USERSPACE1. I drop the tablespace andrecreate it with an 8K
pagesize and assign to it a bufferpool with an 8K pagesize. Now he is able
to create his table.
Now he tries to create a table with a normal sized row definition in the
default tablespace from a remote client and DB2 tells him that it cannot
find a tablespace with a pagesize of "at least" 4K that he has access to (he
is connected as the instance owner). He *can* however create the table
without error when connected to the database from the server side. If he
uses a 4K tablespace he can create the table from the client side.
Why is it that he can use the default tablespace for both table definitions
when connected locally on the server, but cannot create both when connected
remotely?
If anybody has any advice, I would be very grateful.
TIA
Brian
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
