Running SQL Scripts with Unicode Characters on an Oracle Database Server
InstallShield 2020
Project:This information applies to the following project types:
| • | Basic MSI |
| • | DIM |
| • | InstallScript |
| • | InstallScript MSI |
For installations that use the default SQL script support that is available in the SQL Scripts view of InstallShield, Microsoft ODBC for Oracle is used to connect to an Oracle database server on a target system. In some cases, you may want to override the default behavior, and use the Oracle ODBC Instant Client instead of Microsoft ODBC for Oracle.
For example, if your SQL script contains Unicode characters, you may want to use the Oracle ODBC Instant Client, since it has support for running SQL scripts that contain Unicode characters, but Microsoft ODBC for Oracle does not.
To configure your InstallShield project so that your installation uses the Oracle ODBC Instant Client instead of Microsoft ODBC for Oracle:
| 1. | In the View List under Additional Tools, click Direct Editor. |
| 2. | In the Tables explorer, click the ISSQLDBMetaData table. |
| 3. | Perform the following steps for the Oracle record: |
| a. | Change the AdoDriverName field to the following value: |
{Oracle in instantclient11_1}
| b. | Change the AdoCxnServer field to the following value: |
DBQ=
At run time, the installation uses the Oracle ODBC Instant Client for connecting to the Oracle database and running SQL scripts.
Tip:The Oracle ODBC Instant Client is available on a target system if the ODBC package of the Oracle Instant Client software is installed. To learn how to add it to your installation, see Downloading the Oracle Basic Instant Client and the Oracle ODBC Instant Client and Creating an .msi Package and InstallShield Prerequisite for Both.