Hello Eduard,
MaxDB changes persistent formats between builds too and implicitely migrates data.
So it's forbidden to use data of a newer version with older software.
Only for supporting special recovery szenarios our development support/developers can
decide if a downgrade is possible.
If it is possible the dev-support has to patch the version in the data.
So for a standby you must use the same softwareversion.
Kind regards
Uwe
-----Original Message-----
From: Eduard M [mailto:vef206@stripped]
Sent: Freitag, 12. Januar 2007 11:31
To: Döhr, Markus ICC-H
Cc: maxdb@stripped
Subject: Re: Restored database does not contain backup data!
Martin,
I see the following at the end of KNLDIAG.ERR. Does it means that master
version is 7.6.00.32 and standby version 7.6.00.27 and because of that it
does not work? (but this is only a difference in build number).
I'll attach full logs in another email.
2007-01-12 11:16:49 15952 ERR 11599 BTRACE ----> End of Stack Back Trace
<----
2007-01-12 11:16:49 15952 ERR 7 Messages Begin of dump of registered
messages
2007-01-12 11:16:49 15952 ERR 20000 Kernel Assertion of state The software
version is too old failed!
2007-01-12 11:16:49 15952 ERR 4 KernelCo + The persistent version is:
Version = 7.6.0.32
2007-01-12 11:16:49 15952 ERR 8 Messages End of the message list
registry dump
2007-01-12 11:16:49 15952 ERR 11196 DBCRASH vabort:Emergency Shutdown,
Task: 48
2007-01-12 11:16:50 0 ERR 12006 DBCRASH Kernel exited without core and
exit status 0x200
2007-01-12 11:16:50 0 ERR 12010 DBCRASH Kernel exited exit code 2
2007-01-12 11:16:50 ___ Stopping GMT 2007-01-12
09:16:50 7.6.00 Build 027-123-124-939
Eduard
On 1/11/07, Eduard M <vef206@stripped> wrote:
>
> Markus,
>
> I get the following error when I try to execute db_warm:
>
> dbmcli on STANDBY>db_warm
> ERR
> -24895,ERR_SHUTDOWN: shutdown of database occured
> -24994,ERR_RTE: Runtime environment error
> 6,connection broken server state 6
>
> Eduard
>
> On 1/10/07, "Döhr, Markus ICC-H" <Markus.Doehr@stripped> wrote:
> >
> > > Then I restore it from the backup file and activate:
> > >
> > >
> > > recover_start burvis
> > > db_activate dba,dba
> > > load_systab
> >
> > Try this:
> >
> > medium_put burvis /opt/sdb/backup/BURVIS_COM FILE DATA
> > db_activate recover burvis
> > db_warm
> > load_systab
> >
> > db_activate will activate, format the devspaces (which you just
> > recovered)
> > and as result you have an empty database.
> >
> >
> > Greetz,
> >
> > SIEGENIA-AUBI KG
> > Informationswesen
> >
> > i.A.
> >
> > Markus Döhr
> > SAP-Competence Center/Basis
> >
> > Tel.: +49 6503 917-152
> > Fax: +49 6503 917-7152
> > E-Mail: markus.doehr@stripped
> > Internet: http://www.siegenia-aubi.com
> >
>
>
