OAC REST API Dataset – intermittent refresh failures with “nQSError: 47123 Invalid connection detail

Question

We are experiencing an intermittent refresh issue with an Oracle Analytics Cloud dataset that uses a REST API (Preview) connection.

The dataset is used in a workbook join to apply user visibility/security filtering. It retrieves two fields from a Fusion REST endpoint:

* UserName
* SecurityContextValue

The refresh behavior is alternating:

* some executions complete successfully;
* other executions fail a few minutes later, without any configuration change;
* the history currently shows 92 successful full refreshes and 22 failed refreshes.

The dataset is configured with Automatic Caching and replaces the existing data on each full refresh.

A successful refresh reads 9 rows and completes normally. The OAC Diagnostic Log shows the following sequence:

Data Refresh Service
-> logical query against the XSA dataset object
-> BI Server queue time: 0.006 seconds
-> physical query sent through the REST connector:
   select "USERNAME", "SECURITYCONTEXTVALUE" from AUTOREST.ITEMS
-> Query Status: Successful Completion

The physical query completes in approximately 0.82 seconds after it is sent to AUTOREST.ITEMS.

For a failed refresh, the Diagnostic Log shows:

Dataset reload job started
-> logical query created by Data Refresh Service
-> BI Server queue time: 0.003 seconds
-> [nQSError: 47123] Invalid connection details were supplied.
   Please enter the correct details and try again.
-> [nQSError: 43119] Query Failed
-> Dataset reload task ended with status: Failed

In the failing case, the log does not show the subsequent physical-query step:

Sending query to database ... from AUTOREST.ITEMS

Therefore, the failure appears to occur after OAC resolves the logical dataset query, but before the physical query is dispatched through the REST connector.

The REST connection uses Basic Authentication with a Fusion SaaS technical account. The connection configuration, endpoint, and credentials have not been changed between successful and failed executions.

Could anyone advise on:

* What conditions can cause intermittent nQSError: 47123 Invalid connection details were supplied for an OAC REST API dataset?
* Does this error indicate a connection/credential resolution issue within OAC, or can it also be returned when the remote Fusion endpoint rejects a request?
* Are there known limitations involving connection pooling, credential rotation, throttling, concurrency, or REST API usage limits that could cause this alternating behavior?
* Which additional OAC diagnostic logs or settings would help capture the underlying HTTP status or connector error?

BrandonH · Answer

* / 2. I dont think you can trust the error text. It would be good if you could get a more detailed error message through a trace.

We've seen that connections get bounced to cloud data sources including fusion, due to "DDOS" type protection. I think you will be at risk of this type of problem with how you are planning to use the connection as a dynamic refresh from a workbook.

I dont think it will be stable to have a live Fusion rest endpoint used as a security dimension source for a workbook. Even using a dataflow to a scheduled refresh dataset may be better.

User795811-Oracle · Answer

Hi Bredan,

I checked the dataset and confirmed that there are currently no schedules configured for it. Therefore, there are no scheduled refresh jobs directly associated with this dataset.

We are still completing the wider impact analysis to identify any other datasets, data flows, or manual processes that might use the same REST endpoint or the same Fusion technical account concurrently.

In parallel, we created a new REST connection and a new test dataset using the same REST endpoint configuration. The behavior was reproduced as follows:

* initial attempt to create the AUTOREST.ITEMS dataset table failed;
* dataset profiling failed with error code 47123;
* without changing the endpoint or dataset definition, a subsequent profiling attempt succeeded and returned 9 rows.

The original dataset also shows historical successful and failed refreshes. The OAC diagnostic logs for failed executions show that the failure occurs while initializing the reader, before any rows are read. In a previously captured failed refresh, BI Server Log reported nQSError 47123 - Invalid connection details were supplied.

This seems to indicate an intermittent condition during REST connection initialization rather than a data-volume, dataset join, or cache issue. We are correlating the failed and successful timestamps with OCI diagnostic logs and checking for any concurrent usage of the REST endpoint.

Please let us know whether there are additional diagnostics or known limitations for REST API (Preview) connections that could help identify the underlying cause of intermittent error 47123.

Brendan T · Answer

Are there other notebooks sharing the same REST connection or if multiple scheduled refresh jobs reference it concurrently?  If so, then you might have intermittent fails.