Probably your target database contains log from an earlier installation. If you only recover the data area into the target instance log and data are not compatible to each other. You have to reinstall the target instance with the source data backup and you must not restart it until you have recovered all log from your source instance you need to.
Standby scenaries were discussed several times in the list so I think you will find examples if you search in the history or in the online documentation. Kind regards, Uwe >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] >Sent: Monday, March 22, 2004 1:49 PM >To: [EMAIL PROTECTED] >Subject: DBIdentifier of DataVolume > > >Hello, > >we use spdb 7.4.3.17 and make an import/recovery from an db >which is from >an other system. after the recovery (way=meduim), the db dont start no >more. > > >RestartArchiveLog: LogAndDataIncompatible >2004-03-22 13:27:43 21676 ERR 60 Log RESTART ERROR '3800' => >SHUTDOWN IS FORCED >2004-03-22 13:35:34 --- Starting GMT >2004-03-22 >12:35:34 7.4.3 Build 017-123-039-277 >2004-03-22 13:35:47 22040 ERR 25 Log DBIdentifier of DataVolume >(vmware:WTEST_20040322_100914) and LogVolume >(ints1035:WEBNIX_20030507_111105) does not >2004-03-22 13:35:47 22040 ERR 25 Log match >2004-03-22 13:35:47 22040 ERR 64 Log RestartArchiveLog: >LogAndDataIncompatible >2004-03-22 13:35:47 22040 ERR 60 Log RESTART ERROR '3800' => >SHUTDOWN IS FORCED > >How we can change the DBIdentifier of DataVolume/LogVolume? > >Or what is the best solution to import an new db into a running system? > > >regurads >bjoern ramann [...] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
