Hello,
We have a warm-standby of one of our databases, and by this I mean a
server in constant recovery mode applying logs being shipped from a
primary to the warm-standby. Recently we had to bounce the standby
instance and I saw this error in our logs:
2009-04-27 07:11:21.213 GMT8261,
On Mon, 2009-05-11 at 13:50 -0400, sramirez wrote:
> Short of copying the data files elsewhere and doing a row-level
> comparison of the data, is there any way I can check to see if there is
> actual corruption in the warm standby server?
Right now, Warm Standby has same functionality as equi
> Right now, Warm Standby has same functionality as equivalent Oracle
feature - i.e. no way to confirm absence of corruption. However, WAL
records contain CRC checks that ensure the transferred data is correct,
which is more than most other replication techniques posess. Hot Standby
will allow
