Could it be that the standby is
auto-registering itself with the listener for the production database?
We've had a couple of incidents where a development DBA copied the init.ora file
from a production database configured for MTS. But the listener
parameters were not changed and all new co
I have 8.1.7.0 on Solaris 8 and also had this problem. Somehow the way I
get around this is to go back to the Primary db and reset the
log_archive_dest_2 to whatever the identifier of the standby db is. (even if
the log_archive_dest_2 is already set). Then I do the standby recovery,
then managed
