Workload Automation Agent Fails to Start with ORA-01017 After Password Change for the Database Plugin
search cancel

Workload Automation Agent Fails to Start with ORA-01017 After Password Change for the Database Plugin

book

Article ID: 445769

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

The Workload Automation Agent with the Database Plugin enabled fails to start. The following error is observed in the db_connection_pool.log:

java.sql.SQLException: ORA-01017: invalid username/password; logon denied

This typically occurs after a database user password has been changed, but the agent continues to attempt connections using cached or pending job data containing the old credentials.

Environment

Product: Workload Automation Agent
Version: 12.x (e.g., 12.1.01.00)
Plugin: Database Plugin
OS: Windows / Linux

Cause

When a database password is changed, the agent may have pending database-related jobs or cached connection pool data that still references the old password. During initialization, the agent attempts to restore these connections; if the credentials are invalid, the ORA-01017 error prevents the agent service from starting successfully.

Resolution

To resolve the initialization failure and flush the invalid credentials, perform a cold-start of the database plugin.

To do so follow these steps:

  1. Stop the Agent: Ensure the agent service is completely stopped.
  2. Update Credentials (if applicable): Use the agent's password utility to encrypt the new password and update the db.default.password parameter in agentparm.txt.
  3. Clear Pending Database Jobs: Navigate to the agent's database directory and delete the following .odb files:
    (Note: Deleting these files will flush pending database-related jobs and trigger monitors.)
    • db_afm.odb
    • internal_plugin_queue_for_database.odb
    • trigmon_pers.odb
  4. Restart the Agent: Start the agent service. The plugin should now initialize without attempting to restore the stale connections.
  5. Validation: Execute a test SQL job to verify that the Database Plugin is communicating correctly with the target database.