This is a preview of a document which will be published soon. Because syntax and possibilities of log settings between 7.3 and 7.4 changed and even changed within 7.4.3 this short overview might help you.
Features in 7.3: "demo log mode" exists software mirroring of log area exists (dual log mode) Changed in 7.4.3.0: The "demo mode" does not exist. Instead there exists the command SET LOG DEVICE OFF/ON which disables redo log writing for transactions. This feature does not exist in earlier versions. The parameter LOG_MODE exists and you could set it to whatever you want but only SINGLE is internally used. Changed in 7.4.3.5: LOG_MODE DUAL is reimplemented again but with less functionality as in 7.3. Changed in 7.4.3.10: The parameter LOG_MODE cannot be set to DEMO. The parameter LOG_BACKUP [yes/no] was added. If this is set to "no" the log area is automatically overridden and no log backups are needed. This is a reimplementation of the "demo mode". Changed in 7.4.3.11: The parameter LOG_BACKUP is removed. A new command is introduced SET LOG AUTO OVERWRITE [ON|OFF] which can be executed in admin and online state. The view DB_STATE shows the actual state. The command SET LOG DEVSPACE [ON/OFF] is renamed to SET LOG WRITER [ON/OFF] Changed in 7.4.3.17: The parameter LOG_MODE is finally removed. Instead the parameter LOG_MIRRORED = YES/NO is introduced. It cannot be directly set with param_put because there exists the dbmcli command "db_addvolume", which enters the correct volume data as well. kind regards Uwe _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
