Are you basically loading Oracle, but want to keep a synchronized copy in Teradata? What happens when the Oracle piece is retired in favor of just the Teradata side?
You could consider making all transformation processes create insert and update files per table, that way you just need loading jobs for both targets. Any scripted processes for the Oracle side have to be ported to the Teradata side. Don't try to have a single job simultaneously write to Oracle and Teradata, that would be a big mistake because that type of job is difficult to restart/re-run and is probably a slow performer because of coordinate handshaking.
In the long run, just look to convert from one to the other. The given dual-target strategy is difficult ot sustain.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle