ADF Related login issue

Question

having a ADF pipeline which is trying to connect with oracle data base while clicking on test connection connectivity us getting successful but while debugging the pipeline its getting failed with below error details:

Operation on target Copy MOC PTW from MyPlant to Adls failed: ErrorCode=OracleConnectionOpenError,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Failed to open the Oracle database connection.,Source=Microsoft.DataTransfer.Connectors.OracleV2Core,''Type=Oracle.ManagedDataAccess.Client.OracleException,Message=ORA-01017: invalid username/password; logon denied https://docs.oracle.com/error-help/db/ora-01017/,Source=Oracle Data Provider for .NET, Managed Driver,'

note: we are using same credentials to connect for same oracle with same Self integrated Run Time database in ADF lower environment pipeline is getting successful connection but getting failed in other ADF pipeline environment.

Answer 1

The error message you're encountering, ORA-01017: invalid username/password; logon denied, indicates that the credentials being used to connect to the Oracle database are incorrect. Since you mentioned that the same credentials work in a lower environment but fail in another Azure Data Factory (ADF) pipeline environment, here are some steps you can take to troubleshoot the issue:

1. Verify Credentials: Double-check the username and password being used in the failing ADF pipeline environment. Ensure there are no typos or extra spaces.
2. Environment Differences: Investigate any differences between the configurations of the working and failing environments. This includes checking the connection strings, authentication methods, and any environment-specific settings.
3. Network Issues: Ensure that the ADF environment has the necessary network access to reach the Oracle database. This may involve checking firewall settings or network security groups.
4. Oracle Database Configuration: Confirm that the Oracle database allows connections from the ADF environment. There may be restrictions based on IP addresses or other security settings.
5. Check for Locked Accounts: Sometimes, accounts can become locked after multiple failed login attempts. Verify with your database administrator if the account is locked or if there are any restrictions on the account.
6. Use of Integrated Runtime: Since you mentioned using a self-hosted integration runtime, ensure that it is properly configured and running. Sometimes, issues with the runtime can lead to connection failures.

If these steps do not resolve the issue, consider reviewing the detailed logs from the ADF pipeline for more insights into the failure.

Answer 2

Hey Upendra, C S (C S) (admin),

It looks like you're facing an Oracle connection issue when debugging your Azure Data Factory (ADF) pipeline. The error message ORA-01017: invalid username/password; logon denied typically indicates a problem with the credentials being used, even though the test connection is successful. Here are a few things you could check to help resolve this:

1. Credential Consistency: Double-check that the username and password are exactly the same in both environments (lower and the problematic ADF pipeline). Even a minor difference can lead to authentication failures.
2. Integration Runtime: Since you mentioned you're using the self-hosted integration runtime, ensure that the setup and configurations for the integration runtime in both environments are identical. If the integration runtime setups differ, it may affect the Oracle connection.
3. Environment-Specific Issues: Sometimes, different environments can have unique configurations. Check if there are any environment-specific settings (like firewalls, network security groups) that could be blocking or affecting the connection to the Oracle database.
4. Role and Permissions: Make sure that your Azure Data Factory has the required roles and permissions to access the Oracle database. Verify that the service principal or managed identity assigned to your ADF has been configured correctly.
5. Logs and Monitoring: Check the logs generated during the pipeline run for any additional error messages or warnings that could provide more context on the connection failure.

If you've checked all these points and are still facing issues, could you provide some additional details? Could you clarify the following things

1. Are you using the same self-hosted integration runtime configuration in both environments?
2. Do you have any firewall rules or network security configurations that might be affecting the connectivity in the problematic environment?

Thanks!

Kalyani