Re: physical standby database managed/non-managed
- From: "Terry Sutton" <terrysutton@xxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 09:51:02 -0800
Sandeep,
If your network people are not swayed by the good advice you've received, to
answer your last question:
CONNECT / AS SYSDBA
SELECT MAX (sequence#) last_log
FROM v$log_history;
--Terry
> Hi,
>
> We need to implement physical standby database. Primary and standby
> will be in two separate networks behind their own firewalls. Security
> guys dont allow to ping from one server to other server. I can not
> create sqlnet connection either.
>
> So from primary I ssh to a hop server and from there I ssh to standby.
> Under given situation I assume that I can not set up data guard. Or is
> there any way I can implement data guard? Is any suggestion to network
> security folks that will let me connect from primary to standby
> without opening any security risk?
>
> I have started looking into alternative solution using non-managed
> standby. I created a standby database. I am copying the archived logs
> from primary manually and applying on standby. Standby running behind
> the primary acceptable here. Moving the archived logs will be
> implemented through a perl script that will be called from cronjob.
> In this script I have command "Recover standby database;" After that
> if I do AUTO it applies all archived logs and give ORA-00308 for next
> (not yet there) archived log.
> This is the way it is supposed to be.
>
> Is there any way that standby recover to the last available archived
> log and comes out cleanly? How can I query the last archived log file
> applied on the standby database?
>
> Thanks
>
> Sandeep
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
