ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Test Match failed with database error ORA-00955: name is already used by an existing object

book

Article ID: 8566

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When publishing through the self service console on the TDM Portal,  the test match ends up failing with the following Oracle exception in the TDM Job Engine.  

Default location for TDM Job Engine (C:\ProgramData\CA\CA Test Data Manager Portal\logs\TDMJobEngine.log)

ORA-00955: name is already used by an existing object 
at System.Data.OracleClient.OracleConnection.CheckError(OciErrorHandle errorHandle, Int32 rc) 
at System.Data.OracleClient.OracleCommand.Execute(OciStatementHandle statementHandle, CommandBehavior behavior, Boolean needRowid, OciRowidDescriptor& rowidDescriptor, ArrayList& resultParameterOrdinals) 
at System.Data.OracleClient.OracleCommand.ExecuteNonQueryInternal(Boolean needRowid, OciRowidDescriptor& rowidDescriptor) 
at System.Data.OracleClient.OracleCommand.ExecuteNonQuery() 
at TestMatch.TestMatchProcessor.CreateTMCTableInDatabase(String newTableName, Database dbToUse, DbConnection openConn, Boolean isRemote) 
at TestMatch.Program.Main(String[] args) 

How can I resolve this issue?

Cause

Issue is that the TDM Portal process may create a temporary table to assist with test matching in your target database.  If the process is killed,  the temporary table will be left in the target database,  and will prevent future test matchings from taking place in your target database.

Environment

TDM 4.X using Oracle as the TDM repository

Resolution

To resolve this issue,  you will need to do the following.

1) Open your favourite SQL Query tool, connect, and browse for tables in your target database that you are test matching with.

2) In your table view,  look for a table name that begins with "FNV_".   If you find a table with this prefix,  delete it.

3) Publish your job,  and verify the removal of the temporary table has addressed your issue.

Additional Information

If you do not find a tablename in your target database with FNV,  and this error still happens when creating a test match with the TDM portal,  please reach out to support for assistance on this issue.