Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 34 Oracle Analytics and AI Sharing Center
- 20 Oracle Analytics and AI Lounge
- 273 Oracle Analytics and AI News
- 48 Oracle Analytics and AI Videos
- 16.2K Oracle Analytics and AI Forums
- 6.3K Oracle Analytics and AI Idea Labs
- Oracle Analytics and AI User Groups
- 100 Oracle Analytics and AI Trainings
- 16 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
How purge OAC Cache programmatically.
OAC version November 2025
OAC is private instance.
We followed 2956513.1-BIJDBC_JWTASSERTION-BI-JDBC_Using_JWTAssertion_Steps.pdf
BI-JDBC utility is installed on VM within Organization network and not in OCI.
bijdbc.properties are updated as per the doc.
when "purgeoaccache.sh" is executed it is unable to be connect to IDCS
We did raise a SR and as per Oracle team the BIJDBC utility is not tested with proxy server and purgecache.jar was developed for a customer only and not for GA.
Is there a alternative to clear/purge OAC cache programmatically.
Thanks.
Raju
Answers
-
Welcome to the Oracle Analytics Community!
If you have not already come across, please take a look into the following blog which might be useful.
Hope this help.
Thank you.
0 -
try
DELETE https://<your-oac-host>/api/tcm/v1/dbcache.or you can execute this from your VM using a standard cURL command.
curl -i -X DELETE -H "X-ID-TENANT-NAME: <your-tenant-id>" -u <user>:<password> https://<your-oac-host>/api/tcm/v1/dbcache0 -
To Add
How To Programmatically Clear Cache in Oracle Analytics Cloud(OAC) using JDBC [Video Content] (KB59916)
https://blogs.oracle.com/analytics/improve-oac-cache-management-with-python
You have to be able to reach the instance, so you need from where the call is being initiated (VCN, VPN/FastConnect, etc.)1 -
Thanks SteveF , We followed KB59916 but as per Oracle the solution hasn't been tested when using proxy server.
0 -
Hi Brendan,
curl -v -x <private_proxy_host:portnumber> -i -X DELETE -H "X-ID-TENANT-NAME:idcs-<>.oraclecloud.com" -u "<user_name>:<password>" https://<oac host>/api/tcm/v1/dbcache- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- TLSv1.3 (IN), TLS handshake, [no content] (0):
- TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
- TLSv1.3 (IN), TLS app data, [no content] (0):
< HTTP/1.1 401 Unauthorized
HTTP/1.1 401 Unauthorized
< Date: Sat, 24 Jan 2026 04:20:30 GMT
Date: Sat, 24 Jan 2026 04:20:30 GMT
< Content-Type: text/html
Content-Type: text/html
< Content-Length: 144
Content-Length: 144
< Connection: keep-alive
Connection: keep-alive - Authentication problem. Ignoring this.
< www-authenticate: Basic realm=""
www-authenticate: Basic realm=""
< vary: origin
vary: origin
0 -
@Raju Punith-60121 , Welcome to the Oracle Analytics Community! Thank for your question.
I am not sure if it is possible programmatically, but we can always enable or disable Query Caching.
In Oracle Analytics Cloud, the query cache is enabled by default. You can enable or disable query caching on the Advanced System Settings page.
- Click Console.
- Click Advanced System Settings.
- Click Performance and Compatibility .
- Set Cache Enable on or off.
- On — Data query caching is enabled.
- Off — Caching is disabled.
- Click Apply. Wait a few moments for the changes to refresh through the system.
Hope it helps!
0 -
Thanks R Vohra, it is enabled but we want to purge the cache after daily ETL is complete. Thanks
0 -
Thanks
Thanks Bhaskar , have gone thru link but the option of dbcache does not work.
0 -
Sounds to me like here there is a mix of topics/issues, one impeding the other to work…
Aren't you facing mostly an "access" issue to your OAC instance for the various methods to work? As it's a private instance, there are more things blocked than allowed.
The SR you raised answered that they didn't test that solution through a proxy, can't you configure things in your tenancy to allow a more direct access to your instance for that kind of "technical" tasks like purging cache?
As you saw from the various posted options and links, there are a number of ways to clear the cache, but all assume you have a full direct access to your OAC instance somehow.
And when reading "Configuring Automated Purge Cache on a Private OAC instance Cannot Connect to Instance (KB154773)", it sounds to me like if the general answer is: manage to get a better access to your OAC instance, and then just use one of the various methods that exist.
But we don't know how your tenancy is configured, what your whole infrastructure is like, and therefore it's all guessing and providing the usual common solution that works for public instances.
0
