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 recovery. This probably explains why yours work after you bounce your Primary db. You must have the standby db location set in the init.ora file. What I do, however, is force a reset of the standby db location after I startup the standby db. This way I don't have to bounce my Primary db. Everything's scripted. Clear as mud? HTH. Ross
-----Original Message----- Sent: Friday, 22 February 2002 7:59 To: Multiple recipients of list ORACLE-L Fellow dba's, We have come across a weird problem with a standby database. Every time we issue "alter database mount standby database" on the standby database, the primary database fails to connect through listener. It becomes OK after primary database is shutdown and restarted — of course this can is not an acceptable solution since the standby will be opened every week for reporting. Anyone experience this before? Any direction would be appreciated. Thanks Stephen Andert Scottsdale, Arizona -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ross Collado INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
