In Azure Data Factory, I'm trying to create a linked service by using the Oracle Service Cloud (Preview) connector to connect to my organisation's Oracle HCM instance. I'm generally following this guidance, using the copy data tool, which should be straightforward: https://learn.microsoft.com/en-us/azure/data-factory/connector-oracle-service-cloud?tabs=data-factory
I have tried the following host names...
https://xxxx.xx.xxx.oraclecloud.com/
https://xxxx.xx.xxx.oraclecloud.com/hcmRestApi
https://xxxx.xx.xxx.oraclecloud.com/hcmRestApi/resources/11.13.18.05/grades
https://xxxx.xx.xxx.oraclecloud.com:443/hcmRestApi/resources/11.13.18.05/grades
... but all of the generate the following error...
Error code 9603
ERROR [HY000] [Microsoft][OSvC] (20) Error while attempting to use REST API: Couldn't resolve host name
ERROR [HY000] [Microsoft][OSvC] (20) Error while attempting to use REST API: Couldn't resolve host name
Activity ID: 590c5007-ec6f-4729-9eb2-d05ef779dc0e.
I'm using a username and password that has been tested on Oracle, and have tried various combinations of using encrypted endpoints, host verification and peer verification as true or false.
I believe I'm using the correct endpoints, based on Oracle's guidance:
Oracle REST endpoints
https://docs.oracle.com/en/cloud/saas/human-resources/22c/farws/rest-endpoints.html
I'm not sure what else to try to get this connector to work? Has anybody else got it to work, or perhaps noticed something I'm doing wrong with the host name?
Related
I have tried to configure an AWS DMS Endpoint, but when I try to do the connection test it shows me the following error:
Test Endpoint failed: Application-Status: 1020912, Application-Message: Log Miner is not supported in Oracle PDB environment Endpoint initialization failed.
I have given all the grants that are required in Oracle DB following the documentation:
https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.Oracle.html
But the error still persists. What could be the solution?
Add this line to extra connection attributes (under endpoint settings)
useLogMinerReader=N;useBfile=Y;
make sure to grant necessary permission to your container user on this link https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.Oracle.html#CHAP_Source.Oracle.Self-Managed.BinaryReaderPrivileges
Good afternoon, I am trying to run an oracle database with docker, but when I try to connect from the sql developer I get the following error:
ORA-28040: No matching authentication protocol
The question is that I am using the parameters that are specified to be necessary to connect to the database, such as the host ip (10.164.7.203) and port 1521:
Try to apply the solution described here:
https://logic.edchen.org/how-to-resolve-ora-28040-no-matching-authentication-protocol/
but I haven't managed to solve the problem either
The container is lifting normally and I have even done operations with sqlplus and everything is fine
the container DON'T use $ORACLE_HOME/network/admin/sqlnet.ora
you must modify in
/app/oracle/product/12.2.0/dbhome_1/admin/ORCLCDB
SQLNET.ALLOWED_LOGON_VERSION=8
We are trying to make a connection from PowerBI Desktop, to the Google Big Query Database. Upon starting the app and immediately after trying to make the connection to the Google Data Source, we get the error below:
Unable to Connect
We encountered an error.
Details: "ODBC: ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST API: Couldn't resolve host name
ERROR [HY000] [Microsoft][DriverOAuthSupport] (8701) Error interacting with REST
API: Couldn't resolve host name"
I suppose that it has something to do with the proxy used inside our corporate environment but i haven't found anything so far on what urls/ports should be opened in order for this connection to work.
Please do keep in mind that this is a new business need and it is not something that worked and stopped working.
I have an error when i try to connect to a web service using apex , it always gives error ORA-12545: Connect failed because target host or object does not exist i cant even connect to google, when i check dba_host_aces i have the permission to resolve and connect. the problem is that i am not sure if i need to do something with the oracle server to allow the apex to run or open ports or something, i have been using this guide oracle-base to make the function that calls the webservice
I'm trying to connect to s4 hana system using s4 sdk. While executing calls via .execute() method in cloud foundry environment, i see below error logs:
Caused by: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: Failed to get authentication headers. Destination service returned error: Missing private and public key for subaccount ******-****-****-***-*******.
Note: I've already configured trust between subaccount and S4Hana system and created respective communication and business user. The associated authentication method used in the destination is oAuth2SamlBearerAssertion. Note: The call executes fine in both local and cloud foundry environment with basic authentication.
Can someone please suggest what is wrong here.
As correctly pointed out by #Dennis H there was a problem in trust configuration between my subaccount and S4 Hana system, the configuration wrong in my case :
-> The certificate I downloaded for trust was using this URL:
https://.authentication.eu10.hana.ondemand.com/saml/metadata
This is incorrect we need to get the certificate from download trust button in destination tab at subaccount level
->Provider name was incorrect in the communication system.
We are developing a side-by-side extension app and deploying it to CF. Our app is trying to connect to S4HANA cloud system using oAUTH2SAMLBEARERASSERTION. But facing issues while doing it. We are getting below error in logs. Please be noted, we are able to connect to S4HANA Cloud using basic auth.
com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: Failed to access the configuration of destination
Our destination parameters look as attached screenshotenter image description here
Thank you.