I also ran into this error before. Why is it that one is *forced* to do a backup after a load? I mean if I load a database for test reasons a full backup may just be a waste of time.
I would suggest do make this "feature" optional and enabled by default, not mandatory. Or is there a technical reason? > -----Original Message----- > From: Strahl, Torsten [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 5. Dezember 2002 19:26 > To: 'Eirikur S.Hrafnsson' > Cc: '[EMAIL PROTECTED]' > Subject: RE: Table is read only! > > > Hi, > you should run a full data base backup. > After successful execution the tables will > be writeable again. > > Regards, > Torsten > > SAP DB, SAP Labs Berlin > > -----Original Message----- > From: Eirikur S.Hrafnsson [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 5. Dezember 2002 17:58 > To: [EMAIL PROTECTED] > Subject: Table is read only! > > > Hi > > After successfully exporting and importing a user between > databases(thanks to the sapdb team!) I found out that the imported > users tables a read only?? How can I fix this? > > Best regards > > Eirikur Sveinn Hrafnsson > [EMAIL PROTECTED] > Chief Software Engineer > idega Software, http://www.idega.com > > _______________________________________________ > 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 > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
