AGENT filesystem filled up and is now reporting INACTIVE. Unable to set Active.
search cancel

AGENT filesystem filled up and is now reporting INACTIVE. Unable to set Active.

book

Article ID: 9000

calendar_today

Updated On:

Products

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

Issue/Introduction

After the agent file system filled up completely, the agent is no longer communicating with the scheduler. Even though the service is up and running, the scheduler reflects the agent as Inactive.

Environment

Release: WKLOEB01300-11.3-Workload Automation-Agent for Oracle EBusiness Ste
Component:

Cause

As a result of the agent file system filling up, the agent database has potentially become corrupt.

Resolution

In order to resolve this issue, you will need to perform a COLD start of the agent. Follow this process in the exact order documented below to resolve your issue:

  1. Stop the agent services if they aren't already.
  2. Navigate to the base installation directory your agent.
  3. Locate the database directory.
  4. Rename the database directory to database.BAK or something similar. Alternatively, you can move the database folder to a different directory (ie. /tmp) for temporary storage in case we need to recover it.
  5. Restart the agent services.
  6. Give the agent a little time to get started and you should see the status reflected as Active in your scheduler within a few minutes.
  7. If this does not resolve your issue, then you will need to restore the original database directory and Open a case with CA Support.