Re: DATAGUARD: Primary 2 NODE RAC: Standby Single node Single instance

thanks yong,

Actually you were right, in our exuberance we were too impatient to see the data. We monitored the alert logs by opening a telnet session for the standby and the primary:

cd to bdump directory:

tail -f alert.log (on both primary and standby)

then on sql prompts did:

alter system switch logfile on the primary.

watched the alert log being populated for transfer of dbf file.

on the standby alert watched for registration.

Once we saw the registration on the standby (which sometimes takes more than a few minutes** and this the important bit...it TAKES more than FEW MINUTES**)
On the standby alert window wait to see a message like:

media recovery log path/name of log

then the log has been received and applied.

on standby:

alter system recover managed standby database cancel;

alter database open read only

and run your select.

Basically, that transport and recovery is not immediate when you do the log switch on primary. So a little patience was what we needed.

then in the other
yong321_at_yahoo.com wrote:
> wannabe DBA wrote:
> ...
> > Then on the standby:
> >
> > SQL>alter database recover managed standby database finish;
> > SQL>alter database open read only;
> > SQL>select * from testthiscarbuncle;
> >
> > table does not exist!
> >
> > It seems the logs are not being applied. Can someone give me some
> > pointers as to where i should look to diagnose this issue!!!?
>
> Is there anything in v$archive_gap on standby? Can you check Metalink
> Note:232649.1 for any clue? In short, you can wait for 1 minute before
> you check if the log is applied. Make sure parameters FAL_SERVER and
> FAL_CLIENT are set. If nothing helps, you have to manually apply the
> logs by alter database register logfile.
>
> Yong Huang
Received on Sat Jul 08 2006 - 03:17:29 CDT