CA WADE fail-over errors and issues.
search cancel

CA WADE fail-over errors and issues.

book

Article ID: 10374

calendar_today

Updated On:

Products

DSERIES- SERVER CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

The purpose of this document is to provide customers who use the CA Workload Automation DE product with a procedure for the proper shutdown and startup of the product when performing scheduled database maintenance. As with any application that relies on a relational database to perform its day to day operations, it must be shutdown properly to avoid causing any undesired behavior. These procedures will illustrate proper shutdown and start-up sequences for an HA configuration at the application level.



Environment

All supported releases of CA Workload Automation DEDatabase: Any supported database version (current supported databases are DB2, MS SQL Server, Oracle and postgreSQL).Operating System: Any supported OS release

Resolution

For Linux/UNIX based environments:

Shutdown sequence

  1. Logon to your standby DE server.
  2. Navigate to the bin directory beneath the installation path of your DE manager.
  3. Stop the DE Manager by entering the command stopServer. The message "The server has stopped gracefully" confirms the server has been stopped.
  4. Check to ensure that the server did in fact terminate by entering the command status. If the resulting response does not contain a PID beneath the "ESP Server" banner, then the service is in fact down.
  5. Logon to your Primary DE server.
  6. Navigate to the bin directory beneath the installation path of your DE manager.
  7. Stop the DE Manager by entering the command stopServer. The message "The server has stopped gracefully" confirms the server has been stopped.
  8. Check to ensure that the server did in fact terminate by entering the command status. If the resulting response does not contain a PID beneath the "ESP Server" banner, then the service is in fact down.
  9. Once you have verified that both Primary and Standby are down, you can then shutdown the database services as necessary to begin your maintenance activities.

Startup sequence

  1. Start the database services on your database server.
  2. Logon to the Primary DE server
  3. Navigate to the bin directory beneath the installation path of your DE manager.
  4. Start the DE Manager by entering the command startServer. The message "Starting server: [STARTED]" confirms the server has been started.
  5. Check to ensure that the server did in fact start by entering the command status. The resulting response should contain a PID beneath the "ESP Server" banner.
  6. Logon to your Standby DE server.
  7. Navigate to the bin directory beneath the installation path of your DE manager.
  8. Start the DE Manager by entering the command startServer. The message "Starting server: [STARTED]" confirms the server has been started.
  9. Check to ensure that the server did in fact start by entering the command status. The resulting response should contain a PID beneath the "ESP Server" banner.
  10. You can validate the environment by running a test job; the VERIFY application works well for this as it checks multiple components, to ensure product functionality. Alternatively, you should begin to see your batch activities resuming according to their schedules.

 

For Windows based environments:

Shutdown sequence

  1. Logon to your Standby DE server.
  2. Click on the Windows Start button, charm, etc and locate the "Run" feature.
  3. Type services.msc to launch the Services console.
  4. Locate the CA Workload Automation DE service, right-click on it and select Stop
  5. Logon to your Primary DE server.
  6. Click on the Windows Start button, charm, etc and locate the "Run" feature.
  7. Type services.msc to launch the Services console.
  8. Locate the CA Workload Automation DE service, right-click on it and select Stop.
  9. You can now safely shutdown the database services on your database server.

Startup sequence

  1. Start the database services on your database server.
  2. Logon to the Primary DE server
  3. Click on the Windows Start button, charm, etc and locate the "Run" feature.
  4. Type services.msc to launch the Services console.
  5. Locate the CA Workload Automation DE service, right click on it and select Start.
  6. Logon to your Standby DE server.
  7. Click on the Windows Start button, charm, etc and locate the "Run" feature.
  8. Type services.msc to launch the Services console.
  9. Locate the CA Workload Automation DE service, right click on it and select Start.
  10. You can validate the environment by running a test job; the VERIFY application works well for this as it checks multiple components, to ensure product functionality. Alternatively, you should begin to see your batch activities resuming according to their schedules.

Additional Information

If there you encounter any issues with restarting of the DE services, you should open a case with CA Support immediately and provide all of the necessary logs to aid in the review and troubleshooting process. Please include the logs prior to the shutdown of the application as well as the logs during the time at which you attempted to restart the services. CA Support will need the tracelogs, the errors.txt and the stdout.txt files for review.