Oracle and Netezza works in totally different way like the way of working on primary keys. So if you are planing for a migration, even though you are replacing a tNetezzaInput to tOracleInput, you need to see the data fetch and performance since the optimizer works in different ways in both DBs.
In simple words, a Netezza specific operations in your code will not work in Oracle after migration. So unless your SQL is database neutral, you will have to do the testing of your flows for migration. There are no short cuts in it as it is DB specific constraints where Talend do not have any control.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
