|
Right after you initiate the "recover managed standby database disconnect"
command, your standby database is attempting to resolve the gap sequence between the time of the backup used to create the standby and the current archivelog according to the controlfile of the primary database. This is fine, but notice that you immediately receive an error saying "Failed to request gap sequence." It is very likely that the archivelog on the production server (that contains the thread #1 node) has been moved or compressed, so the primary database cannot find it to complete the request.
Check the alert log of the primary database. This will provide details on what is going on, most likely in a trace file created on the primary server. If it is indeed a matter of the archivelog being moved, either move it back to the original location on the primary server or register a copy on the standby server (ALTER DATABASE REGISTER LOGFILE 'file_name').
Good luck,
Bill
|
