The command "set log mode demo" was renamed (since V7.4.*) to "set log auto overwrite [on|off]" in admin or online mode.
Kind regards Uwe >-----Original Message----- >From: Dirk Zugenmaier [mailto:[EMAIL PROTECTED] >Sent: Wednesday, February 02, 2005 7:12 PM >To: Zabach, Elke >Cc: Dirk Zugenmaier; [email protected] >Subject: Re: AW: Instance_type changed after Upgrade > > >Zabach, Elke wrote: > >>Dirk Zugenmaier wrote: >> >> >>>Hi, >>> >>>after upgrading from SapDB 7.3.0.24 to MaxDB 7.5.0.16 we experienced >>>some troubles with Indexes not beeing used. So we upgraded to MaxDB >>>7.5.0.23. >>> >>>But now the Instance_type of the Database has suddenly changed. >>>Previously we used the BW-Type AFAIK (No Log since it is used for a >>>DataWareHouse) but now it has changed to OLTP (as it is defined in >>>cserv.pcf, since the BW-type does not longer seem to exist). >>> >>>The Documentation says, there is no way in changing it, but how did >>> >>> >>that >> >> >>>update change it? There must be another way then exporting all data >>> >>> >>and >> >> >>>creating a new instance. >>> >>> >>> >> >>Do not worry at all. >>As we have had some INSTANCE_TYPE defined (for future use), but in the >>meantime decided, not to use them, but to destroy three of >them, we had >>to change them in the parameter-files of the databases using them. >>As we did not use them in a special way (they were handled like >>INSTANCE_TYPE OLTP) nothing will work differently now because of this >>'changed' INSTANCE_TYPE. The 'change' was only done >internally to fulfil >>the constraint of allowed INSTANCE_TYPEs even for your database having >>had another one, which was destroyed. >> >>BW did use the LOG as OLTP does. >> >>Elke >>SAP Labs Berlin >> >> >Thanks alot. But when thinking back (and reading my own docs) I >remembered the Log-Mode to be set to demo mode (we have no need for a >log and it slows down way to much). When searching google for commands >to do so, the only thing I could find was "dbmcli -d ... -u ... >util_execute set log mode demo" but doing so only returns a message >saying an SQL-Error occured. Has this option been deactivatet as well? > >Thanks > >Dirk Zugenmaier > > > >-- >MaxDB Discussion Mailing List >For list archives: http://lists.mysql.com/maxdb >To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
