Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 439 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Prevent queries from killing my dev server

I'm running Oracle 10g XE in a Windows Server 2003 box somewhere in our LAN to power a PHP application running on a local Apache/2.4 server in my Windows 7 PC. I've a couple of queries with inline views that —all of a sudden— apparently need several hours to complete, while they should run in a few seconds (and that's what they used to do until some revisions ago).
The problem is that I cannot even diagnose the issue because everything I try (run my app or even calculate the explain plan) stays running endlessly and prevents any other page from the site from loading until I log into the Windows Server box using Terminal Services and manually restart Oracle. The whole restart takes several minutes.
As far as I know there isn't a query timeout feature in the OCI8 PHP extension and my attempts to configure Oracle to kill long running queries automatically have hit a wall of endless technical documentation and custom PL/SQL scripts beyond my area of expertise.
Is there anything relatively simple I could do to mitigate this issue?
Answers
-
May be you can try PHP function set_time_limit() or max_execution_time in php.ini.
-
I hadn't through of that because I assumed it wouldn't work. I've just tried and I can confirm it doesn't work. Quoting from the documentation:
The maximum execution time is not affected by system calls, stream operations etc.