Hi Olaf, In this very old release you have to do:
In dbmcli: Util_execute init config Recover_start ... Db_warm Db_state Bye You are receiving SQLM.en: ENG -8003 Log and data must be compatible because the log volume is ot initialized. Kind regards Uwe P.s. BTW you should upgrade to 7.5! >-----Original Message----- >From: Olaf D�ring [mailto:[EMAIL PROTECTED] >Sent: Monday, April 25, 2005 1:07 PM >To: [email protected] >Subject: Re: AW: "recover with initialization" with dbmcli > >Hi, > >Am Montag, 25. April 2005 12:34 schrieb Brunzema, Martin: >>... >> in Release 7.3 you need the logvolumes (formerly call logdevspaces) >> or a logbackup for a restart. The only way to avoid this is to >> use a databackup with checkpoint (i.e. without open transactions) >Yes, I do a "backup_start mediumname MIGRATION" on the source Database, > >> Also you need to issue the command "db_warm" after datarecovery. >after that I do a "db_warm", but the answer is: >ERR >-24988,ERR_SQL: sql error >-8003,Message not available > >Whats wrong? > >Olaf >-- >Dipl. Inform. (FH) Olaf D�ring >-Systemadministration- >Landeskontrollverband Westfalen-Lippe e.V. >Nevinghoff 40 >48147 M�nster > >Telefon: 0251 / 23007-28 >Fax: 0251 / 23007-50 >E-Mail: [EMAIL PROTECTED] > >-- >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]
