Autosys API Web Interface is Not Working
Article ID: 9297
Updated On:
Products
Issue/Introduction
After applying an API to our Autosys environment, we are unable to connect to the webserver. We are getting database connection errors:
2018-01-18 12:07:16,408 [AEConnMgr Monitor] ERROR com.ca.waae.dbaccess.dao.AEConnection - createEntityManager [EventServer_1] -> IllegalStateException encountered. Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
Error Code: 17002...Throwing AEConnFatalException.
.
.
.
2018-01-18 13:50:22,399 [AEConnMgr Monitor] ERROR com.ca.waae.dbaccess.dao.AEConnection - createEntityManager [EventServer_1] -> IllegalStateException encountered. Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12504, TNS:listener was not given the SID in CONNECT_DATA
Error Code: 12504...Throwing AEConnFatalException.
Environment
CA Workload Automation AE r11.x or 12.x
Cause
Although Autosys can connect to the AEDB using a Oracle SID, service name or alias, the webserver connects to the AEDB using only the Oracle SID. The first database error means that the listener is not running on the database server. The second database error means that the provided database name is not a valid Oracle SID in the tnsnames.ora file.
Resolution
Resolve the Database Errors
1. Login to the Autosys server and navigate to the $AUTOUSER directory
2. View the config.$AUTOSERV file and look for the EventServer parameter - the first value in the parameter is the database name (make note of this)
3. Login to the database server and confirm your environment variables for Oracle have been set
4. Start the listener service with the following command: ./lsnrctl start
5. Navigate to the $TNS_ADMIN directory and check the tnsnames.ora file for the database name you saw in the config.$AUTOSERV file - the tnsnames.ora entry may look something like this:
FAKE_ALIAS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = EXAMPLE.HOSTNAME.COM )(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = FAKE_ALIAS.COMPANY.COM)
)
)
6. Make note of the name that appears in place of the blue text
Update the EventServer Parameter
1. From the Autosys server, edit the config.$AUTOSERV file and look for the EventServer parameter
2. Replace the first value (the database name) with the Oracle SID you saw in the tnsnames.ora file (the blue text)
3. Save the file
4. Restart the scheduler service
5. Confirm that Autosys can still connect to the database by running chk_auto_up or by viewing the event_demon log
You should be able to access the API web interface.
Feedback
