It seems like you have a mission critical 15 TB system with the corresponding downtime requirement and in contrast to that you want to tinker with non SAP / Oracle certified solutions (i assume you refer to DBvisit Replicate) just to save a few bucks?
Triple-O was exactly designed for that - otherwise you can try to optimize your RMAN conversion procedure as 40 hours for 15 TB does not sound that well optimized neither.
SAP distribution monitor may also be a valid solution depending on the source data (ECC / BI) and your exact (downtime) requirements.
I want to move database from big endian to little endian. My database size is 15 TB. When I I use transport tablespace or data pump. I open database read only. it takes 40 hours. I want to minimize down time. What procedure can i adopt?
we already discussed a few possibilities (also enhanced features with cross-platform transportable tablespace) in this SCN thread:
However Oracle Golden Gate (O2O Triple-O - details in SAPnote #1508271) would be another option. By the way Oracle Streams will be deprecated with Oracle 12.1 and you should use Oracle Golden Gate instead - so the Oracle product path is clear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.