DB2 9.1 Problem on a new server
Has anyone run into the following error while running the repotools
-createTable command on 0.6M2a on Red Hat? I think its a problem with DB2 not Jazz as it fails no matter what location I specify for the tablespace. Syntax error or access rule violation SQL: CREATE TABLESPACE CONTENTTS MANAGED BY DATABASE USING (file /data/databases/jazz/db2inst1/NODE0000/JAZZ/tablespaces' 250000) SQL Exception #1 SQL Message: DB2 SQL error: SQLCODE: -298, SQLSTATE: 428B2, SQLERRMC: null SQL State: 428B2 Error Code: -298 I am running the repotools.sh as db2inst1 (the instance owner) and the directory permission are as follows... drwxr-xr-x 2 db2inst1 db2grp1 4096 Sep 24 16:46 tablespaces Not that it should matter, but /data is a LVM volume. |
3 answers
Tadayuki YOSHIDA wrote:
Hello, have you solved the problem? Leaving the tablespace.location set to 'content_tablespace' did work. End result is it created the tablespace under the directory where I created the database. It would appear that one doesn't have to modify this property so long as your happy with the tablespace name being content_tablespace. Should this be written up as bug? I'm not convinced it still isn't a issue with the DB2 setup. -Mark |
I had the same problem and indeed it was permissions. The easiest way to determine if it is indeed permissions is point to a subdirectory of /tmp with the repotools and see if you get the same problem.
|
amcohen.us.ibm.com wrote:
I had the same problem and indeed it was permissions. The easiest way Yeah, I thought of that after my post. So I tried creating /tmp/tspace using the db2inst1 user id and it still fails with the same error message. It would appear that the location I'm specifying doesn't matter. I'm at a complete loss. Syntax error or access rule violation SQL: CREATE TABLESPACE CONTENTTS MANAGED BY DATABASE USING (file '/tmp/tspace' 2 50000) SQL Exception #1 SQL Message: DB2 SQL error: SQLCODE: -298, SQLSTATE: 428B2, SQLERRMC: null SQL State: 428B2 Error Code: -298 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.