dSeries shutdown and / or restart failed due to DB ownership issue
Article ID: 448693
Updated On:
Products
Issue/Introduction
Restarting dSeries may fail after some changes were made in database. The following error may be seen in the errors.txt and/or stdout.txt logs:
Starting Server in SSL Mode
Copyright (c) 2026 Broadcom. All rights reserved.
Product Version: 25.1.00
ESP dSeries Workload Automation Server Id: DE25-7500
ESP dSeries Workload Automation Server is starting.
RMI components are ready: 2026-04-04 13:58:03.522
com.ca.wa.comp.configurationserver.WAConfigurationServerException: com.ca.wa.core.engine.rdbms.DatabaseException: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block ..........
at com.ca.wa.core.engine.bootstrap.ServerMain.main(ServerMain.java:442)
Caused by: com.ca.wa.core.engine.rdbms.DatabaseException: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block......... com.ca.wa.core.engine.rdbms.RelationalDatabaseManager.checkSqlException(RelationalDatabaseManager.java:1861)
... 4 more
Caused by: org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
.........
Caused by: org.postgresql.util.PSQLException: ERROR: must be owner of table esp_wso_variable
at .....
[relationaldatabase] [ERROR] main:..... SQL Exception for query: ALTER TABLE ESP_WSO_VARIABLE DROP CONSTRAINT FK_ESP_WSO_VARIABLE; the exception is: ERROR: must be owner of table esp_wso_variable
org.postgresql.util.PSQLException: ERROR: must be owner of table esp_wso_variable
Environment
ESP dSeries Workload Automation: 12.3 or above
Cause
The error is due to mismatch of DB schema owner. If DB was moved or changes owner were done, then all the table and views ownership was not done correctly or skipped.
Resolution
Consult your DBA and / or DB vendor on how to fix the schema ownership. The dSeries will use the user that is defined in db.properties. All the tables, views in the database must be owned by that db user in db.properties file.
Note: If using AD user for MS-SQL, then user that starts the DE service on Windows has to be the owner or must have SELECT, INSERT, DELETE, UPDATE permissions on all tables. We recommend that user that starts dSeries service be the owner of the database used by dSeries.
Additional Information
Here is sample PSQL command for PostgreSQL to change the owner in PostgreSQL, it is provided as is. Make sure to back up database before making any changes. Change new_user , de_database to actual schema and database that dSeries uses to connect to database.
PGPASSWORD=<postgres_password> psql -U postgres -d de_database -h db_host.example.com -v ON_ERROR_STOP=1 -c "
DO \$\$
DECLARE r RECORD;
BEGIN
FOR r IN SELECT tablename FROM pg_tables WHERE schemaname='public' AND tableowner <> 'new_user' LOOP
EXECUTE format('ALTER TABLE public.%I OWNER TO new_user', r.tablename);
END LOOP;
END \$\$;"
Command for views (also needed):
PGPASSWORD=<postgres_password> psql -U postgres -d de_database -h db_host.example.com -v ON_ERROR_STOP=1 -c "
DECLARE r RECORD;
BEGIN
FOR r IN SELECT viewname FROM pg_views WHERE schemaname='public' AND viewowner <> 'new_user' LOOP
EXECUTE format('ALTER VIEW public.%I OWNER TO new_user', r.viewname);
END LOOP;
END \$\$;"
To confirm the changes:
PGPASSWORD=<postgres_password> psql -U postgres -d de_database -h db_host.example.com -c "
SELECT 'table' as kind, tablename as name, tableowner as owner FROM pg_tables WHERE schemaname='public' AND tableowner <> 'new_user'
UNION ALL
SELECT 'sequence', sequencename, sequenceowner FROM pg_sequences WHERE schemaname='public' AND sequenceowner <> 'new_user'
UNION ALL
SELECT 'view', viewname, viewowner FROM pg_views WHERE schemaname='public' AND viewowner <> 'new_user';
"
For Oracle, MS-SQL and DB2, consult your DBA on how to change table ownership.
Feedback
