Receiving Error: [CAUAJM_E_112573] Specify an Oracle user and its password. Or, specify a TNS_ADMIN that has been granted the DBA ROLE, DBA_TABLESPACES SELECT, and CREATE SESSION authorities when installing WCC

Products

• Autosys Workload Automation

Issue/Introduction

After specifying the Oracle user that has been granted DBA ROLE, DBA TABLESPACE SELECT, V$PARAMETER SELECT and CREATE SESSION authority, receiving the below errors:

===============================================================================

Web UI Admin Details

--------------------

Specify the Oracle user that has been granted DBA ROLE, DBA TABLESPACE SELECT,

V$PARAMETER SELECT and CREATE SESSION authority.

User name (Default: ####): ######

Password (Default: *****):

===============================================================================

Database Validation

-------------------

 

Error:

[CAUAJM_E_112573] Specify an Oracle user and its password. Or, specify a

TNS_ADMIN that has been granted the DBA ROLE, DBA_TABLESPACES SELECT, and

CREATE SESSION authorities.

Cause

• The DBA privileged user being used doesn't have enough permissions OR
  
  
• The error could also happen if the admin user in question here exists in the root container as well as the Pluggable Database (PDB). The installer runs a query and looks for a value of 1 to be returned:
  select COUNT(*) as value from user_role_privs join all_tab_privs on username = grantee and granted_role = 'DBA' and table_name = 'DBA_TABLESPACES' and grantable = 'YES';
  
  

  cawa_installer.log for the CDB/PDB case would be something like this:

  2026-03-10 09:21:12,422 [main] DEBUG com.ca.autosys.db.validation.DBValidator(131) - Checking the version :19 23
2026-03-10 09:21:12,422 [main] DEBUG com.ca.autosys.db.connection.DBOperations(81) - Running query: select cdb as value from v$database
2026-03-10 09:21:12,427 [main] INFO  com.ca.autosys.db.validation.OracleDBValidator(145) - ORACLE_DB_SETUP : check is contained db- YES
2026-03-10 09:21:12,427 [main] DEBUG com.ca.autosys.db.connection.DBOperations(81) - Running query: SELECT CON_ID as value FROM V$CONTAINERS WHERE ROWNUM=1 ORDER BY CON_ID
2026-03-10 09:21:12,428 [main] INFO  com.ca.autosys.db.validation.OracleDBValidator(132) - ORACLE_DB_SETUP : check is pluggable DB - 3

  ..

  2026-03-10 09:21:12,428 [main] DEBUG com.ca.autosys.db.connection.DBOperations(81) - Running query: select COUNT(*) as value from user_role_privs join all_tab_privs on username = grantee and granted_role = 'DBA' and table_name = 'DBA_TABLESPACES' and grantable = 'YES'
2026-03-10 09:21:12,429 [main] DEBUG com.ca.autosys.db.connection.DBOperations(191) - Query params:
2026-03-10 09:21:12,431 [main] INFO  com.ca.autosys.db.validation.OracleDBValidator(259) - ORACLE_DB_SETUP : use authorization - 2

  
  

  In a PDB on Oracle 19c/23c, the DBA role grant may appear in multiple container rows (once for the local container, once inherited from the CDB root), making the COUNT(*) return 2 instead of 1. But as  the installer is hard coded for 1 at this time, we get an error.

Resolution

• Need to have the Oracle DBA grant the following privileges:

GRANT DBA TO <user>;
GRANT CREATE SESSION TO <user>;
GRANT SELECT ON "SYS"."DBA_TABLESPACES" TO <user> WITH GRANT OPTION;
GRANT SELECT ON "SYS"."V_$PARAMETER" TO <user>;

NOTE: Need to replace <user> with the user that will need to have the access into the database and use that user during the installation

• In case of PDB/CDB, where the query  (select COUNT(*) as value from user_role_privs join all_tab_privs on username = grantee and granted_role = 'DBA' and table_name = 'DBA_TABLESPACES' and grantable = 'YES';)  gives a count >1,  you could alter the admin privileged user (or create a new admin user) so that the query would return a value of 1  only. Some options for the DBA to consider: 

  • Revoke one of the privileges so the query returns a count of 1 only
    -- Connected to the PDB as SYSDBA
REVOKE SELECT ON DBA_TABLESPACES FROM <your_admin_user_you_are_using_for_install>;

• • Or, create a custom admin user just in the PDB and do grants just on the PDB level (not on the CDB/root level).

Additional Information