This content has been marked as final. Show 7 replies
Its all depends upon how much downtime you will get for the migration ?1 person found this helpful
If you want to use the cross platform migration you need to place the tablespaces in readonly mode which requires a downtime for app perspective. If you get a enough downtime window then you can use Transportable tablespaces. You may also consider about creating a NFS mount point between the source and target with good network bandwidth.
If you don't get enough downtime then you probable need to implement goldengate or streams.
start capturing changes using the golden gate
Perform initial load using the export/import ot datapump
apply the changes through golden gate
sync the source and target
But you may want to check what kind of datatypes your database has, Some specific datatypes may not supported by golden gate
Hi Epikto,1 person found this helpful
The Oracle Goldengate its the best solution for you:
Goldengate works in several platforms (including big and little endian transformation), enabling high availability solutions, real-time data integration, transactional and etc...
I will look at goldengate and see if it can meet our needs. However there may not be a consistent reliable connection between network endpoints
Goldengate may be the best solution. However since it provides continuous data synchronization you need to consider the demands on your hardware for this.
Pl also be aware that GG licenses are not cheap - if the cost is justifiable, then it is a viable solution
I just did a non-downtime migration utilize goldengate , transportable tablespace from standby db of Production.
Worked out like a charm.
It all depends on how much downtime you have!
Goldengate its best solution for the minimum downtime, but need the network very fast and reliable.
In this case you really need use the cross platform tablespace migration or using the expdp/exp (using parallel for more performance) tools, but using those you need more downtime.