Re: Ora-19906 when restoring user managed backup - stumped!

From: gs <gs_at_gs.com>
Date: Wed, 09 Sep 2009 16:43:38 GMT
Message-ID: <_WQpm.44312$PH1.15577_at_edtnps82>



gs wrote:
> joel garry wrote:
>> On Sep 8, 7:06 pm, GS <g..._at_gs.com> wrote:
>>> ps. database is 10.2.0.4 on windows 64 bit server.
>>
>> Wild guess after looking at metalink Note: 824213.1is that you did a
>> flashback of your prod database at some point, perhaps between when
>> you took the controlfile backup and the online backup?  Any clues in
>> the prod alert log?
>>
>> See 
>> http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/flashptr005.htm#sthref646 
>>
>> maybe if you specify an until time you can overcome an SCN ambiguity.
>>
>> jg
>> -- 
>> _at_home.com is bogus.
>> Cash of the Titans: Amazon, Microsoft and Yahoo versus Google:
>> http://www3.signonsandiego.com/stories/2009/sep/09/sparring-rises-over-googles-book-deal/?uniontrib 
>>

>
> Nope, no flashback done, and controlfile script is standard script I use
> using backup controlfile to trace. After digging through the prod alert
> log I am seeing a few of these:
>
> Wed Sep 09 10:07:31 2009
> Thread 1 cannot allocate new log, sequence 3255
> Private strand flush not complete
> Current log# 5 seq# 3254 mem# 0: E:\ORACLE\ORADATA\MYDB\MYDB\REDO5.LOG
> Current log# 5 seq# 3254 mem# 1: D:\ORACLE\ORADATA\MYDB\REDO5A.LOG
> Wed Sep 09 10:07:32 2009
> Thread 1 advanced to log sequence 3255 (LGWR switch)
> Current log# 6 seq# 3255 mem# 0: E:\ORACLE\ORADATA\MYDB\MYDB\REDO6.LOG
> Current log# 6 seq# 3255 mem# 1: D:\ORACLE\ORADATA\MYDB\REDO6A.LOG
>
> so I am wondering if this is somehow related.. looking at ways now to
> cure this particular error, it happens when I do a manual logfile switch
> as well.

update, according to metalink note:372557.1 this is normal expected behavior so.. Received on Wed Sep 09 2009 - 11:43:38 CDT

Original text of this message