The mistake is to "activate" the instance. In this moment you created a new instance which has written log. If you then recover data from a different instance this will cause the "Db identifier mismatch" error.
Your script should look like this: [...] >medium_put completeF complete FILE DATA 0 0 YES >db_cold >util_connect >util_execute INIT CONFIG >recover_start completeF DATA >db_warm >load_systab -ud dba [...] Kind regards, Uwe >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Sent: Tuesday, March 02, 2004 9:27 AM >To: [EMAIL PROTECTED] >Subject: Restore Problem: db_ident mismatch > >Hi, >I need to recover a database on an other db server using an complete >backup. >Domain name, server name and database name differ from the origin system. > >To do the job, I create a new database instance and want to recover its >content >from the backup medium. I am able to do this using the dbm gui's >installation >wizard using the "create for recovery" option. > >But I am not able to do this using a script: after the sucessfull recovery >I always get an "db_ident mismatch" error when I try to set the instance >into >"warm" mode. > >I am using Kernel 7.3.0 Build 024-000-000-000 but I hope to get an answer >here. > >Here is my script: > >--------------------------------------------------------------------------- >----- >param_startsession >param_init OLTP >param_put LOG_MODE SINGLE >param_put MAXDATADEVSPACES 10 >param_put MAXDATAPAGES 10000 >param_put MAXUSERTASKS 10 >param_checkall >param_commitsession >param_adddevspace 1 SYS SYS_001 F >param_adddevspace 1 DATA DAT_0001 F 65536 >param_adddevspace 1 LOG LOG_001 F 13107 >db_start >util_connect >util_execute INIT CONFIG >util_activate dsa,dsa >load_systab -ud dba >medium_put completeF complete FILE DATA 0 0 YES >db_cold >util_connect >recover_start completeF DATA >db_warm >--------------------------------------------------------------------------- >----- > > >All commands return OK (yes, I have copied the backup file into the right >place >before running the script, recover_start returns OK), but the last db_warm >returns: >--------------------------------------------------------------------------- >----- >>db_warm >ERR >-24988,ERR_SQL: sql error >-8003,Message not available > >--------------------------------------------------------------------------- >----- > > > >Here is the corresponding knldiag.err: >--------------------------------------------------------------------------- >----- >Date Time TID(hex) Typ MsgID Label Message-Text >--------------------------------------------------------------------------- >----- >2004-03-01 17:28:21 --- Starting --- >2004-03-01 17:29:26 --- Starting --- >2004-03-01 17:29:43 0xA84 ERR 52444 LOG db_ident mismatch > > >Does anyone know the trick? How can I initialize a database without >starting it, >so that I can use the backup file from the old server? > >Thanks, > >R�diger > > > >-- >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]
