If there are too much scheduler jobs in an Oracle database, the CJQ process may die unexpectedly. This has nothing to do with job history, not, it’s the number of jobs known to the system. In my experience, the critical number is somewhere around 32.000 in 10.2 64bit. By the way, that’s the solution for this post here.

That’s a PL/SQL script to remove them subsequently, this example focuses on jobs of type ‘ONCE’ and a special user, but it should be no trouble to change the query on dba_scheduler_jobs in a way you need it for your situation.

“Because God got angry at some point in time, computer programmers are forced to deal with localisation and internationalisation.” (From a typo3 tutorial.)

That’s a cool sentence, and the point I laughed about it is gone long time ago. The last days I spent with i18n for my “Usn’s web site (http://www.usn-online.de)“. (I don’t consider this IT blog being a homepage, it’s more or less a public note pad.)

Let me tell you, typo3 is ugly, i18n is ugly, and my unnamed (non-Oracle) web database backend is ugly as well. Without the help-to-help-myself from Maxi (typo3) and TheBonsai (general coding), it would have been a complete mess and waste of time. But sometimes, a quick, customized explanation (aka personal tutorial) immensely speeds up the process. Poor olde brain. :)