Hi,
> Ok, I understand how the dual log works, why you should use it and have > that all setup dandy but what is baffling me is the Autolog feature of > sapdb. Can someone explain the inner-workings of this feature > (what-when-where-why) and any other pertinent information in regards > to this feature? when you change data in the database, these changes are logged on the log-volume. This LogVolume can become full. In this state it is not possible anymore to change any data, because the changes cannot be logged. In order to free space on the log-volume, one has to save it into log-backups. This can be done automatically by the feature autolog. You define a LogSegment size (default 1/3 of the LogVolume size) and the log is saved in chunks of this size in versioned files (i.e. numbered files). A Log-Save is started when log_segment logpages are written and can be saved. > I have read the user manual and all that biz but beyond it saying you > should use it I did not see any information as to how it works, when > it writes, how you should back it up, etc. > Also, if someone knows how to make the autolog turn on automatically > after a restart/reboot for a db running on Linux (cause the dbmgui > says it won't) I would appreciate that info too. autolog can at the moment only started manually or by adding a dbmcli-command to a startup-script. regards, Martin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
