Hello Novad, it is normal and expected behaviour that if an SQL statement cannot be executed because of the lack of space for permanent information, or the lack of space in the log, the execution halts but continues when there is a volume added (or space is freed by other means).
Your tool did simply wait for an response from the database (or until some time out happens). Regards Alexander Schr�der SAP DB, SAP Labs Berlin > -----Original Message----- > From: Novad Protikin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 29, 2005 12:52 PM > To: [email protected] > Subject: Nirvana instead of index > > (sorry I don't understand how I can add a post to a > certain thread) > > > Ok, I found the solution myself now. > > At the beginning I used a query tool that works with > ODBC. For some reason MaxDB doesn't produce an error > but lets the tool disappear into nirvana. > > After several fruitless attempts I tried my CREATE > INDEX using DBMCLI > > With that I finally got an error with error code. The > error code was NOT in the documentation (you folks at > MaxDb really make it hard). But from the message I > could deduce that the volume was full. After creating > another volume the index-creation finally worked. > > > > > > > > >Hi, > > > >would you mind posting the knldiag and the output of > >"dbmcli -d <dbname> -u <dbm,passwd> show all" perhaps > > >this will show whats going on on your system. > > > >Kind regards > >Holger > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ > > -- > MaxDB Discussion Mailing List > For list archives: http://lists.mysql.com/maxdb > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
