After importing updated trusted root certificates into the Oracle Wallet (e.g. because a third-party integration like Slack rotated its certificates), outbound HTTPS calls from the database (via UTL_HTTP) still fail with a certificate validation error. Does anything actually need to be restarted for the updated wallet to take effect?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Yes — the database itself needs to be restarted (not just the middleware/application server) for UTL_HTTP-based outbound calls to pick up an updated Oracle Wallet, since that HTTP call is made directly by the database process, independent of the middle tier. Restarting only the middleware server won't refresh the database's own wallet-backed trust store.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions