just create a tablespace in DB2 with 8K page size along with 8k bufferpool
(& tempspace) maybe. The ensure that the DB user under which the openJPA
app is running has permissions to use this tablespace and you are now done
(best create the tablespace by connecting as the same DB User app uses)
You dont need openJPA to generate the DDL with the 'in tablespace XXX'
part. DB2 will automatically use that tablespace for the table as long as
the userID has permissions to use it
Mario
From: "seba.wag...@gmail.com" <seba.wag...@gmail.com>
To: users@openjpa.apache.org
Date: 09/29/2011 03:49 PM
Subject: Re: Wrong SQL produced by openJPA for create statement in DB2 -
SQL Error -286 while creating table
I think I have found at least one ressource that is referencing my problem:
http://server-demo-ec2.cloveretl.com/clover/docs/db2.html
Any other ideas or possible gotchas?
I could not find any additional params for the connection URL.
Are there any configuration params people know for the JDBC URL for DB2 ?
Thanks
Sebastian
2011/9/29 seba.wag...@gmail.com <seba.wag...@gmail.com>
> I did get the advice:
>
> *the pagesize of the tablespace is too small
> you need an 8k ts (and bufferpool and tempspace..)
> you can specify in create table ...... in tsname
> *
> => How can I specify the tablespace column for the create-statement
> generated by openJPA ?
>
> Thanks
> Sebastian
>
> 2011/9/29 seba.wag...@gmail.com <seba.wag...@gmail.com>
>
> Hi,
>>
>> I face a strange error when tables are created by openJPA 2.1.1 into DB2
>> (Version 9.7.x Express-C)
>>
>> OpenJPA produces this insert statements:
>>
>> CREATE TABLE roomclient (roomclient_id BIGINT NOT NULL GENERATED BY
>> DEFAULT AS IDENTITY, avsettings VARCHAR(254), broadcast_id BIGINT,
canDraw
>> SMALLINT, chat_user_room_id BIGINT, connected_since TIMESTAMP, firstname
>> VARCHAR(254), formated_date VARCHAR(254), isBroadcasting SMALLINT,
>> is_chat_notification SMALLINT, is_mod SMALLINT,
>> is_recording SMALLINT, language VARCHAR(254), last_login VARCHAR(254),
>> lastname VARCHAR(254), mail VARCHAR(254), official_code VARCHAR(254),
>> picture_uri VARCHAR(254), public_sid VARCHAR(254), room_enter TIMESTAMP,
>> room_recording_name VARCHAR(254), room_id BIGINT, scope
>> VARCHAR(254), streamid VARCHAR(254), swfurl VARCHAR(254), user_id
BIGINT,
>> usercolor VARCHAR(254), userip VARCHAR(254), username VARCHAR(254),
userport
>> INTEGER, userpos INTEGER, zombieCheckFlag SMALLINT, PRIMARY KEY
>> (roomclient_id))
>>
>> OpenJPA fails with this error: SQLCODE=-286, SQLSTATE=42727,
>> DRIVER=3.62.56
>> Es konnte kein Standardtabellenbereich mit einer Seitengröße von
>> mindestens "8192" gefunden werden, für den die Berechtigungs-ID
"DB2ADMIN"
>> eine Nutzungsberechtigung hat..
>> => The Create statement is obviously wrong.
>>
>> Our openJPA config looks like:
>>
>>
http://code.google.com/p/openmeetings/source/browse/trunk/singlewebapp/src/META-INF/db2_persistence.xml
>>
>> Anybody an idea what the error 286 means or what is wrong with the
create
>> statement?
>> Other tables are successfully created, it seems just this one fails
>> constantly.
>>
>> Thank you very much,
>> Sebastian Wagner
>>
>> --
>> Sebastian Wagner
>> http://www.openmeetings.de
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wag...@gmail.com
>>
>
>
>
> --
> Sebastian Wagner
> http://www.openmeetings.de
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wag...@gmail.com
>
--
Sebastian Wagner
http://www.openmeetings.de
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wag...@gmail.com
