upgrade to 9...
SQL> recover ... disconnect
hth
connor
--- "Orr, Steve" <[EMAIL PROTECTED]> wrote: >
Problem: How to keep a standby database in
> continuous managed recovery
> without having to maintain an open terminal session.
> (Version 8.1.7.2)
>
> When you execute the following...
>
-
I just started the databases up in the background.
Patrol keeps track of the databases but we have never
had a problem doing this. Had to write a custom
dbstart script though. Works fine but is unsupported
by Oracle.
--- "Orr, Steve" <[EMAIL PROTECTED]> wrote:
> Problem: How to keep a standb
On Friday 06 December 2002 18:29, Orr, Steve wrote:
[...]
> So then I tried nohup:
> --
> $ nohup sqlplus "/ as sysdba" @managed_recov.sql &
> [1] 23412
> $ nohup: appending output to 'nohup.out'
> [1]+ Exit 127 nohup sqlplus "/ as sysdba"
Quit whining =8-)
The behaviour is the same for any process that inherits it's stdin/stdout
and stderr from the parent. Once the parent (your shell) goes
away, the file handles are closed and the child has nothing to
talk to. You only half-solved the problem with the nohup. You
did the right thin
Problem: How to keep a standby database in continuous managed recovery
without having to maintain an open terminal session. (Version 8.1.7.2)
When you execute the following...
--
SQL> RECOVER MANAGED STANDBY DATABASE;
---
