I'm afraid I have no DB2 to test :( thought something wrong with RoomClient.
Will try to get free (or demo) version of DB2 to test. On Thu, Sep 29, 2011 at 14:45, [email protected] <[email protected]>wrote: > I mean DB2 => IBM DB2 Express-C Version 9.7.x > The error is followed by another bunch of errors and Openmeetings does not > boot complete at all. > So at the moment DB2-database is no more available as install option ... > > However I will investigate also on openJPA list... > > > 2011/9/29 Maxim Solodovnik <[email protected]> > >> Hello Sebastian, >> >> RoomClient is not stored in the DB right now (I'm currently implementing >> it) >> so we can ignore this error for now. >> While testing migration of RoomClient to the DB I'll test DB table >> creation. >> >> >> On Thu, Sep 29, 2011 at 14:24, [email protected] < >> [email protected]> wrote: >> >>> Maxim, >>> >>> have you seen this error before, its thrown when you are using DB2 as >>> database with OpenMeetings while openJPA tries to create the tables. >>> >>> ---------- Forwarded message ---------- >>> From: [email protected] <[email protected]> >>> Date: 2011/9/29 >>> Subject: Wrong SQL produced by openJPA for create statement in DB2 - SQL >>> Error -286 while creating table >>> To: [email protected] >>> >>> >>> 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 >>> [email protected] >>> >>> >>> >>> -- >>> Sebastian Wagner >>> http://www.openmeetings.de >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> [email protected] >>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > > -- > Sebastian Wagner > http://www.openmeetings.de > http://www.webbase-design.de > http://www.wagner-sebastian.com > [email protected] > -- WBR Maxim aka solomax -- You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en.
