Upgrade to dSeries 25.0 fails with ORA-00904: "PASSWORD_HISTORY": invalid identifier

Products

• ESP dSeries Workload Automation
• ESP dSeries Workload Automation - Scheduler (dSeries)

Issue/Introduction

After performing an in-place upgrade from dSeries 12.3 to 25.0, the server fails to start. The following error is observed in the tracelog:

text

 

com.ca.wa.publiclibrary.engine.security.SecurityException: Failed loading users and groups.    at com.ca.wa.core.engine.security.SecurityManagerImpl.loadPrincipals(SecurityManagerImpl.java:207)...Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "PASSWORD_HISTORY": invalid identifier...SQL = SELECT USER_ID, DISPLAY_ID, NAME, PASSWORD, USER_TYPE, LOCK_ID, MODIFIED_BY, MODIFIED_TIME, PASSWORDEXPIRY, PASSWORDLASTMODIFIEDTIME, PASSWORDCOMPLEXITYVALIDATION, PASSWORDINVALIDATTEMPT, PASSWORD_HISTORY, PREVENTCONCURRENTLOGIN FROM ESP_USER ORDER BY DISPLAY_ID

Environment

• Source Version: ESP dSeries Workload Automation 12.3
• Target Version: ESP dSeries Workload Automation 25.0
• Database: Oracle

Cause

This error occurs because the database schema was not fully updated during the in-place upgrade process. Specifically, the PASSWORD_HISTORY column was not added to the ESP_USER table.

This is often caused by a failure in an earlier step of the upgrade script (such as an ALTER TABLE command on the ESP_AGENT_RP table) which prevents the rest of the schema updates from executing. If the inplaceupgrade.log shows an ORA-01430: column being added already exists or similar database exception during the upgrade, the process may stop before reaching the ESP_USER table modifications.

Resolution

To resolve this issue, the upgrade must be performed again on a clean database state.

1. Verify Schema State: Engage your DBA to run the following command against the dSeries database to confirm the missing column: DESC ESP_USER;

2. Full Rollback: Roll back the dSeries server application files and restore the Oracle database using the backup taken immediately prior to the upgrade attempt. This step is mandatory to ensure a consistent state. See Roll Back the Server to a Previous Version.

3. Check Upgrade Logs: Review the inplaceupgrade.log located in the ####/upgrades/ directory. Look for any SQL errors (e.g., ORA-01430) that occurred during the first attempt. Ensure that any environmental or permission issues identified in the log are resolved.

4. Re-attempt Upgrade: Re-run the in-place upgrade to version 25.0. Ensure the database user has sufficient privileges to perform ALTER and CREATE operations on all tables.

5. Verification: Once the upgrade utility reports success, verify that the ESP_USER table now contains the PASSWORD_HISTORY column before starting the server.