Microsoft Connector for Oracle is released for SQL Server 2019 Preview

lupji , we've been using the new Microsoft Oracle connector and SQL 2019 as a target for a while now without connection issues. But we don't use tnsnames.ora, rather we put the service name into the connection string. So the connection string value look similar to: 

SERVER=ourServerName.oracleoutsourcing.com:1521/ourServiceName.oracleabc.com;ORACLEHOME=;ORACLEHOME64=;WINAUTH=0

Have recently upgraded to

Microsoft Connector for Oracle - 15.0.2000.110

Visual Studio - 16.7.3

SQL Services Integration Services (VS Extension) - 3.9 (aka 15.0.2000.128)

SQL 2019 - CU5 and CU7

We did have problems using a project level connection managers, so we always use a package level connection manager. Not sure if this is still an issue. 
Have both 32-bit and 64-bit Oracle connectors installed on development machines, and the 64-bit on the production server. We haven't had to run the package in 32-bit mode.