As I wrote just before to someone else. With the complete installation you have created a new data and a new log area. If you only overwrite the data area with a data recovery the log area belongs to the new instance.
There are two ways. The official way is to use "init config" (this deletes the log area) + "restore data". The other way is to use "restore data" + "util_execute clear log". kind regards Uwe > -----Original Message----- > From: Georg Schoepe [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 6. August 2003 14:46 > To: [EMAIL PROTECTED] > Subject: Can't start DB-Instance after 7.3->7.4-migration - > knldiag.err-infos > > > Hi, > > here the knldiag.err-log. > > 2003-08-06 14:36:47 0xA20 ERR 25 Log > DBIdentifier of DataVolume > (localhost:TEST_20020804_112745) and LogVolume (localhost:TEST_20020 > 2003-08-06 14:36:47 0xA20 ERR 25 Log 806_132854) > does not match > 2003-08-06 14:36:47 0xA20 ERR 64 Log RestartArchiveLog: > LogAndDataIncompatible > 2003-08-06 14:36:47 0xA20 ERR 60 Log RESTART > ERROR '3800' => > SHUTDOWN IS FORCED > 2003-08-06 14:36:52 --- Starting GMT > 2002-08-06 14:36:52 7.4.3 Build 025-123-046-179 > > regards > Georg > > > "Georg Schoepe" <[EMAIL PROTECTED]> schrieb im Newsbeitrag > news:[EMAIL PROTECTED] > > Hi, > > > > with many problems I made a migration of SAPDB with one of tree > instances. > > As you see below, at the end it seemed to be successful. > > But unfortunately no tables were there in SQL-studio, as I > expected - so I > > made a recovery of my cold-backup. > > This seemed to be successful too, but now I can't start the > DB-instance. > > > > Please help > > Thanks and greetings > > Georg > > > > > > > > --- > > dbmcli on TEST>db_admin > > OK > > --- > > dbmcli on TEST>util_connect > > OK > > --- > > dbmcli on TEST>util_execute INIT CONFIG > > OK > > --- > > dbmcli on TEST>util_activate DBA,DBA > > OK > > --- > > dbmcli on TEST>load_systab -ud DBA > > OK > > 0,OK: everything works fine > > 0,""C:\PROGRAMME\SAPDB\DEPEND_7.4\bin\x_python" > > "C:\PROGRAMME\SAPDB\DEPEND_7.4\env\lsystab.py" -d TEST -u > DBA,* -dompwd > DBA > > en ENG" > > Removing obsolete objects > > Installing Loader tables > > Installing messages and help > > Installing SYSDBA tables > > Installing comments for SYSDBA tables > > Installing precompiler tables > > Installing system tables for R3 backup information > > Installing ODBC and JDBC tables > > Installing system tables for ORACLE (V7) mode > > Installing data dictionary tables and views > > Installing synonyms for oracle system tables > > Installing comments on oracle sytem tables > > Installing tables for SQL Studio > > Installing suppose list > > Installing tables for WebAgent > > Installing tables for WebDAV > > Installing tables for WebDAV XML Indexing > > Installing DOMAIN tables > > Installing comments for DOMAIN tables > > Installing Views as replacement for SHOWs > > Installing Database Manager tables > > ================================== > > Installation successfully finished > > ================================== > > > > --- > > dbmcli on TEST>db_online > > OK > > --- > > dbmcli on TEST>util_release > > OK > > > > ############################################# > > After this I made a recovery of my cold-complete-backup with DBMGUI > > Now I have to restart the instance - but this fails: > > ############################################ > > --- > > dbmcli on TEST>db_online > > ERR > > -24895,ERR_SHUTDOWN: shutdown of database occured > > -71,connection broken > > > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general > _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
