Many portal functions are not working after GTREP outage and recovery
search cancel

Many portal functions are not working after GTREP outage and recovery

book

Article ID: 446341

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

GTREP database outage due to disk full (transaction log full).

After adding more disk space and database recovery, many operations on TDM portal start failing, such as failed to get Environment details, cannot save filters for data model scanning, PII scan failed, etc.

Following errors might be found:

The transaction log for database 'gtrep' is full due to 'LOG_BACKUP'
o.h.e.j.s.SqlExceptionHelper:  SQL Error: 9002, SQLState: S0002
o.h.e.j.s.SqlExceptionHelper:  SQL Error: 18456, SQLState: 08S01
o.h.e.j.s.SqlExceptionHelper:  Kerberos Login failed: Integrated authentication failed. ClientConnectionId:3c036ad9-85c9-4b43-9d9b-1caaa15c3783 due to javax.security.auth.login.LoginException (Unable to obtain password from user
)

Environment

TDM docker portal 5.x

Cause

The issue is caused by the corruption of the database connections in the TDM Portal. When the GTREP repository becomes unavailable or read-only (due to disk space issues), the existing connections in the TDM Portal become stale or enter an error state. Even after the DBA resolves the database space issue, the Portal service continues to use these stale connections, leading to different operation failures on portal.

The login failed error is misleading.

Resolution

After GTREP recovery, need to restart TDM to re-initialize the connections.