Oracle Communities

Oracle Analytics and AI

Child Item

Bug with the developer option in OAS 2025 DV

Hello everyone,

We recently upgraded to Oracle Analytics Server (OAS) 2025 and are encountering an issue specifically within the Data Visualization (DV) module. When we enable Developer Mode and click the “Refresh” button, the DV screen enters an infinite loop of authentication pop-ups requiring repeated credentials. Eventually, it becomes unusable unless we force‑quit the browser or application.

Has anyone else encountered this behavior in OAS 2025 DV? Any insights—workarounds, configs, or patches—would be greatly appreciated.

Thanks in advance!

Recording-20250812_170405.mp4

Find more posts tagged with

OAS 2025

Accepted answers

Qui Thai

Hi Dhaval Parikh Stantec,

Your problem can be solve. Just see the link below.

You can updatet the logconfig.xml file with Format = ODL-TEX,JSON.

But do this only for the UserLog section !

Otherwise it will generate a lot of logfile and your system wil hang.

After you restart the OAS the problem will be solved.

See:

OAS 2025:"Log Could Not Be Retrieved" Error When Clicking View Log in Administration>Manage Sessions — Oracle

`Cause:`

This issue is an internal product defect. In OAS 2025, BI Server logs are generated only in JSON format (obis1-query.json, obis1-diagnostic.json), while the standard log format is missing.

A review of the logconfig.xml file (located at <<Domain Home>>/config/fmwconfig/biconfig/OBIS/) reveals the following:

Element: /server/ServerInstance/Log/FormatOAS 2025: Set to JSON
Element: /server/ServerInstance/UserLog/FormatOAS 2025: Set to JSON

`Solution:`

To resolve this issue:

Update the logconfig.xml file in the OAS 2025 environment by setting Format = ODL-TEXT,JSON.
Restart the OAS 2025 environment.

After this update, both log formats will be generated in <<Domain Home>>/servers/obis1/logs/, and the "View Log" functionality in the UI Console (Sessions and Query Logs) should work correctly without errors.

Hope you can solved the problem,

Qui Thai

All comments

Steve F-2

Hi Dhaval,
There could be an issue with a front-end configuration (HTTP Server, Load Balancer, Proxy) and the managed server configuration.

It would be best if you you capture an HTTP Archive (HAR) with your browser web/developer tools.

SRDC - How To Collect HTTP Archive (HAR) File From Chrome, Microsoft Edge or FireFox Browsers (Doc ID 3035966.1)

Since a HAR file can include sensitive information, you may want to obfuscate or post it in a secure service request along with information about your authentication and architecture. The HAR file may provide some additional insight into the looping.

Leaving this here for anyone else to comment on the behavior itself. I have not encountered it, but it may be due to your architectural layers.

Michal Zima

@Dhaval Parikh Stantec I would agree with @SteveF-Oracle - we are not having on our OAS 2025 instances such issue in Developer mode, you are describing (we are having Apache HTTP server in front of OAS, taking care of OAM integration for SSO).

Gianni Ceresa

What Steve and Michal said: didn't have any issue with it with default authentication.

peacey

we have what sounds like the same issue. We have an SR open.

Steve F-2

I tested again with a two-node horizontal scale-out cluster with an Apache HTTP Server front-end.
It worked fine with accessing each node independently (i.e. - stopping only node2, stopping only node1) via the HTTP Server.

Key points for this test environment:

HTTP only (no HTTPs offloading/termination)
Default authenticator (no SSO, no external LDAP). External LDAP should not matter, but SSO configuration possibly.
Tested with Safari and FireFox browsers.

@Dhaval Parikh Stantec - did you ever come to a conclusion / solution?

@peacey - Opening an SR is the right course of action. Please do provide your architecture/environment/browser details in the SR + HAR file ^^^

Qui Thai

Hi Dhaval Parikh Stantec,

Your problem can be solve. Just see the link below.

You can updatet the logconfig.xml file with Format = ODL-TEX,JSON.

But do this only for the UserLog section !

Otherwise it will generate a lot of logfile and your system wil hang.

After you restart the OAS the problem will be solved.

See:

OAS 2025:"Log Could Not Be Retrieved" Error When Clicking View Log in Administration>Manage Sessions — Oracle

`Cause:`

A review of the logconfig.xml file (located at <<Domain Home>>/config/fmwconfig/biconfig/OBIS/) reveals the following:

Element: /server/ServerInstance/Log/FormatOAS 2025: Set to JSON
Element: /server/ServerInstance/UserLog/FormatOAS 2025: Set to JSON

`Solution:`

To resolve this issue:

Update the logconfig.xml file in the OAS 2025 environment by setting Format = ODL-TEXT,JSON.
Restart the OAS 2025 environment.

Hope you can solved the problem,

Qui Thai

BrandonH

@Qui Thai has the correct solution.

I confirmed that the RESPONSE of the erroring request:

Request URLhttps://someurl.com/dv/ui/api/v1/data/viewLog?cursorID=4912335&resultsType=unformatted

Has in summary these errors:

analytics/res/v-1Y8JXKiIr58/b_mozilla/common.js"></script><div class="ErrorMessage">Error during query processing (SQLExecDirectW)

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058]

Code: 43275. [nQSError: 43275] Message returned from OBIS [ecid:00… … ]

Code: 43261. [nQSError: 43261] Log Viewer process failed to convert the obis1-query.json to obis1-query.log: jq is not installed. Please install jq first before run this script.

I also tested and confirmed that in environments generating only .json obis logs, the problem happens. In environments generating both TEXT,JSON formats of logs the issue does not happen. After changing a problematic environment to logging both formats, the issue no longer occurs.

So the "Authentication Error" popup is just masking the root issue.

I've sent these updates along to Oracle in: SR 3-41987043331

RVohra

Cannot access the SR, appreciate if you can keep us updated here. It will help for other OAC users.