upgrade the Amazon RDS for Oracle connector v2 is not working

Question

upgrade the Amazon RDS for Oracle connector v2 is not working

Ashok Sharma 0

I am trying to upgrade existing linked service for Amazon RDS for Oracle to v2. When I try to publish the linked service, below properties are empty. Can someone help me on this?

I am using below json template for the linked service.

{

"name": "AmazonRdsForOracleLinkedService", 

"properties": { 

    "type": "AmazonRdsForOracle", 

    "version": "2.0", 

    "typeProperties": { 

        "server": "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST= amazonrdsfororaclesample.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=db1)))",  

        "username": "<user name>",  

        "password": "<password>",  

        "authenticationType": "<authentication type>" 

    }, 

    "connectVia": { 

        "referenceName": "<slefhosted Integration Runtime>", 

        "type": "IntegrationRuntimeReference" 

    } 

}

}

User's image

Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-19T07:39:43.75+00:00
Hi @Ashok Sharma
Thanks for sharing the details.

Based on your screenshot and JSON template, the issue appears to be caused by placeholders not being properly resolved or populated during deployment. Specifically, the fields for server, username, and authenticationType are showing up empty in the UI when publishing the v2 Amazon RDS for Oracle linked service.

Key Points to Check:

Ensure JSON Values Are Set In your JSON, the following fields are defined as placeholders:
"server": "(DESCRIPTION=...)", "username": "<user name>", "password": "<password>", "authenticationType": "<authentication type>"
These must be replaced with actual values before publishing. For example:
"server": "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=amazonrdsfororaclesample.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=db1)))", "username": "your_db_user", "password": { "type": "SecureString", "value": "your_password" }, "authenticationType": "Basic"

Use Valid Authentication Type The only supported value for authenticationType currently is:
"authenticationType": "Basic"

Integration Runtime If you’re using a Self-hosted Integration Runtime, ensure:

It is correctly registered.

The name used in "referenceName" matches exactly what's configured in ADF.

Double-Check for JSON Errors A missing or incorrectly formatted property (like password) can cause the UI to render blank fields.

Next steps:

Replace placeholders in the JSON with actual values.

Redeploy the linked service.

If fields are still missing in the UI after publishing, try recreating the linked service through the ADF UI first, then exporting the working JSON for future reuse.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Ashok Sharma 0

I created linked service using ADF UI, which works fine. However, when I export the published version and try to deploy it using CI/CD pipeline or using power shell cmd, it is not publishing correctly. Three Properties ("Server", "Authentication Type" and "User Name") are published as empty.

I even tried to publish it as a new linked service. That is not working either.

The json I posted in the description, is a sample json only.

The Json, I am publishing

{

"name": "LS_TESTRDS",

"type": "Microsoft.DataFactory/factories/linkedservices",

"properties": {

    "description": "amazon rds ",

    "annotations": [],

    "type": "AmazonRdsForOracle",

    "version": "2.0",

    "typeProperties": {

        "server": "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=testservice)))",

        "authenticationType": "Basic",

        "username": "UserName",

        "password": {

            "type": "AzureKeyVaultSecret",

            "store": {

                "referenceName": "LS_KeyVault",

                "type": "LinkedServiceReference"

            },

            "secretName": "testsecret"

        }

    },

    "connectVia": {

        "referenceName": "SelfHostedIR",

        "type": "IntegrationRuntimeReference"

    }

}

}

Published version

{

"name": "LS_TESTRDS",

"type": "Microsoft.DataFactory/factories/linkedservices",

"properties": {

    "type": "AmazonRdsForOracle",

    "typeProperties": {

        "password": {

            "type": "AzureKeyVaultSecret",

            "store": {

                "referenceName": "LS_KeyVault",

                "type": "LinkedServiceReference"

            },

            "secretName": "testsecret"

        }

    },

    "version": "2.0",

    "connectVia": {

        "referenceName": "SelfHostedIR",

        "type": "IntegrationRuntimeReference"

    },

    "description": "amazon rds ",

    "annotations": []

}

}

Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-23T02:24:05.07+00:00
@Ashok Sharma Thanks for confirming that the linked service works fine when created via the ADF UI, but fails during deployment via CI/CD or PowerShell.

When using ARM templates or PowerShell, some connector properties (like server, username, and authenticationType) may not persist unless explicitly declared under the typeProperties section with exact casing and structure, especially for Amazon RDS for Oracle v2.

Troubleshooting steps:

Ensure All Required Fields Are Explicitly Declared Sometimes, even if optional in UI, these must be explicitly included in your ARM template or script. Example of corrected structure:
"typeProperties": { "server": "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=testservice)))", "authenticationType": "Basic", "username": "UserName", "password": { "type": "AzureKeyVaultSecret", "store": { "referenceName": "LS_KeyVault", "type": "LinkedServiceReference" }, "secretName": "testsecret" } }

Add "parameters" Block if Using ARM Template Parameterization If deploying through CI/CD using parameterized templates (e.g., arm-template-parameters-definition.json), ensure these fields are not accidentally removed or left null due to the parameter file structure.

Check ADF ARM Schema Compatibility Make sure you’re using the latest ARM schema version in your template to fully support v2 connectors:
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#"

