Answer
There's an effective client-request timeout of around 30 minutes for long-running interactive operations that isn't easily raised through configuration, so for something that genuinely needs longer than that, the practical option is to trigger the equivalent logic directly at the database level (e.g. calling the same underlying API/procedure from a PL/SQL session) rather than through the client — that bypasses the client-request timeout entirely, since the operation is then just a long-running database transaction rather than something waiting on an interactive request/response cycle. It's also worth checking whether the operation's own performance can be improved (heavy view logic is a common cause of these very long run times), since raising a timeout doesn't address the operation being slow to begin with.