Juergen Sauer wrote: > Moin, > We did this: save a Database to DATASAVE using dbmcli. > Resored this Database like this, using dbmcli: > db_cold > util_connect $DBM > recover_start restore DATA > util_connect $DBM > util_execute clear log > db_restart > util_connect $DBM > backup_save data MIGRATION > backup_save initial MIGRATION > autosave_on > - --------------------------------------------- > After that action, we can not execute SQL commands like this: > > INSERT INTO RESOURCES (RESOURCE_TYPE_ID, TITLE, DESCRIPTION, > TEACHER_ONLY) > VALUES (1,'fdsfdfsfs','sdfsdf',0) > // > > This refuses to work, whith error code -8 Pos[1] = General > Error, Parse > Again, used from SQL Studio 7.3.00.1. > > After using this commads (from repmcli -b file) > // > drop table resources > // > //* ============================================================ */ > //* Table: resources */ > //* ============================================================ */ > create table resources > ( > resource_id fixed not null default SERIAL, > module_id fixed, > resource_type_id fixed, > special_id smallint, > title char(255), > description char(255), > keywords char(255), > filename char(255), > xlength float, > url char(255), > thumbnail char(64), > start_nc_level smallint, > end_nc_level smallint, > teacher_only smallint, > date_ins timestamp default TIMESTAMP, > date_upd timestamp default TIMESTAMP, > date_del timestamp default NULL, > deld fixed default 0, > admin_id fixed, > primary key(resource_id) > ) > // > INSERT INTO RESOURCES (RESOURCE_TYPE_ID, TITLE, DESCRIPTION, > TEACHER_ONLY) > VALUES (1,'fdsfdfsfs','sdfsdf',0) > // > > All of that worked fine and This works also from SQL-Studio. > > How can we fix this awful behavior ? > > Any idea what's going wrong here ?
No, not really. Some questions: - is it possible that the SQLStudio - Session was not closed before your backup/restore-try? - what did you do in the time between backup and restore? Did you do anything? Did you do some DDL on that table? Or did you just checked the backup/restore-behaviour without intermediate work? - can / would you like to reproduce it? If yes, the first step after restoring should be the switching on of the vtrace. Then after receiving error -8 we would like to see the whole vtrace not just the error-resulting command. see http://sapdb.2scale.net/moin.cgi/VTrace - can you select the table after restoring? That means: is there only trouble with insert or with all commands? - do you have some referential constraint/index on/for this table? Mmh, that should be all, I hope. Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
