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
