Re: Point-In-Time

Flashback Query can work across DDL's if you're using Flashback Data Archive to track changes to the table(s) in question. Have you confirmed that changing table definitions are what's causing the ORA-01466 errors?

And, what version of the database are you using?

Thanks,

-Kevin J

-- 
Kevin Jernigan
Senior Director Product Management
Advanced Compression, Hybrid Columnar
Compression (HCC), Database File System
(DBFS), SecureFiles, Database Smart Flash
Cache, Total Recall, Database Resource
Manager (DBRM), Direct NFS Client (dNFS),
Continuous Query Notification (CQN),
Index Organized Tables (IOT), Information
Lifecycle Management (ILM)
+1-650-607-0392 (o)
+1-415-710-8828 (m)

On 10/12/15 8:23 AM, Lyall Barbour wrote:


> Hi,

>   Our DW team has had a Logical Standby of the OLTP database they get 

> their data from for years now.  Each night, the SQL Apply on the LS 

> stops and they get a point in time view of transactions for the day. 

>  This has been a pet peev of mine since i've started working at my 

> current job.  I'd like to change it and i thought that Oracle 

> Flashback Query in the Primary database would get me what i want.  In 

> our testing we've been running into ORA-01466 errors often enough 

> where we could see it being a problem with an actual implementation of 

> our current new configuration of this work.

>   Does anyone have a better way of getting what the DW team needs on a 

> daily basis then what i've described?  All they really need is a 

> Point-In-Time view.

> Lyall Barbour

> -- http://www.freelists.org/webpage/oracle-l 



--
http://www.freelists.org/webpage/oracle-l