Oracle data sources can be connected via linked server, ODBC, SSIS or PowerShell.
SSIS is currently the recommended way of connecting to these types of sources.
The PowerShell connection method does not require the Oracle OLEDB provider. This connection method will automatically install and use the Oracle.ManagedDataAccess.dll.
Both linked server and SSIS require a valid connection to an Oracle data source via Oracles OLEDB provider.
This Oracle OLEDB provider along with Oracle Client Tools can be installed from here: (Administrator install mode is recommended)
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-win64soft-094461.html (Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64))
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-win32soft-098987.html (Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (32-bit))
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html (Oracle Database Client (12.1.0.2.0) for Microsoft Windows (x64))
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html (Oracle Database Client (12.1.0.2.0) for Microsoft Windows (32-bit))
The Oracle connection should be tested beforehand via Oracle Client Tools like Net Manager or SQL*Plus before trying to connect via Profitbase Studio.
The user may set up a linked server or SSIS connection pointing to either a connection defined in the tsnnames.ora file (can also be administered via Net Manager) or a direct connection string in the format of: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=NN.IP.NN.NNN)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=NNNSIDNNN)))
Note!
When connecting via Oracle SSIS through an app server you in some cases may have to set two SSIS Settings; DefaultCodePage (default set to 1252) and set AlwaysUseDefaultCodePage = True otherwise you might encounter error messages concerning LocaleID or Code Page.
Also note!
When connecting via Linked Server OLEDB Provider option "Allow inprocess" needs to be checked.