Hi Filip,
I assume, that your LogVolume has never been really created.
Please change the recovery command for the first data-backup
to
DB_ACTIVATE RECOVER <data-backup-mediumname>
kind regards, Martin
> -----Urspr�ngliche Nachricht-----
> Von: Filip Sergeys [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 15. April 2004 18:12
> An: [EMAIL PROTECTED]
> Betreff: standby database log backup recovery fails
>
>
> Hello,
>
> I'am trying to setup a standby database but only partially
> succeed to do
> so.
> These are the steps I perform:
>
> I create an instance for recovery using the DBMGUI. The instance
> installs successfully. I then stop at the moment the recovery wizard
> starts.
>
> I define the backup mediums also using the DBMGUI. 3 media are defined
> 1 parallel for the fullbackup called FULLBACKUP
> 1 for incremental backups called INCR
> 1 for log backups called ARCH
> (note the location of these media are not equally to the original
> database from which a standby is created)
>
> I stop the database db_offline and start it again db_admin (It has not
> been in operational state ever)
>
> I continue in the DBMCLI with importing the fullbackup
> recover_start FULLBACKUP DATA AUTOINGNORE -> succeeds (vtrace is
> available if somebody needs it)
>
> Then I import the incremental backup
> recover_start INCR PAGES -> succeeds also (vtrace available)
>
> Finally I want to import the log backups. I use the example in the
> documentation for standby database. Here troubles start
>
> First I need to know from which log backup to start.
> db_restartinfo -> error
> -24988,ERR_SQL: sql error
> -9209,System error: KB Log error
>
> ok, so I consult the backup history from the original database. Log
> backup number 399 is the first one after the last incremental
> backup. so
> I do:
> recover_start ARCH LOG 399 -> database shuts down!
>
> I want to recover the vtrace so I do: trace_prot abkx. output appended
> at the end.
>
> Question: what is wrong in the sequence of my actions? The
> database has
> not been in operational state since its creation.
> The goal is to have a standby database up and ready as much
> as possible,
> only importing the very last log backups at the moment it
> should go into
> operational state.
>
> Thanx,
> cheers,
>
> Filip Sergeys
>
>
>
> **************************************************************
> **********
> *** KERNPROT 7.5.0 2004-04-15
> 17:41:43 ***
> **************************************************************
> **********
>
> Input File: /var/maxdb/data/wrk/ECCENTXD/knltrace.dat
>
> ---------- from entry 1.6 to 1.8197 (from page 2 to 2)
> -----------------
>
> ===== T58 ===== nil.idnil
> ==================================1.6 page 2
> LogicalLogOffsets: 0 -> 4294967295
> FirstKnownSeq: [EMAIL PROTECTED]
> log info page not assigned
>
>
>
>
>
>
>
>
> --
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> * System Engineer, Verzekeringen NV *
> * www.verzekeringen.be *
> * Oostkaai 23 B-2170 Merksem *
> * 03/6416673 - 0477/340942 *
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe:
> http://lists.mysql.com/maxdb?> [EMAIL PROTECTED]
>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
