CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10014 Error establishing a database connection. dbstatistics: Unable to run dbspace
book
Article ID: 115650
calendar_today
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)CA Workload Automation AE - Scheduler (AutoSys)Workload Automation Agent
Issue/Introduction
During the execution of the DBMaint script, following errors are displayed in the DBMaint.out file
CAUAJM_I_60007 Archiving Events... CAUAJM_I_60013 Number of Events Deleted: 35510 CAUAJM_I_60014 Archiving Job Runs... CAUAJM_I_60017 Number of job runs deleted: 12267 CAUAJM_I_60018 Archiving Audit Info... CAUAJM_I_60021 Number of Audit Infos Deleted: 73 CAUAJM_I_60019 dbstatistics: Running dbstatistics at: Mon Sep 17 13:01:30 2018 CAUAJM_I_60020 dbspace: Running dbspace at : Mon Sep 17 13:03:19 2018 CAUAJM_E_18407 Failed to connect to Oracle server: ORASID CAUAJM_E_18400 An error has occurred while interfacing with ORACLE. CAUAJM_E_18401 Function invoked from failed <154> CAUAJM_E_18402 ORA-12537: TNS:connection closed CAUAJM_E_10649 Server ORASID was not available during connection operation. CAUAJM_E_18407 Failed to connect to Oracle server: ORASID ../.. CAUAJM_E_50033 Error initializing tx subsystem: CAUAJM_E_10014 Error establishing a database connection. dbstatistics: Unable to run dbspace
Environment
Autosys 11.3.6 SP6 with Oracle Database on Linux
But this problem can happen with any other Autosys release
Cause
The max number of Oracle processes were reached. This is seen in the Oracle alert log file
Resolution
Increase number of Oracle processes from 300 to 400
Depending on your needs and Autosys activity, these numbers might be greater than 300 or 400