cir-51: "TNS:listener could not find available handler for requested type"
- Article Type: General
- Product: Aleph
- Product Version: 20
Problem Symptoms:
The cir-51 ("Overdue and Lost Billing Summary Letter") jobs for some ADMs run OK, but those for other ADMs stay in a 'running' state (in the Task Manager Batch Queue) or exit with the following error:
"ORA-12520: TNS:listener could not find available handler for requested type"
Cause:
Too many jobs running at the same time. In this case, the cir-51 jobs for 52 ADMs (a total of 140 jobs) were set up in the $alephe_tab/job list to run within a one-minute period.
Resolution:
Stagger the times for the release of the jobs in the job_list; for instance, spreading them out over a half-hour time period. There is no reason that the cir-51 jobs (or any jobs) need to all run at once.
Additional Information
As noted in Article 000018016 ("ORA-12520: TNS:listener could not find available handler for requested") this error occurs when Oracle exceeds the max-process limit.
Though this might be resolved by increasing the number of processes in Oracle as described in Article 000022411 ("Number of Oracle processes exceeded"), in the case where it happens only when certain batch jobs are running, the better approach is to stagger the running of the jobs as described above.
- Article last edited: 3/13/2014