Unable to communicate to agent machine after Oracle Plug-In installed

Document ID : KB000097547
Last Modified Date : 03/07/2018
Show Technical Document Details
Issue:
A recently installed a Solaris machine was able to successfully execute a test job.
Then the Oracle Plugin was installed.
Now all jobs go into pending machine status when sent to that agent, regardless of job type.

OA related errors in the logs. 
05/15/2018 12:15:59.688 PDT-0700 1 main.MainThread.CybOaPluginDriver.runApplication[:151] - CybOaPluginDriver terminated 
05/15/2018 12:15:59.688 PDT-0700 1 main.MainThread.CybOaPluginDriver.runApplication[:152] - OaDbHandler initialization failed. No suitable driver found for jdbc:oracle:thin:@ustlpdcsd0020:1524:EBSPROD 
05/15/2018 12:15:59.688 PDT-0700 1 main.MainThread.CybOaPluginDriver.runApplication[:171] - OA plugin initialization problem - TERMINATING 


 
Resolution:
Please confirm the JDBC driver is in place and can be seen and accessed by the agent
See the following link for the steps needed. 
https://docops.ca.com/ca-workload-automation-agent-for-oracle-e-business-suite/11-3/en/installing/install-agent-for-oracle-e-business-suite 


 
Additional Information:
Support has seen where the ojdbc6.jar file was in jars/ext and the agentparm.txt file was configured to look there yet errors persisted.
Support copied the ojdbc6.jar file up one directory from jars/etx to jars and restarted the agent.
That moved past the error.