Hi Mark, how do you create the index with the dbmcli? Do you use a sql session with sql_connect, sql_execute and sql_release? If you do so it's possible that this session gets a session timeout if it was to long idle after the creation of the index and all your changes were rolled back. So you you should send a commit after the creation to avoid this in the future or increase the session_timout parameter. If you use only sql_execute without any explicit session then the dbmcli will implicit open a session and close it after the command with a commit.
Kind regards Holger SAP Labs Berlin > -----Original Message----- > From: Mark Wong [mailto:[EMAIL PROTECTED]] > Sent: Freitag, 12. April 2002 17:32 > To: [EMAIL PROTECTED] > Subject: RE: Is this a bug with the create index statement? > > > Hi Holger, > > I used dbmcli to create the index, and it said "OK". I did > attempt this > on the same dataset with the same database paremeters on a > system with 8 > raw disks, which still took over 6 hours with the default database > parameters. > > It kind of sounds like if the database is taking too long, something > decides to time out? When I bumped up the DATA_CACHE and > _IDXFILE_LIST_SIZE, the index built in about 15 minutes. > > Mark > > On Fri, 2002-04-12 at 03:12, Becker, Holger wrote: > > Hello Mark, > > > > your trace shows a returncode "700 Session inactivity > timeout (work rolled > > back)". > > So it seems that the session in which you created the index > was rolled back > > because of idle time. > > But I wonder why the application didn't reported this error. > > So what application did you use? Did you use autocommit feature? > > > > BTW to improve index creation performance it could be > usefull to split your > > devspace > > into two devspaces also they are on the same harddisk. > > > > Kind regards > > Holger > > SAP Labs Berlin > > > > > > > -----Original Message----- > > > From: Mark Wong [mailto:[EMAIL PROTECTED]] > > > Sent: Donnerstag, 11. April 2002 17:53 > > > To: [EMAIL PROTECTED] > > > Subject: Is this a bug with the create index statement? > > > > > > > > > I have put a trace, that's too big to attach, here: > > > > > > http://www.osdl.org/archive/markw/index.txt.bz2 > > > > > > I attempted to build an index with DATA_CACHE and > > > _IDXFILE_LIST_SIZE set > > > to default values. dbmcli returned OK, but the index does > > > not exist, as > > > verified in the domain.indexes table. Raising the value > of DATA_CACHE > > > and _IDXFILE_LIST_SIZE to 81920 and 8192, respectively (if it > > > matters to > > > know), allows the index to be created properly. > knldiag.err does not > > > output any messages over the course of the attempted > index creation. > > > > > > Let me know if there is any more information I can provide. > > > > > > Thanks! > > > -- > > > Mark Wong - - [EMAIL PROTECTED] > > > Open Source Development Lab Inc - A non-profit corporation > > > 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 > > > (503)-626-2455 x 32 (office) > > > (503)-626-2436 (fax) > > > > > > _______________________________________________ > > > sapdb.general mailing list > > > [EMAIL PROTECTED] > > > http://listserv.sap.com/mailman/listinfo/sapdb.general > > > > > _______________________________________________ > > sapdb.general mailing list > > [EMAIL PROTECTED] > > http://listserv.sap.com/mailman/listinfo/sapdb.general > -- > Mark Wong - - [EMAIL PROTECTED] > Open Source Development Lab Inc - A non-profit corporation > 15275 SW Koll Parkway - Suite H - Beaverton OR, 97006 > (503)-626-2455 x 32 (office) > (503)-626-2436 (fax) > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
