Visual KPI can connect to Oracle using ODBC, OLEDB or OLAP. A great resource for setting up the connection and security can be found on the Oracle area of the ConnectionStrings website:
Both Oracle and Microsoft provide 32- and 64-bit drivers for connecting to the database. Visual KPI supports all known drivers from both. Make sure to match your selected driver "bitness" to the operating system "bitness" because the Oracle drivers do not support "cross-architecture" calls from within IIS application pools. While Visual KPI has always supported callling 32-bit drivers while running in native 64-bit mode, we depend on the driver author to support this type of down-level support, and with the Oracle drivers we often see "operation resulted in arithmetic overflow" when trying to cross the 32/64 bit boundary. It is safer, easier and less time consuming to simply match the driver architecture to the server architecture. Save yourself some headaches and find the right driver first!
Oracle databases must be treated carefully, since connecting to them successfully involves paying close attention to the client and server versions, connection types and security requirements.
It is essential that you establish and test connectivity using SQL+ or another client running on the Visual KPI Server machine prior to creating the Visual KPI Interface to the database. If errors are encountered, be sure to search the online Oracle User forums to see if it is a known issue with the release combination you are using. A good place to start is the Oracle Windows and .NET forum:
Once you have created a working connection outside of Visual KPI, you are ready to create an interface which uses this connection information. Visual KPI supports both DSN-based interfaces and direct connections using your selected connection string. Here is an example for a 64-bit OLEDB connection on a 64-bit Windows Server 2008 R2 without a DSN. Take the defaults in any screen not shown below:
Modify the OLEDB Provider string to point to your Data Source name with your security credentials. When the Query dialog boxes are shown, simply click next to create the interface without modifying the default Query examples for Current Value, Historical Value and Trend Value. You can modify all of these later after verifying the interface connectivity. See the XXXX FAQ entry for tips on creating correctly parameterized Interface Queries for any data source.
Last updated on March 19, 2013 by Transpara