I've been able to isolate the failure point to be when the OS does a non-clean shutdown. After a Windows failure or hard shutdown (power failure/unplug of box/hard reset/etc) - when XP comes back up, the table is inaccessible. I should mention that the data on the XP machines does not need to be resilient (it's copied from a resilient/backed-up source, and is completely refreshable), so we're operating the SAP installs with LOG OVERWRITE to ease maintenance.
To attempt to find a workaround, I've also played around with taking SAP down before the OS shutdown hoping that would clear the problem. No luck. Vtrace has proved difficult - as I'm running out of the "Program Files" directory, and SAP has problems with the " " space. I'm also not certain if my discovery above still requires a Vtrace to decipher. Any clues as to a possible solution or workaround? Thanks. > On Win XP SAP 7.4.3 Build 17, I'm getting an Invalid sequence for DML and DDL statements (-3007) > when attempting a select from a given table. The error comes up via both JDBC and ODBC calls with > any select from the problem table. > > Documentation gives very little information on this error - it simply states "Repeat the QUERY and FETCH" > which obviously does no good. The problem goes away by dropping and recreating the table, but that's not > ideal by any stretch of the imagination. > > Is this an error at the parse phase? ie if I flush the sql pool, might that help? > Typically, when there's DB catalog corruption, I get an AK catalog error - but could > this be the problem nonetheless? > > Any insight would be appreciated. If possible please provide an example how to reproduce the problem. Additionally a vtrace (see http://sapdb.2scale.net/moin.cgi/VTrace) from the problem and the knldiag.err file could be helpful. Kinde regards, Holger SAP Labs Berlin I've experienced the same problem on linux with SapDB 7.4.3 Build 17. If i made selects on one table a got the same error message. If i modified the select so that i only get one result it works. SELECT * FROM sample_table where id > 0 fails with the error Invalid sequence for DML and DDL statements (-3007) SELECT * FROM sample_table where id = 1 SELECT * FROM sample_table where id = 2 SELECT * FROM sample_table where id = 3 works. I've written a little programm which creates a new table and copies all data from the "corrupt" table. The new table works, so the data seems to be ok. Even dropping the corrput table doesn't work. Michael usually this error should not be reproducable with several select at different times. If this occurs, the catalog is somehow confused, but you will usually have no chance to influence this by flushing or the like. And there are possibilities where no AK catalog error, but that one mentioned above will occur. It sounds as if you had this error several times, each time starting with a freshly created table, doing something and then resulting in that error reproducable. Is that true, can you reproduce that effect from scratch table? Or. if you cannot reproduce it from scratch, can you please make up your mind what you did between the last correct insert/update/delete/select on that table and that error, all commands (even those resulting in an error) done for that table explicitly or implictly (dropping a foreign key or the whole table with a foreign key in, where your special table is the referenced one) are of interest. Then we/I would be VERY interested in that table/index/foreign key definition and the doing between creation of that table/last good command and that error. Perhaps some sequence of ddl/dml is able to confuse the catalog. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
