Control-M/Enterprise Manager 'check_all' or 'ctl' life check on components periodically failed with error 'Failed to login the database, Exiting application.'

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Enterprise Manager


    COMPONENT:

    Control-M/Enterprise Manager


    APPLIES TO:

    Control-M/Enterprise Manager all versions with Oracle database



    PROBLEM:

    Symtoms:
    When executes 'check_all' or 'ctl' commands to check the status of Control-M/Enterprise Manager components, some components returned 'Failed to login the database, Exiting application.' at first attempt, but returned 'is alive' status on the next execution.

    check_all -U emuser -P ****** 

    Database Server Status 
    ====================== 
    Database Server is active 


    Gateway Status 
    ============== 
    Gateway "xxx" on xxx is alive! 
    Message returned: "Connected" 


    GCS Status 
    ========== 
    Failed to login the database, Exiting application. 


    GUI_Server Status 
    ================= 
    GUI_Server "xxx" on xxx is alive! 
    Message returned: "OK" 

    BIM Status 
    ========== 
    No BIM(s) registered. 


    Forecast Server Status 
    ====================== 
    Forecast_Server "xxx" on xxx is alive! 
    Message returned: "OK" 


    Self Service Server Status 
    ========================== 
    Self_Service_Server "xxx" on xxx is alive! 
    Message returned: "OK" 


    CONTROL-M Configuration Server Status 
    ================================ 
    CMS "CMS" on xxx is alive! 
    Message returned: "OK" 


    CONTROL-M/EM Configuration Agent Status 
    ================================== 
    Failed to login the database, Exiting application. 


    Control-M Naming Service Daemon Status 
    ====================================== 
    Naming Service status: Running on local machine, xxx:13076 

    All Control-M/Enterprise Manager components are verified to be up and running and no exception observed on the respective processes logs.


    CAUSE:

    Maximum number of allowed connections for the Oracle database reached.


    SOLUTION:

    Please work with Oracle database administrator to review and fine tune client connection settings such as to allow more concurrent connection.

     

     


    Article Number:

    000134629


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles