OAC - when running reports showing ". [nQSError: 17014] Could not connect to Oracle database.

Sambasivarao Manam

We could able to connect ADW DB , create connection from OAC Console ,create ADW DB from SQL Developer but after deploying RPD and running reports getting Error as Could not connect to Oracle database.

Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)
State: HY000. Code: 43275. [nQSError: 43275] Message returned from OBIS [ecid:19e055fa-7ccf-41a2-9ae2-981596dc8a2d-00071024,0:1:15:6 ts:2024-05-04T02:22:41.225+00:00]. (HY000)
State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)
State: HY000. Code: 17001. [nQSError: 17001] Oracle Error code: 12529, message: ORA-12529: TNS:connect request rejected based on current filtering rules at OCI call OCIServerAttach. (HY000)
State: HY000. Code: 17014. [nQSError: 17014] Could not connect to Oracle database. (HY000)

Can someone pls provide insights what could be the issue.

Sumanth V -Oracle

@KhaderBelgoud-Oracle - Reuploading the ADW wallet again resolved this issue.

Sumanth V -Oracle

@Sambasivarao Manam - Please validate the ACL entries of your ADW, as suggested in below document.

Connection to ADW or Autonomous Transaction Processing(ATP) Database from Oracle Analytics Cloud(OAC) Fails With " Listener refused the connection with the following error: ORA-12529, TNS: connect request rejected based on current filtering rules" Error (Doc ID 2669439.1)

RanaAshutosh-Oracle

This issue may also occur if TNS entry defined (via successful data connection) in console is not recognized by rpd connection pool. Offline rpd changes with direct tns entry definition at rpd connection pool and setting externalize connection to 'FALSE' at connection pool can resolve the issue in that case :

TNS format - (description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=*******.oraclecloud.com))(connect_data=(service_name=**********.oraclecloud.com))(security=(ssl_server_cert_dn="CN=*****.oraclecloud.com,OU=Oracle ADB INDIA,O=Oracle Corporation,L=Redwood City,ST=California,C=US")))
 

Sambasivarao Manam

Connection pool.PNG

Hi RanaAshtosh, Thanks for your response. I verified connection and  externalize connection already set to 'FALSE' at connection pool and verified TNS entry and did not see any difference.

Sambasivarao Manam

Hi Sumanth , I am able to connect ADW from OAC and see database tables via

Console →DATA

Console → Connection

as soon as deployed RPD with same ADW DB could not able to run the reports with Errors

Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65PState: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)State: HY000. Code: 43275. [nQSError: 43275] Message returned from OBIS [ecid:19e055fa-7ccf-41a2-9ae2-981596dc8a2d-00075b38,0:1:23:6 ts:2024-05-04T11:36:37.271+00:00]. (HY000)State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)State: HY000. Code: 17001. [nQSError: 17001] Oracle Error code: 12529, message: ORA-12529: TNS:connect request rejected based on current filtering rules at OCI call OCIServerAttach. (HY000)State: HY000. Code: 17014. [nQSError: 17014] Could not connect to Oracle database. (HY000)

Sumanth V -Oracle

@Sambasivarao Manam - In that case issue seems to be with connection string used as DSN in RPD. To verify the same, please try using a connection created in DV or Console as externalise connection in RPD and deploy it and verify if you are able to create analysis without the error. Thanks.

Sambasivarao Manam

Hi, Thanks for your time. it is started working after re-upload Wallet file in console connection /data . am not sure what could be the reason for not working earlier. I tried multiple times and succeeded finally .

Sumanth V -Oracle

@Sambasivarao Manam - Thanks for sharing. But it's kind of strange as you mentioned connection created under Console- Data was also working. Good to know it's working now.

KhaderBelgoud-Oracle

The error message "connect request rejected based on current filtering rules" indicates that the ingress/egress rules on the ADW DB subnet need to be verified.

Namrata Bhan-Oracle

@Sambasivarao Manam We noticed you have at least one answer to your question. Please accept the answer that helped you resolve the issue. Thanks