AutoSys Workload Automation

  • 1.  How to verify database connection details

    Posted Jun 14, 2018 01:07 PM

    Hey Guys,

     

    I am super new to Ca and autosys world.... i am trying to verify a database connection details that autosys secondary scheduler is pointing to.... Where do i go on the scheduler server or what command line will show me the connection details...

     

    regard,

    Sam



  • 2.  Re: How to verify database connection details

    Broadcom Employee
    Posted Jun 14, 2018 01:18 PM

    Hi Sam,

     

    You can use the following command:

     

    chk_auto_up

     

    This can be sent from the command line

     

    I hope this can help

     

    Thanks,

    Roya



  • 3.  Re: How to verify database connection details

    Posted Jun 14, 2018 01:53 PM

    Thanks Roya for your prompt response.. When i use the command line , it only showed me the Machine status if online/offline...... But did not show any details about the database..

     

    Regards,

    Sam



  • 4.  Re: How to verify database connection details
    Best Answer

    Broadcom Employee
    Posted Jun 14, 2018 02:50 PM

    Hi Sam,

     

    Please find below an example of the result returned by "chk_auto_up":

     

    chk_auto_up
    ______________________________________________________________________________

    CAUAJM_I_50054 Attempting (1) to Connect with Database: pharo01-i12441,1433:AEDB

    CAUAJM_I_50055 *** Have Connected successfully with Database: pharo01-i12441,1433:AEDB. ***   < =======
    ______________________________________________________________________________

    CAUAJM_I_50128 Connected with Event Server: pharo01-i12441,1433:AEDB

    ______________________________________________________________________________

    ______________________________________________________________________________

    CAUAJM_I_50038 Checking CA WAAE Primary Scheduler on Machine: pharo01-I12441.ca.com
    CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: pharo01-I12441.ca.com
    ______________________________________________________________________________

     

    In a Full HA configuration, chk_auto_up provides the information about connection to the Primary and Dual databases.

     

    I hope this can help.

     

    Thanks,

    Roya



  • 5.  Re: How to verify database connection details

    Broadcom Employee
    Posted Jun 14, 2018 03:03 PM

    Hi Sam,

     

    Thank you very much for your reply.

     

    You run the command "chk_auto_up" from the operating system command prompt when AutoSys environment set. Example:

     

    $ echo $AUTOSYS

    /opt/CA/WorkloadAutomationAE/autosys

     

    $ echo $AUTOUSER

    /opt/CA/WorkloadAutomationAE/autouser.PRD

     

    $ chk_auto_up   < ======

    ______________________________________________________________________________

    CAUAJM_I_50054 Attempting (1) to Connect with Database: pharo01-i12441,1433:AEDB

    CAUAJM_I_50055 *** Have Connected successfully with Database: pharo01-i12441,1433:AEDB. ***   < =======
    ______________________________________________________________________________

    CAUAJM_I_50128 Connected with Event Server: pharo01-i12441,1433:AEDB

    ______________________________________________________________________________

    ______________________________________________________________________________

    CAUAJM_I_50038 Checking CA WAAE Primary Scheduler on Machine: pharo01-I12441.ca.com
    CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: pharo01-I12441.ca.com
    ______________________________________________________________________________

     

    I hope this can help.

     

    Thanks,

    Roya



  • 6.  Re: How to verify database connection details

    Broadcom Employee
    Posted Jun 14, 2018 03:14 PM

    Hi Sam,

     

    You can also find the configured database information in the config.$AUTOSERV file under $AUTOUSER directory.

     

    Example:

     

    $ cd $AUTOUSER

     

    $ more config.PRD

     

    # Keyword: Provider=<ORA|SYB>
    #
    # Specifies which Relational Database Management System (RDBMS)
    # provider CA Workload Automation AE uses.
    #
    # The valid values are as follows:
    #
    # ORA = Identifies Oracle as the database provider.
    # SYB = Identifies Sybase as the database provider.
    #
    Provider=ORA
    #+---------
    #
    # Keyword: DBAccess=username/password
    #
    # Defines the user name and password (in encrypted format) used by
    # the scheduler and application server to connect to the database.
    # The database user name and password is defined during the CA
    # Workload Automation AE installation.

     

    DBAccess=autosys/E6F5F6A37E4ED383DA19CC52A6890474
    #+----------
    #
    # Keyword: EventServer_1=<SYBASE_SVR:SYBASE_DB,DBPORT,DBHOST |
    # SYBASE_SVR:SYBASE_DB,DBPORT,DBHOST,PRINCIPAL |
    # ORACLE_SVR,DBPORT,DBHOST >
    # Specifies the database for a specific event server. Typically,
    # this name is AEDB. In dual event server mode, the value for both
    # secondary event servers can be different and it is specified as
    #
    # Keyword: EventServer_2=<SYBASE_SVR:SYBASE_DB,DBPORT,DBHOST,PRINCIPAL |
    # ORACLE_SVR,DBPORT,DBHOST >
    #
    # When CA Workload Automation AE runs in single event server mode,
    # only one event server is defined. If you wish to run CA Workload
    # Automation AE in dual event server mode, you must specify the
    # database that the second event server will connect to in the
    # EventServer_2 keyword.
    #
    #
    # The valid values for a Sybase database are as follows:

    #
    # SYBASE_SVR:SYBASE_DB,DBPORT,DBHOST,PRINCIPAL
    # Identifies Sybase as the database for a specific event server.
    #
    # For Sybase, the parameters that compose this keyword value
    # consist of the Sybase server name:database name combination,
    # database TCP-IP port, the database host and the optional server
    # principal if kerberos authentication is used, comma-delimited.
    #
    # Example: EventServer_1=SYBSVRPROD:AEDB,5000,MACHPROD,SybPrincipal
    #
    #
    # The valid values for an Oracle database are as follows:
    #
    # ORACLE_SVR,DBPORT,DBHOST
    # Identifies Oracle as the database for a specific event server.
    #
    # For Oracle, the parameters that compose this keyword value
    # consist of the Oracle SID, database TCP-IP port, and the
    # database host, comma-delimited.
    #
    # Example: EventServer_1=orcl,1521,MACHPROD
    #

    # Note: For Oracle database, database TCP-IP port and database host
    # values will be ignored when DBAccessMode value is set to 1.
    #

    EventServer_1=DB1,1521,dbserver1      < ========
    EventServer_2=DB2,1521,dbserver2      < ========

     

    +----------
    #
    # Keyword: DBLibWaitTime=<value>
    #
    # Defines the time (in seconds) the scheduler and the application
    # server wait before breaking the connection with an event server
    # in an unknown state. That is, the scheduler and the application
    # server maintain and check connections with the databases, and if
    # an event server is in an unknown state, the connection is broken
    # after the specified time.
    #
    # Default: 90
    #
    # Note: If you set the DBLibWaitTime parameter to 0 (zero), the
    # scheduler or the application server do not time out. They
    # wait until the database responds. We do not recommend
    # setting this parameter to 0 because the scheduler may stop
    # responding.
    #
    #DBLibWaitTime=90

     

    #+----------
    #
    # Keyword: DBEventReconnect=<value> - Single Server Mode
    # DBEventReconnect=<value,value> - Dual Server Mode
    #
    # Defines the number of times the scheduler or the application
    # server try to connect (or reconnect) to an event server before
    # shutting down or before rolling over to single event server mode.
    #
    # Default: 50 (in single event server mode)
    # 50,5 (in dual event server mode)
    #
    # Limits: For dual event server mode, specify two numbers separated
    # by a comma.
    #
    DBEventReconnect=50,5
    #
    # In Dual Event Server Mode, this parameter contains two values
    # describing the connection and rollover behaviors as follows:
    #
    #DBEventReconnect=50,5

    .........

     

    I hope this can help.

     

    Thanks,

    Roya



  • 7.  Re: How to verify database connection details

    Posted Jun 17, 2018 10:15 PM

    Hi Sam,

     

    Did Roya's response(s) help with the information you were after?

    Can you please help to mark the correct response as answer if you do not have further questions?

     

    Thanks,

    Chandru



  • 8.  Re: How to verify database connection details

    Posted Jun 18, 2018 08:22 AM

    Hi Sam,

     

    I add the following documentation link to help you on Scheduler Troubleshooting  and all detail about chk_auto_up

    utility .

     

     

    https://docops.ca.com/ca-workload-automation-ae/11-4-2/en/troubleshooting/troubleshooting-ae/scheduler-troubleshooting

     

    Thanks and warm regards,

     

    Faouzia



  • 9.  Re: How to verify database connection details

    Posted Jun 19, 2018 03:22 AM

    Hi Sam

     

    A good tip is to run sqlplus ( If the database is Oracle or any other sql command for Sybase or SQL Server on Windows) from the scheduler/application server to connect to the second event_server which is defined in your $AUTOUSER/config.$AUTOSERV file to query the Autosys alamode table with the autosys account.

    This is going to confirm if the password of the autosys user is OK in the database and if there is no issue with the tnsnames.ora or Oracle listener. ( If database is Oracle )

     

    sqlplus autosys/<password>@<SID defined in the autosys configuration file>

    select * from alamode;

    exit;

     

    If sqlplus is OK, look into the as_server log file in directory $AUTOUSER/out to find out any error message

    If there is no error in the as_server and event_server logs, then run the chk_auto_up steps.

     

    You can also use additional flags like: chk_auto_up -r 111

     

    Regards

    Jean Paul