Re: Log apply services with RMAN

>
> My guess is there were no transactions in that log, since it was able
> to apply later logs. My other guess is a bug that didn't update
> whatever archived_logs looks at. In your original production alert
> log, does it say which thread 51112 was? If thread 1, no problem
> (oracle handled it), otherwise there may be future stickiness. How
> much time elapsed between creation of logs 51111,2 and 3? What does
> the standby alert log say about those three?
>
> jg
> --
> @home.com is bogus.
> "'Scuse me, while I kiss this guy!" - Jimi Hendrix, pointing at bass
> player, in concert.

Hello and thank you for your response.
In the primary server it was thread 1.
15 minutes past between 51111,2 and 3

Upon further review of the alert log on the standby system, Here's what happened.
I had issued a RECOVER AUTOMATIC STANDBY DATABASE. As it got to the point where Oracle was looking for sequence 51112 which it could not find since it hadn't been created on the primary yet and sent over, I hit CANCEL. Then I issued the statement to start managed recovery operations. The next statement in the alert log is the background recover operation is looking for sequence 51113. Could this be the problem and if so why? Here's an portion of the alert log from the standby:

ALTER DATABASE RECOVER automatic standby database Media Recovery Start
Mon Apr 30 14:01:50 2007
Media Recovery Log /oracle/PRD/saparch/PRDarch1_51110.dbf Mon Apr 30 14:02:04 2007
Media Recovery Log /oracle/PRD/saparch/PRDarch1_51111.dbf Mon Apr 30 14:02:16 2007
Media Recovery Log /oracle/PRD/saparch/PRDarch1_51112.dbf Errors with log /oracle/PRD/saparch/PRDarch1_51112.dbf ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
Mon Apr 30 14:03:48 2007
ALTER DATABASE RECOVER CONTINUE DEFAULT Mon Apr 30 14:03:48 2007
Media Recovery Log /oracle/PRD/saparch/PRDarch1_51112.dbf Mon Apr 30 14:04:01 2007
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Apr 30 14:04:04 2007
ALTER DATABASE RECOVER CANCEL
Mon Apr 30 14:04:04 2007
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL Starting ORACLE instance (normal)
Mon Apr 30 14:04:10 2007
ALTER DATABASE MOUNT STANDBY DATABASE
ORA-1100 signalled during: ALTER DATABASE MOUNT STANDBY DATABASE... Mon Apr 30 14:04:10 2007
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process MRP0 started with pid=11
MRP0: Background Managed Standby Recovery process started Media Recovery Waiting for thread 1 seq# 51113 Mon Apr 30 14:04:16 2007
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DI Mon Apr 30 14:04:16 2007
ALTER SYSTEM SET log_archive_dest_2='' SCOPE=MEMORY; Mon Apr 30 14:04:16 2007
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE AVAILABILITY Completed: ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE AV Mon Apr 30 14:07:46 2007
Media Recovery Log /oracle/PRD/saparch/PRDarch1_51113.dbf Media Recovery Waiting for thread 1 seq# 51114 Mon Apr 30 14:09:27 2007
alter database register logfile '/oracle/PRD/saparch/ PRDarch1_51112.dbf'
Mon Apr 30 14:09:27 2007
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE Register archivelog /oracle/PRD/saparch/PRDarch1_51112.dbf already exists
ORA-16089 signalled during: alter database register logfile '/oracle/ PRD/sapar.. Received on Tue May 01 2007 - 07:37:19 CDT