Manual Publish Test via ARM Template As a test, try deploying the same template directly using the Azure Portal’s "Deploy a custom template" blade. If the fields still appear empty, it confirms an ARM template issue (not a runtime bug).

Known Workaround:

This is a known behavior occasionally observed with newer connector versions where Linked Service definitions work via UI but break in ARM-based deployments.

As a workaround:

Export from ADF UI as ARM Template, not via “Manage Hub > Export” but through Resource Group > Automation Script in Azure Portal.

Compare this with your deployment template for field mismatch.

I hope this information helps. Please do let us know if you have any further queries.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-24T09:31:41.22+00:00

@Ashok Sharma We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Ashok Sharma 0 Reputation points

2025-06-24T09:51:22.7866667+00:00
Hi Smaran Thoomu - Thanks for your response.

All required fields are explicitly declared. I am using json file for published version (Code View). Doesn't look like any issue with case sensitivity of the fields

I am not using any parameter json file

I have also tried adding $schema property in the json file

I have not tried deploying the same template directly using the Azure Portal’s "Deploy a custom template" blade. Can you guide me (with some screenshots) how to do it? I am getting challenges doing it.
Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-24T15:58:35.37+00:00

@Ashok Sharma I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.

1 answer

Your answer

Ashok Sharma 0 Reputation points

2025-06-19T12:04:46.2166667+00:00

I created linked service using ADF UI, which works fine. However, when I export the published version and try to deploy it using CI/CD pipeline or using power shell cmd, it is not publishing correctly. Three Properties ("Server", "Authentication Type" and "User Name") are published as empty.

I even tried to publish it as a new linked service. That is not working either.

The json I posted in the description, is a sample json only.

The Json, I am publishing

{

"name": "LS_TESTRDS", "type": "Microsoft.DataFactory/factories/linkedservices", "properties": { "description": "amazon rds ", "annotations": [], "type": "AmazonRdsForOracle", "version": "2.0", "typeProperties": { "server": "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hostname)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=testservice)))", "authenticationType": "Basic", "username": "UserName", "password": { "type": "AzureKeyVaultSecret", "store": { "referenceName": "LS_KeyVault", "type": "LinkedServiceReference" }, "secretName": "testsecret" } }, "connectVia": { "referenceName": "SelfHostedIR", "type": "IntegrationRuntimeReference" } }

}

Published version

{

"name": "LS_TESTRDS", "type": "Microsoft.DataFactory/factories/linkedservices", "properties": { "type": "AmazonRdsForOracle", "typeProperties": { "password": { "type": "AzureKeyVaultSecret", "store": { "referenceName": "LS_KeyVault", "type": "LinkedServiceReference" }, "secretName": "testsecret" } }, "version": "2.0", "connectVia": { "referenceName": "SelfHostedIR", "type": "IntegrationRuntimeReference" }, "description": "amazon rds ", "annotations": [] }

}
Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-24T09:31:41.22+00:00

@Ashok Sharma We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Ashok Sharma 0 Reputation points

2025-06-24T09:51:22.7866667+00:00

Hi Smaran Thoomu - Thanks for your response.

All required fields are explicitly declared. I am using json file for published version (Code View). Doesn't look like any issue with case sensitivity of the fields

I am not using any parameter json file

I have also tried adding $schema property in the json file

I have not tried deploying the same template directly using the Azure Portal’s "Deploy a custom template" blade. Can you guide me (with some screenshots) how to do it? I am getting challenges doing it.
Smaran Thoomu 24,110 Reputation points Microsoft External Staff Moderator

2025-06-24T15:58:35.37+00:00

@Ashok Sharma I agree that this issue looks strange and I wasn't able to reproduce this issue. If you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.

Answer 1

Alex Burlachenko 9,780

hi Ashok! thanks for posting this,

make sure u picked 'version 2.0' in the dropdown. sometimes the ui glitches and resets it to 1.0. if it still acts up, try deleting the linked service and recreating it from scratch. Check if ur selfhosted integration runtime is updated to the latest version. old runtimes can cause weird issues like this. u can find the update instructions here https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime#update-the-self-hosted-integration-runtime

for any oracle connector, not just azure, always verify the connection string format matches oracle's requirements. worth looking into the authentication type too. if u switched from basic to windows auth, u might need to adjust credentials.

one more thing, sometimes the service just needs a restart. here's how to properly restart the integration runtime https://docs.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime#restart-the-self-hosted-integration-runtime

let us know if this sorts it out,

rgds,

Alex

Ashok Sharma 0 Reputation points

2025-06-19T12:06:41.52+00:00

I created linked service using ADF UI, which works fine. However, when I export the published version and try to deploy it using CI/CD pipeline or using power shell cmd, it is not publishing correctly. Three Properties ("Server", "Authentication Type" and "User Name") are published as empty.

I even tried to publish it as a new linked service. That is not working either.
Ashok Sharma 0 Reputation points

2025-06-19T12:15:18.6066667+00:00

I have updated the self hosted IR to latest version. Also, I using connection string what is shown in oracle documentation.

Thanks!

Share via

upgrade the Amazon RDS for Oracle connector v2 is not working

1 answer

Your answer