I think mostafa already said above, but are you using any special characters in the schema passwords? If you have any special characters restart from scratch choosing only A-Z 0-9 passwords. In the old days it created problems, its possible it still does. Same goes for any bi admin passwords through the…

@Michal Zima My comment was specific to the OP's post / enhancement request (API for dataflows)

In my testing, when ALREADY authenticated I load a dashboard eg: GET /analytics/saw.dll?Dashboard&portalPath=%2fshared%****%20Home%2fMy%20Dashboard The response headers return with the expected CSP per the OAS configurations (instanceconfig.xml or safedomains) - broken out for readability: Content-Security-Policy:…

Since you dont have an OHS / Apache, do you have the option to offload the SSL to an F5 or something, so header re-write could be done there? If you pre-authenticate to the blocked OAS page so you have an auth token does it behave with the same error? Are you embedding a /analytics page or a /dv page? In my experience that…

I would not support this. The maturity level of Data Flows within DV doesn't seem to be enterprise grade at this time. Utilizing them within and enterprise scheduling system would be a bad architecture choice compared to other products on the market for transforming data eg ODI.

Would appreciate Oracle updating their documentation regarding session timeouts. In days past the "User Session Expirty Time" could be trusted but ever since DV came into the picture things are more complex. In OAS 6.4 and prior there was a hard coded 60 min timeout that was never spoken of:…

 Go directly to, and Index if necessary on start_dt: s_nq_acct example substr replace: SELECT start_dt, REPLACE (SUBSTR (saw_src_path, INSTR (saw_src_path, '/', -1) + 1), '\n') report_name, COUNT (*) total_run, saw_src_path FROM #########.s_nq_acct s WHERE s.start_dt = TO_DATE ('2024-02-13', 'YYYY-MM-DD') GROUP BY…

Your need may be better suited to a more "old school" approach such as bursting: Create a Bursting Job (oracle.com)

The error appears to be literally: com.google.gson.stream.MalformedJsonException: Unterminated object near ":"Note: Click on "Apply" to run the repcom.google.gson.JsonSyntaxException: com.google.gson.stream.MalformedJsonException: Unterminated object near ":"Note: Click on "Apply" At quick glance it looks like you messed…

You need to find what is erroring. Under OAS, go to admin -> manage bi publisher -> Data sources -Use the "test" button on your failing data source. Confirm it still fails. If its still failing go to the weblogic console to investigate the source: http://myserver:port/console Go to: Services -> Data Source Open the data…