HELP! Need help with recovering standby database!

feelthy

New Member
Hi,
Being reasonably new to Progress, and being one of those people who picks all the slack, I have to look after our DRP server for the next 3 - 4 weeks. My issue is that I have 2 DRP databases which have been corrupted, and I have had to restore from production copies. No big deal. Where my issues start is the rfutil roll foward of AI files.
The log file shows output such as:

[FONT=r_ansi]
09:53:33 RFUTIL 0: Expected ai file number 1 but file specified is 1766 in sequ
ence. (8019)
09:53:33 RFUTIL 0: ** The database was last changed Mon Dec 12 23:31:33 2005. (
831)
09:53:33 RFUTIL 0: ** The after-image file expected Fri Dec 9 22:00:44 2005. (
832)
09:53:33 RFUTIL 0: ** Those dates don't match, so you have the wrong copy of on
e of them. (833)
09:53:33 RFUTIL 0: roll forward open /bkp/prod/cfp/ai/mfg.a6.20051209_233200 er
ror: -1
09:53:33 RFUTIL 0: rfutil -C roll forward session end. (334)
mfg
mfg.a6.20051209_233200 FAILED - Return Code 2
APPLIED mfg.a6.20051209_233200 at 13 Dec 2005 09:53 FAILED - PLEASE CHECK

There is some confusion around whether I should be truncating the BI file prior to the roll beginning...however if I do it, or don't do it, the messages are the same...

I know i'm missing something simple, can you guru's help?
[/FONT]
 
You should not truncate bi. You just need to roll forward after-images in the right order starting with the first after-image immediately after backup was taken.
 
Hmmm....seems the missing piece on information was the base version of the progress database versions. Traditionally, all of our db's are 91C, but we have some 91E databsaes now....
. setdlc 91e, then the restore, fixed it right up!

Thanks for your help.
 
I have the same error with a customer but they have Progress version 7!!

they use a backup (NOVELL) server to keep the databases (a sort of replication solution in v7 environment) but now they get this error.

can anyone help ??
** The database was last used Mon Sep 17 16:14:43 2007 (886)
** The before-image file expected wed nov 14 17:24:08 2007(887)
** Those dates don't match, so you have the wrong copy of one of them. (888)

The database (.db) and the before-image (.bi) files do not have the correct matching time stamps. This means you are trying to start PROGRESS with the wrong copy of one or the other of those two files. Find the correct files, then restart PROGRESS.

if it helps this is their start up procedure:

search add 1 vol1:\apps\has\dlc.v7\bin
load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has.db\HAS_STAM -S HAS_STAM_63 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has.db\HAS_MUTA -S HAS_MUTA_63 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has15.db\HAS_MUTA -S HAS_MUTA_15 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has93.db\HAS_MUTA -S HAS_MUTA_93 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has13.db\HAS_MUTA -S HAS_MUTA_13 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has17.db\HAS_MUTA -S HAS_MUTA_17 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has17p.db\HAS_MUTA -S HAS_MUTA_17p -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has5.db\HAS_MUTA -S HAS_MUTA_5 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has57.db\HAS_MUTA -S HAS_MUTA_57 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has94.db\HAS_MUTA -S HAS_MUTA_94 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has07.db\HAS_MUTA -S HAS_MUTA_07 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has19.db\HAS_MUTA -S HAS_MUTA_19 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has81.db\HAS_MUTA -S HAS_MUTA_81 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has94.db\HAS_MUTA -S HAS_MUTA_94 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has36.db\HAS_MUTA -S HAS_MUTA_36 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has7.db\HAS_MUTA -S HAS_MUTA_7 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has19.db\HAS_MUTA -S HAS_MUTA_19 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has53.db\HAS_MUTA -S HAS_MUTA_53 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has78.db\HAS_MUTA -S HAS_MUTA_78 -N tli -tcponly -L 2000 -autoexit
?load vol1:\apps\has\dlc.v7\bin\_mprosrv vol1:\apps\has\has09.db\HAS_MUTA -S HAS_MUTA_09 -N tli -tcponly -L 2000 -autoexit
search del 1
 
This is not the same error as the initial thread.

You have mismatched db and BI timestamps. That's a very different problem.

One way that this happens is when you use OS or 3rd party tools to make a backup without shutting down the db first. That seems very likely in this case.

In any event your database is not usable. You need to either find the correct .bi file (if it exists -- and it probably does not) or make a new backup with the database offline.

The best plan would be to use probkup to make your backups and prorest to restore them.
 
The problem here is.... there are no backups (wish there were). Probkup does not work in this case. Any other suggestions?
 
You should have migrated off Novell 15 years ago... That would be suggestion #1.

But I'm confused about what it is that is actually going on here. Suggestion #2 is that you open a new thread and carefully explain the actual problem and the environment that you have. Then we'll have a better idea of how to help you.

But really, get off v7 & Novell ASAP. That's a really, really bad place to be.
 
Back
Top