Reportizer Documentation
Contents Index

Opening Oracle Databases

In Reportizer Opening Data Source dialog, there are several ways to open Oracle databases:

1. Opening through FD interface. Select FD interface, click Oracle, then fill all needed database parameters. Consult with your database administrator on how to choose correct parameters.

Example of configuring a database connection:

(colored are required parameters)

Vendor homepathC:\app\product\12.1.0\client_1
OS authenticationNo
Authentication modeNormal
Application nameReportizer
User namedexter
SQL command separator<sqlplus>

2. Opening through ODBC DSN. Select ADO or BDE interface, then choose ODBC data source option and then select the needed ODBC DSN from the drop-down list. But first, you should create an ODBC DSN of the corresponding type using Windows administrative tools, and point it to the database.

3. Opening through BDE alias. Select BDE interface, then choose Alias option and then select the needed alias from the drop-down list. But first, you should create the alias of type ORACLE using BDE Administrator tool and point it to the database.

4. Opening through connection string. Select ADO interface, then choose Connection string option and write a connection string. This way is very flexible and allows to specify many additional parameters in the connection string and override standard Reportizer connection behavior. It is recommended for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):

Provider=msdaora;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;   (Microsoft OLE DB Provider for Oracle must be installed)

Provider=OraOLEDB.Oracle;Data Source=MyOracleDB;User Id=myUsername;Password=myPassword;   (Oracle Provider for OLE DB must be installed)

Driver={Microsoft ODBC Driver for Oracle};;Uid=myUsername;Pwd=myPassword;   (Microsoft ODBC Driver for Oracle must be installed)

Provider=MSDASQL.1;Extended Properties="DSN=ORACLE_DB;UID=MyUsername;PWD=MyPassword"

Oracle client must be installed. The bit-version of it (32 or 64) must match the bit-version of the application.
When choosing the ODBC option, please make sure the corresponding ODBC driver installed and the bit-version of it matches the bit-version of the application (32 or 64).

See also

 Examples of ADO Connection Strings