If the log can not be backuped because there does not exist any unsaved log or because it is forbidden to backup log (e.g. backup history is lost) is currently reported as the same error (-123). In the current development version this is distinguished and if this change is compatible with our tools in older releases the change is ported to older releases too.
Kind regards, Uwe > -----Original Message----- > From: Dr. Ralf Czekalla [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 8. Juli 2003 18:39 > To: Hahn, Uwe; Brunzema, Martin; [EMAIL PROTECTED] > Subject: Re: log full > > > Hi Uwe, > Hi Martin, > > "Hahn, Uwe" wrote: > > > > You have to do a complete data backup to start your backup history. > > After that you are allowed to explicitly backup log or > enable the autolog. > > kind regards > > Uwe > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > Sent: Dienstag, 8. Juli 2003 16:41 > > > To: [EMAIL PROTECTED] > > > Subject: log full > > > > > > > > > > > > Hi, > > > > > > after upgrading the sapdb from 7.3.?.33 to 7.4.0.25 (on nt) > > > autolog was > > > deactivated - sadly without being noticed by anyone. As a > > > consequence now > > > the log is full. > > > What I tried to overcome this situation: > > > -reactivate the autolog via dbmcli: I received the error 'sql > > > error, 123 no > > > more log to save'. > > > -define a new medium for backing up the log. But backing up > > > the log doesn't > > > work, the error message as well: 'sql error, 123 no more > log to save' > > > > > > So what could I do now? > > > > > wouldn't it be better to get a little bit more significant > error message > here - maybe "backup history lost" ??? > Or is it already changed in one of the next paches ? > > Ciao Ralf > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
