Forum Discussion
martin_larsson_ellevio
May 22, 2025Copper Contributor
Oracle 2.0 property authenticationType is not specified
I just published upgrade to Oracle 2.0 connector (linked service) and all my pipelines ran OK in dev. This morning I woke up to lots of red pipelines that ran during the night. I get the following error message:
ErrorCode=OracleConnectionOpenError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=
Failed to open the Oracle database connection.,Source=Microsoft.DataTransfer.Connectors.OracleV2Core,''Type=System.ArgumentException,
Message=The required property is not specified.
Parameter name: authenticationType,Source=Microsoft.Azure.Data.Governance.Plugins.Core,'
Here is the code for my Oracle linked service:
{
"name": "Oracle",
"properties": {
"parameters": {
"host": {
"type": "string"
},
"port": {
"type": "string",
"defaultValue": "1521"
},
"service_name": {
"type": "string"
},
"username": {
"type": "string"
},
"password_secret_name": {
"type": "string"
}
},
"annotations": [],
"type": "Oracle",
"version": "2.0",
"typeProperties": {
"server": "@{linkedService().host}:@{linkedService().port}/@{linkedService().service_name}",
"authenticationType": "Basic",
"username": "@{linkedService().username}",
"password": {
"type": "AzureKeyVaultSecret",
"store": {
"referenceName": "Keyvault",
"type": "LinkedServiceReference"
},
"secretName": {
"value": "@linkedService().password_secret_name",
"type": "Expression"
}
},
"supportV1DataTypes": true
},
"connectVia": {
"referenceName": "leap-prod-onprem-ir-001",
"type": "IntegrationRuntimeReference"
}
}
}
As you can see "authenticationType" is defined but my guess is that the publish and deployment step somehow drops that property. We are using "modern" deployment in Azure devops pipelines using Node.js.
Would appreciate some help with this!
Now the issue is resolved by Microsoft. They released a fix for this on may 27 and I just tested it and it works for us. We are in West Europe and all Europe regions has gotten the fix according to the MS technician I talked to.
5 Replies
Sort By
- MohammedBMCopper Contributor
We are running into the same issue. This needs to get a higher priority from Microsoft. Why are they not helping?
- Lieke_SeatownCopper Contributor
Hi Martin, did you already find a solution to the problem? I am experiencing the exact same thing. My solution has been to add the AuthenticationType directly to the workspace publish brance in the TemplateForWorkspace JSON. This currently seems to solve the problem.
- martin_larsson_ellevioCopper Contributor
No but I have a ticket at Microsoft and the information I have gotten so far is that there is a bug in the Oracle 2.0 linked service. I will have a meeting with them later today and I can brief you after that.
- martin_larsson_ellevioCopper Contributor
In our ADF prod instance I can see the above json code for the Oracle linked service when in "GIT mode" but when I switch to live mode the line with
"authenticationType": "Basic"
is gone.
- martin_larsson_ellevioCopper Contributor
Now the issue is resolved by Microsoft. They released a fix for this on may 27 and I just tested it and it works for us. We are in West Europe and all Europe regions has gotten the fix according to the MS technician I talked to.