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
@@ -121,25 +121,6 @@ More connection properties you can set in linked service per your case:
121
121
| supportV1DataTypes | Specifies whether to use the version 1.0 data type mappings. Do not set this to true unless you want to keep backward compatibility with version 1.0's data type mappings. Type: boolean | No, this property is for backward compatibility use only | false |
122
122
| fetchTswtzAsTimestamp | Specifies whether the driver returns column value with the TIMESTAMP WITH TIME ZONE data type as DateTime or string. This setting is ignored if supportV1DataTypes is not true. Type: boolean | No, this property is for backward compatibility use only | true |
123
123
124
-
#### `server` property configuration
125
-
126
-
For `server` property, you can specify it in one of the following three formats:
|[Oracle Net Services Name (TNS Alias)](https://docs.oracle.com/en/database/oracle/oracle-database/23/netrf/local-naming-parameters-in-tns-ora-file.html#GUID-12C94B15-2CE1-4B98-9D0C-8226A9DDF4CB) (only for the self-hosted integration runtime)|sales|
133
-
134
-
For the parameters used in `server`, we provide an allowlist to avoid security risks, as shown below. You can refer to it to determine which parameters to be set. If the disallowed parameter is set, the connection will fail.
135
-
136
-
- Allowlist for using the Azure integration runtime:
|[Oracle Net Services Name (TNS Alias)](https://docs.oracle.com/en/database/oracle/oracle-database/23/netrf/local-naming-parameters-in-tns-ora-file.html#GUID-12C94B15-2CE1-4B98-9D0C-8226A9DDF4CB) (only for the self-hosted integration runtime)|sales|
184
+
185
+
For the parameters used in `server`, we provide an allow list to avoid security risks, as shown below. You can refer to it to determine which parameters to be set. If you use parameters that are not in the allow list, your connection will fail.
186
+
187
+
- The allow list for using the Azure integration runtime:
The Oracle linked service supports the following properties when apply version 1.0:
@@ -519,12 +521,154 @@ When you copy data from and to Oracle, the following interim data type mappings
519
521
520
522
To learn details about the properties, check [Lookup activity](control-flow-lookup-activity.md).
521
523
522
-
## Upgrade the Oracle connector
524
+
## Upgrade the Oracle connector
523
525
524
-
Here are steps that help you upgrade the Oracle connector:
526
+
Here are steps that help you upgrade the Oracle connector:
525
527
526
-
1. In **Edit linked service** page, select **2.0 (Preview)** under **Version** and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
527
-
1. The data type mapping for the Oracle linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Oracle](#data-type-mapping-for-oracle).
528
+
1. In **Edit linked service** page, select **2.0 (Preview)** under **Version** and configure the linked service by referring to [Linked service properties version 2.0](#version-20).
528
529
529
-
## Related content
530
-
For a list of data stores supported as sources and sinks by the copy activity, see [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats).
530
+
For the authentication related properties including username and password, simply specify the original values in the corresponding fields in version 2.0. For other connection properties in version 1.0 including host, port and Oracle Service Name/Oracle SID, they all become parts of the [server property in version 2.0](#server-property-configuration).
531
+
532
+
For example, if you configure the version 1.0 linked service as shown below:
533
+
534
+
:::image type="content" source="media/connector-oracle/version-1-linked-service.png" alt-text="Screenshot of version 1.0 linked service.":::
The identical version 2.0 linked service configuration using **Easy Connect (Plus) Naming** is:
553
+
554
+
:::image type="content" source="media/connector-oracle/easy-connect-naming-linked-service.png" alt-text="Screenshot of linked service using easy connector (Plus) naming":::
555
+
556
+
```json
557
+
{
558
+
"name": "OracleLinkedService",
559
+
"properties": {
560
+
"type": "Oracle",
561
+
"version": "2.0",
562
+
"typeProperties": {
563
+
"server": "oraclesample.com:1521/db1",
564
+
"username": "<user name>",
565
+
"password": "<password>",
566
+
"authenticationType": "<authentication type>"
567
+
},
568
+
"connectVia": {
569
+
"referenceName": "<name of Integration Runtime>",
570
+
"type": "IntegrationRuntimeReference"
571
+
}
572
+
}
573
+
}
574
+
```
575
+
576
+
The identical version 2.0 linked service configuration using **Connector Descriptor** is:
577
+
578
+
:::image type="content" source="media/connector-oracle/connector-descriptor-linked-service.png" alt-text="Screenshot of linked service using connector descriptor.":::
> Azure Key Vault is supported for the `server` property. You can edit the linked service JSON to add the Azure Key Vault reference, as shown below:
602
+
> :::image type="content" source="media/connector-oracle/azure-key-vault-server.png" alt-text="Screenshot of using Azure Key Vault in server.":::
603
+
604
+
Note that:
605
+
606
+
- If you use **Oracle Service Name** in version 1.0, you can use **Easy Connect (Plus) Naming** or **Connector Descriptor** as the server format in version 2.0.
607
+
608
+
- If you use **Oracle SID** in version 1.0, you need to use **Connector Descriptor** as the server format in version 2.0.
609
+
610
+
- For some additional connection properties in version 1.0, we provide alternative properties/server parameters in version 2.0. You can refer to the table below to upgrade the version 1.0 properties.
611
+
612
+
| Version 1.0 | Version 2.0 |
613
+
|:--- |:--- |
614
+
| encryptionmethod| PROTOCOL (server parameter) |
615
+
| tnsnamesfile | TNS_ADMIN (environment variable supported on the self-hosted integration runtime) |
2. The data type mapping for the Oracle linked service version 2.0 is different from that for the version 1.0. To learn the latest data type mapping, see [Data type mapping for Oracle](#data-type-mapping-for-oracle).
663
+
664
+
An additional connection property `supportV1DataTypes` in version 2.0 can reduce upgrade difficulties caused by data type changes. Setting this property to `true` ensures that the data type in version 2.0 remains consistent with version 1.0.
665
+
666
+
## Differences between Oracle version 2.0 and version 1.0
667
+
668
+
The Oracle connector version 2.0 offers new functionalities and is compatible with most features of version 1.0. The table below shows the feature differences between version 2.0 and version 1.0.
669
+
670
+
| Version 2.0 | Version 1.0 |
671
+
|:--- |:--- |
672
+
|The following mappings are used from Oracle data types to interim data types used by the service internally. <br><br>NUMBER(p,s) -> Single, Double or Decimal based on its precision and scale <br>FLOAT(p)-> Double or Decimal based on its precision <br>NUMBER -> Decimal <br>TIMESTAMP WITH TIME ZONE -> DateTimeOffset <br>INTERVAL YEAR TO MONTH -> Int64 <br>INTERVAL DAY TO SECOND -> TimeSpan |The following mappings are used from Oracle data types to interim data types used by the service internally. <br><br>NUMBER(p,s) -> Decimal or String based on its precision <br>FLOAT(p)-> Double <br>NUMBER -> Double <br>TIMESTAMP WITH TIME ZONE -> DateTime <br>INTERVAL YEAR TO MONTH -> String <br>INTERVAL DAY TO SECOND -> String |
673
+
| convertDecimalToInteger in copy source is not supported. | Support convertDecimalToInteger in copy source. |
674
+
| Using `?` as a placeholder for script activity query parameters is not support. You can use the named parameter (such as `:paramA`) or the positional parameter (such as `:1`) as a replacement. | Support using `?` as a placeholder for script activity query parameters. |
0 commit comments