You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -60,7 +63,7 @@ Below are the environment variables the image understands.
60
63
| AUTH_KEY | No (Required) | The [ADF authentication key](https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime?tabs=data-factory#create-a-self-hosted-ir-via-ui)|
61
64
| NODE_NAME |`container hostname`| The name of the node that will be displayed in ADF. |
62
65
| OFFLINE_NODE_AUTO_DELETION_TIME_IN_SECONDS |`601` (10 minutes) | The number of seconds that a node has to be offline to be automatically cleaned up from ADF. (it has to be the same for all nodes in the same runtime) |
63
-
| ENABLE_HA |`false`| If you are planning to use multiple containers (nodes) in a single runtime, pleasae set this to true. |
66
+
| ENABLE_HA |`false`| If you are planning to use multiple containers (nodes) in a single runtime, please set this to true. |
64
67
| HA_PORT |`8060`| The HA port used for communication between the nodes. |
65
68
66
69
## Usage
@@ -150,6 +153,19 @@ Also, if you are to have more than one node, you need to set ENABLE_HA to `true`
150
153
151
154
You most likely have 4 registered nodes with the current runtime. Azure Data Factory supports only 4 registered nodes per integration runtime.
152
155
156
+
### Error SQLSTATE IM004, SQLAllocHandle on SQL_HANDLE_ENV
157
+
158
+
Applies to: IBM DB2 ODBC Driver Only
159
+
160
+
The error is generated whenever the docker image is executed with [isolation mode](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container) set to `hyperv` and not `process`.
161
+
This typically occurs on Windows Desktop OS as that defaults to isolated: hyperv mode and Windows Server OS defaults to isolated: process mode.
162
+
163
+
#### Solution
164
+
165
+
If you are going to be using IBM DB2 ODBC Driver, it is highly suggested to run the image inside Windows Server 2019 or above. [Isolation mode](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/hyperv-container) should be set to `process`.
166
+
167
+
168
+
153
169
## Thanks
154
170
155
171
This repository was heavily inspired by what was already done [here](https://github.com/Azure/Azure-Data-Factory-Integration-Runtime-in-Windows-Container) by [@wxygeek](https://github.com/wxygeek)
Each additional driver to be installed has to be created according to the directory structure and installation mechanism.
6
+
7
+
## Directory Structure
8
+
9
+
`<vendor>`/[`vendor sub-type`]/`<driver type>`
10
+
11
+
Examples:
12
+
13
+
*`ibm`/`db2`/`odbc`
14
+
*`mariadb`/`odbc`
15
+
*`postgresql`/`pgsql`
16
+
17
+
18
+
## Install Script
19
+
20
+
Each driver directory has an `install.ps1` script plus (if needed) additional files required for the installation. The `install.ps1` script will be called by the `install-drivers.ps1` script inside the `scripts` directory.
21
+
22
+
Please make sure to add all necessary steps to automate the installation of the additional driver inside the `install.ps1` script. It is also
23
+
recommended to have clean-up steps to remove setup files, zip files etc. That would help to keep the image small.
0 commit comments