AutoSys Workload Automation

 View Only
  • 1.  App Server can't connect to oracle DB

    Posted Mar 18, 2013 07:31 PM
    [color=#04a019][size=7]App server can't connect to a database, moreover after I started app server, no new sqlplus session would connect. I kill app server and sqlplus works again. any help would be appreciated. please see details below.[size][color]
    [root@ip-10-245-214-42 ~]# /etc/init.d/waae_server.ACE start
    WAAE Application Server (ACE)                              [  OK  ]
    [root@ip-10-245-214-42 ~]# tail -12 /opt/CA/WorkloadAutomationAE/autouser.ACE/out/as_server.ACE
    [03/18/2013 19:23:39.5965] 21708 4116129488 L:2 config_vars.cpp 1084 Key [ISDBGACTIV] value [LIGHT,HEAVY,COMM]
    [03/18/2013 19:23:39.5971] 21708 4116129488 L:2 config_vars.cpp 1084 Key [EventServer_1] value [AUTOSYS,1521,orahost]
    [03/18/2013 19:23:39.5974] 21708 4116129488 L:2 config_vars.cpp 2962 rCV #2: Trying to open the file in read mode
    [03/18/2013 19:23:39.5982] 21708 4116129488 L:2 config_vars.cpp 2898 rCV #1: Trying to open the file in read mode
    [03/18/2013 19:23:39.5986] 21708 4116129488 L:2 config_vars.cpp 1059 c == NULL... break!
    [03/18/2013 19:23:39.6632] 21708 4116129488 CAUAJM_E_18407 Failed to connect to Oracle server: AUTOSYS
    [03/18/2013 19:23:39.6636] 21708 4116129488 CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    [03/18/2013 19:23:39.6639] 21708 4116129488 CAUAJM_E_18401 Function <Olog> invoked from <openProc> failed <232>
    [03/18/2013 19:23:39.6641] 21708 4116129488 CAUAJM_E_18402 ORA-12537: TNS:connection closed
    [03/18/2013 19:23:39.6644] 21708 4116129488 L:2 OciConnection.cpp 159 Leaving OciConnection::connect().  openProc() failed.
    [03/18/2013 19:23:39.6647] 21708 4116129488 CAUAJM_E_10649 Server AUTOSYS was not available during connection operation.
    [03/18/2013 19:23:39.6649] 21708 4116129488 L:1 CmPool.cpp 190 Retrying database connection
    [color=#04a019][size=7]I've bumped up Oracle "sesions", but it made no difference. not sure if it is right parameter.[size][color]
    SQL> SELECT value FROM v$parameter WHERE name = 'sessions';
    
    VALUE
    --------------------------------------------------------------------------------
    500
    
    SQL> SELECT COUNT(*) FROM v$session;
    
      COUNT(*)
    ----------
            42
    autosys@ip-10-245-214-42 ~]$ autoflags -a
    408 LINUX ORA 11.3.5 0 f50a2ad6 ip-10-245-214-42 ip-10-245-214-42.ec2.internal


  • 2.  RE: App Server can't connect to oracle DB
    Best Answer

    Posted May 03, 2013 12:27 AM
    This seems like an Oracle client configuration issue.

    Make sure you are using a 32 bit Oracle client.

    Also check the Oracle settings in $AUTOUSER/autosys.sh.$hostname. For the aslibs= line, ensure that the $ORACLE_HOME/lib definition is pointing to the correct 32 bit Oracle client.

    If this continues to be an issue please open a case with support.


  • 3.  RE: App Server can't connect to oracle DB

    Posted Oct 25, 2021 08:01 PM
    Hello, we are experiencing this same exact situation after an Oracle client upgrade from Client 11.2 32-bit to Oracle Client 12.2 32-bit on our Secondary Scheduler in Production. Only thing is we are running Scheduler on Windows with Oracle vs. Linux with Oracle as in the above example.

    This same upgrade went seamless in Development. ORACLE_HOME, TNS_ADMIN paths in Administrator console are accurate. Tnsping works fine, chk_auto_up runs OK, however, App Server fails to restart. Both the DB as well as the Scheduler servers were rebooted and still no luck with App Server starting up.

    Here's chk_auto_up output:
    E:\SrvApps\CA\Workload Automation AE>chk_auto_up
    ______________________________________________________________________________

    CAUAJM_E_10029 Communication attempt with the CA WAAE Application Server has failed! [gaxgpba57:9000]
    CAUAJM_I_50054 Attempting (1) to Connect with Database: pnhap209
    CAUAJM_I_50055 *** Have Connected successfully with Database: pnhap209. ***
    ______________________________________________________________________________

    CAUAJM_I_50128 Connected with Event Server: pnhap209

    ______________________________________________________________________________

    ______________________________________________________________________________

    CAUAJM_E_10029 Communication attempt with the CA WAAE Application Server has failed! [gaxgpba57:9000]
    CAUAJM_I_50038 Checking CA WAAE Primary Scheduler on Machine: GAXGPBA56.southernco.com
    CAUAJM_I_50044 Primary Scheduler is RUNNING on machine: GAXGPBA56.southernco.com

    ______________________________________________________________________________

    E:\SrvApps\CA\Workload Automation AE>

    tnsping output:
    E:\SrvApps\CA\Workload Automation AE>tnsping pnhap209

    TNS Ping Utility for 32-bit Windows: Version 12.2.0.1.0 - Production on 25-OCT-2021 20:00:09

    Copyright (c) 1997, 2016, Oracle. All rights reserved.

    Used parameter files:
    E:\Southern\DBConnectivity\Oracle\Network\Admin\sqlnet.ora

    Used LDAP adapter to resolve the alias
    Attempting to contact (description=(connect_timeout=5)(transport_connect_timeout=3)(retry_count=3)(address_list=(address=(protocol=tcp)(host=lrxgpor062pr-scan.southernco.com)(port=3020)))(connect_data=(service_name=pnhap209_app_user.world)(ur=a)))
    OK (0 msec)

    E:\SrvApps\CA\Workload Automation AE>

    Here's an excerpt of App Server log:

    CA WAAE Application Server Log [10/25/2021 19:54:18]
    Time Message
    ------------------------- ------------------------------------------------------------------------------
    [10/25/2021 19:54:18] CAUAJM_I_40275 Log Rollover level set to <MIDNIGHT,SIZE(100),PURGE(7)>.
    [10/25/2021 19:54:18] CAUAJM_I_40244 EnableIPCaching value set to <1>.
    [10/25/2021 19:54:18] CAUAJM_I_40244 LogMaxEndLines value set to <2,000>.
    [10/25/2021 19:54:18] CAUAJM_I_10655 System is running in single server mode. Event server: pnhap209_app_user.world.
    [10/25/2021 19:54:20] CAUAJM_E_18407 Failed to connect to Oracle server: pnhap209_app_user.world
    [10/25/2021 19:54:20] CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    [10/25/2021 19:54:20] CAUAJM_E_18401 Function <Olog> invoked from <openProc> failed <160>
    [10/25/2021 19:54:20] CAUAJM_E_18402 ORA-12154: TNS:could not resolve the connect identifier specified
    [10/25/2021 19:54:20] CAUAJM_E_10649 Server pnhap209_app_user.world was not available during connection operation.
    [10/25/2021 19:55:20] CAUAJM_E_18407 Failed to connect to Oracle server: pnhap209_app_user.world
    [10/25/2021 19:55:20] CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    [10/25/2021 19:55:20] CAUAJM_E_18401 Function <Olog> invoked from <openProc> failed <160>
    [10/25/2021 19:55:20] CAUAJM_E_18402 ORA-12154: TNS:could not resolve the connect identifier specified
    [10/25/2021 19:55:20] CAUAJM_E_10649 Server pnhap209_app_user.world was not available during connection operation.
    [10/25/2021 19:56:20] CAUAJM_E_18407 Failed to connect to Oracle server: pnhap209_app_user.world
    [10/25/2021 19:56:20] CAUAJM_E_18400 An error has occurred while interfacing with ORACLE.
    [10/25/2021 19:56:20] CAUAJM_E_18401 Function <Olog> invoked from <openProc> failed <160>
    [10/25/2021 19:56:20] CAUAJM_E_18402 ORA-12154: TNS:could not resolve the connect identifier specified
    [10/25/2021 19:56:20] CAUAJM_E_10649 Server pnhap209_app_user.world was not available during connection operation.


  • 4.  RE: App Server can't connect to oracle DB

    Posted Oct 26, 2021 03:53 AM
    While DB entry appeared to be correct in the tnsnames.ora file, apparently, adding '_app_user.world' to the DB name fixed the issue. Was able to restart the App server thereafter. Go figure.

    Thanks!


  • 5.  RE: App Server can't connect to oracle DB

    Broadcom Employee
    Posted May 08, 2013 12:54 AM
    Looks like a connect limitation or a process-spawn issue on the Oracle side. I found a CA doc "TEC506006" (via google search - its on this CA Communities website but also on the CA Support website), that seems related and also indicates a connection limitation. When I'd tested with OracleXP it had a connect limit of 50 (which I had to change via sqlplus) but I don't remember the failure mode(ie error code). If your Oracle OS is *nix based, you might check /var/log/system to see if there is a task spawn error indication..the Oracle installs have a pretty high task/FD requirement you might be hitting that as well.