Issue with accessing "Environment" tab
search cancel

Issue with accessing "Environment" tab

book

Article ID: 434518

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Following error shows when navigate to the Environments tab under Modelling section,

An illegal parameter was passed to the API : Cannot find class 'Environment' in database schema

New environment cannot be saved with the same error.

TdmWeb.log:

[23/Mar/2026:02:52:54 +0000] "GET /TDMDataReservationService/api/ca/v1/environments?page=1&projectId=1180&size=25&versionId=1181 HTTP/1.1" 400 211

TDMDataReservation.log:

2026-03-22 20:08:32.361 EDT [ERROR] [https-jsse-nio-8443-exec-83] --- [U:varaprasad-kondapaka][M:GET][P:/api/ca/v1/environments]                          c.c.t.d.g.GraphAPIHelper:  Exception in a transaction. Transaction rolled back.
java.lang.IllegalArgumentException: Cannot find class 'Environment' in database schema
	at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.getVerticesOfClass(OrientBaseGraph.java:729)
	at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.getVerticesOfClass(OrientBaseGraph.java:713)
	at com.tinkerpop.blueprints.impls.orient.OrientBaseGraph.getVertices(OrientBaseGraph.java:750)
	at com.tinkerpop.blueprints.util.wrappers.partition.PartitionGraph.getVertices(PartitionGraph.java:107)
...

Environment

TDM docker portal 4.11.x

Cause

The error indicates the OrientDB database doesn't have the required data/schema -- the volume of OrientDB could be corrupted, may need to recreate it.

But the OrientDB PVC data must remain in sync with the gtrep SQL database.

Specifically, the TDM environments data in OrientDB needs to match the environments data in the gtrep SQL database.
 
Re-creating or wiping one will necessitate re-creating or wiping the other.

 

The root cause of the issue could be due to either the PVC or the SQL gtrep database was re-created after this specific environment was established in TDM, leading to the current discrepancy.

Resolution

Rebuild the whole TDM docker portal, or at least re-init both the gtrep database and the OrientDB.