Heinrich, Tilo wrote:
hello tilo!
As was confirmed by a colleague, you should not worry about:
2005-01-27 16:44:37 18778 ERR 8 AdminERROR 'cancelled' CAUSED
EMERGENCY SHUTDOWN
That is the "normal" side effect of a recover_cancel in newer releases. So your script has to start the database a
t the database after every recover_cancel again.
Best regards,
Tilo Heinrich
SAP Labs Berlin
>-Original Message-
>From: Raimund Jacob [mailto:[EMAIL PROTECTED]
>Sent: Thursday, January 27, 2005 4:34 PM
>To: Filip Sergeys
>Cc: MaxDB List
>Subject: Re: scripted log back
On Thu, 2005-01-27 at 16:33, Raimund Jacob wrote:
Filip Sergeys wrote:
hey Filip, * !
i created my own script now, your one was of great help. here is what i
made differently:
> 2) dynamically build a command script that will be executed by dbmcli in
> the v
Filip Sergeys wrote:
hey Filip, * !
i created my own script now, your one was of great help. here is what i
made differently:
2) dynamically build a command script that will be executed by dbmcli in
the very last step. Start with bringing database in admin mode and do
util_connect
that's what i d
On Thu, 2005-01-27 at 11:32, Raimund Jacob wrote:
Filip Sergeys wrote:
hello!
> 2) dynamically build a command script that will be executed by dbmcli in
> the very last step. Start with bringing database in admin mode and do
> util_connect
this is what i wa
See my comment in between your reply.
On Thu, 2005-01-27 at 11:32, Raimund Jacob wrote:
Filip Sergeys wrote:
hello!
> 2) dynamically build a command script that will be executed by dbmcli in
> the very last step. Start with bringing database in admin mode and do
> ut
Filip Sergeys wrote:
hello!
2) dynamically build a command script that will be executed by dbmcli in
the very last step. Start with bringing database in admin mode and do
util_connect
this is what i wanted to do "interactivly" so that the controlling
script notices errors when they happen. but cre
Hi Raimund,
I have attached a script we use to obtain the same result as you want,
maybe you can use some ideas of it.
I solved to problem of knowing which backup file to load next a little
different by keeping some kind of counter in a separate file (the
filename actually contains the counter eg:
hello tilo, all!
now, is it correct that the approach is this: scan the output of
backup_history_list for the last log id that was succefully imported.
then identify all logbackup-files with an extension that is
numerically higher than this and recover_start for each of them.
If you end log re
Heinrich, Tilo wrote:
hello!
now, is it correct that the approach is this: scan the output of
backup_history_list for the last log id that was succefully imported.
then identify all logbackup-files with an extension that is
numerically
higher than this and recover_start for each
of them.
If
Hello Raimund,
>now, is it correct that the approach is this: scan the output of
>backup_history_list for the last log id that was succefully imported.
>then identify all logbackup-files with an extension that is
>numerically
>higher than this and recover_start file> for each
>of them.
If y
hello, *!
i'm still playing around with log backups and recovery of them in a
standby instance. i now have a little script that triggers a log backup
and can tell if it worked, an error occured or no backup was required.
now i want to write script that (given a directory with log backups)
decid
12 matches
Mail list logo
