- 3,741,291 Users
- 2,248,405 Discussions
- 7,861,728 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 381.2K All Categories
- 2.1K Data
- 204 Big Data Appliance
- 1.9K Data Science
- 446.6K Databases
- 220.6K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 23 Multilingual Engine
- 511 MySQL Community Space
- 462 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 448 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.6K SQL & PL/SQL
- 20.8K SQL Developer
- 291.8K Development
- 7 Developer Projects
- 117 Programming Languages
- 288.6K Development Tools
- 94 DevOps
- 3K QA/Testing
- 645.3K Java
- 18 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.7K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 12 Java Essentials
- 141 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 23 JavaScript - Nashorn
- Programs
- 193 LiveLabs
- 34 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 165 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Is there anyway on sqlcl to timeout a long running sql script?
I have a number of reports running on a daily basis, but if one SQL runs too long, I don't want to hold up the rest.
So if there a way on SQLCL to add a timeout to a long running SQL script?
Thanks
Tagged:
Answers
-
If you're on oracle database 18c or higher you can do:
alter system cancel sql :sid,:serial#,@:inst_id;
from another session.
If you're on a lower db version I don't think there's anything other that you can do than kill the session or close the sqlcl window.
-
It would be run on a schedule, so it's not monitored to be able to close the sqlcl window.
I was thinking down the lines of running it on a separate thread, and then killing that thread when it took too long. But not sure if that's possible on sqlcl threading?
