Database Plugin for agent - how to test it if the database is not available
Article ID: 199268
Updated On: 10-17-2023
Products
Issue/Introduction
We have a Windows server where they are using the database plugin.
It is installed on a DR server and the database is currently down and we cannot run a job.
Is there another way to test the plugin to verify it is working so when they need to run jobs we know it is available?
Environment
Component : CA Workload Automation System Agent
Resolution
Without access to your database you cannot really test the database plugin.
If you have a second system with a working database plugin you can compare
your new system with it. Compare the agentparm.txt file settings, not their
exact values but that the setting for the db plugin are present and have
appropriate values for your specific databases/environment.
Example:
communication.alias_1=WA_AGENT_DB
db.connectionPool.maxSize=5
db.default.password=824CC7B267621C57
db.default.url=jdbc:oracle:thin:@host1234:1522:XE
db.default.user=scott
db.out.format.paramSeparator=|
db.out.format.valueSeparator==
db.persistance.connectionKeySeparator=#
db.trig.namePrefix=CYB_
db.trig.pollingInterval.ms=10000
db.trig.processMissingTriggers=false
db.trig.propfile=dbtrigOracle
jdbc.drivers=oracle.jdbc.driver.OracleDriver:sun.jdbc.odbc.JdbcOdbcDriver
plugins.start_internal_9=database
Also make sure your job owner's id/password is in autosys_secure.
And depending on what is available to you to test with, make sure you can resolve
and reach the database from the agent plugin host.
Meaning test things like
"nslookup host1234"
"ping host1234"
"telnet host1234 1522
"sqlplus scott@XE"
Also, if there is/was a problem installing the database plugin itself typically you
would also not be able to start the agent itself. You would see errors in the
nohup* files or db* log files on the agent.
Feedback
