oracle.jdbc.OracleDatabaseException: ORA-01950: no privileges on tablespace 'USERS' . Cannot login to TDM Portal using any account .

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Login is failing for all accounts when trying to login to the TDM portal.
We need to reset TDM portal password as we used old password and it does not work.

It used to work with LDAP and the admin user, suddenly none of them works.

Log analysis suggest that GTREP(repository) has lost privilege on tablespace USERS.

Environment

Release : 4.9

Component : CA Test Data Manager - TDM Web Portal

Cause

Below error in the TDMWeb logs suggest that there is issue with the GTREP(Repository) DB User.

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

2021-05-06 15:42:14.446 UTC [WARN ] [http-nio-8080-exec-3     ] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  SQL Error: 1950, SQLState: 42000
2021-05-06 15:42:14.446 UTC [ERROR] [http-nio-8080-exec-3     ] --- [U:][M:][P:]                      o.h.e.j.s.SqlExceptionHelper:  ORA-01950: no privileges on tablespace 'USERS'

2021-05-06 15:42:14.446 UTC [ERROR] [http-nio-8080-exec-3     ] --- [U:][M:][P:]                 o.h.i.ExceptionMapperStandardImpl:  HHH000346: Error during managed flush [org.hibernate.exception.SQLGrammarException: could not execute statement]
2021-05-06 15:42:14.448 UTC [ERROR] [http-nio-8080-exec-3     ] --- [U:][M:][P:]              c.c.t.c.e.h.GlobalExceptionConvertor:  HTTP Error - INTERNAL SERVER ERROR: Exception: could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.SQLGrammarException: could not execute statement
oracle.jdbc.OracleDatabaseException: ORA-01950: no privileges on tablespace 'USERS'

 at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:513)
 ... 144 common frames omitted
Wrapped by: java.sql.SQLSyntaxErrorException: ORA-01950: no privileges on tablespace 'USERS'

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

Resolution

The issue got resolved after privilege/permission issue with the DB user was rectified by customer's DBA / DB team.