TDoD service not working with users created in datamaker
search cancel

TDoD service not working with users created in datamaker

book

Article ID: 218295

calendar_today

Updated On:

Products

CA Agile Requirements Designer

Issue/Introduction

In TDOD service, users (traininguser) which we created in Datamaker to access the TDoD service are not working and also administrator is giving below error:

Error:

Could not log into the specified TDoD service with the specified user name and password.TDoD service reported the following error:

Fault code s:Client: Operation: AuthenticateUser: Error executing: pk_gtrep_su.p_insert_su_log: ORA-01654: unable to extend index ARD.GTREP_SUL_NU by 128 in tablespace T_ARD ORA-06512: at "ARD.PK_GTREP_SU", line 257 ORA-06512: at line 1

Environment

Release : 3.0

Component : AGILE REQUIREMENTS DESIGNER TFS INTEGRATION

Cause

Fault code s:Client: Operation: AuthenticateUser: Error executing: pk_gtrep_su.p_insert_su_log: ORA-01654: unable to extend index ARD.GTREP_SUL_NU by 128 in tablespace T_ARD ORA-06512: at "ARD.PK_GTREP_SU", line 257 ORA-06512: at line 1

Looking at the above message, there are two Oracle errors reported. The first error ORA-01654 is documented by Oracles as:

ORA-01654 unable to extend index string.string by string in tablespace string

Cause: Failed to allocate an extent for index segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

The Oracle database cannot extend the index for ARD.GTREP_SUL_NU by 128 in the tablespace T_ARD. This could indicate that the T_ARD tablespace is full and out of space.

For more information, see http://www.dba-oracle.com/t_ora_01654.htm

The second error ORA-06512 appears to be a "catch-all" error that generally appears as part of the message stack in which the message directly preceding Oracle ORA-06512 will list the reason for the error.

See http://www.dba-oracle.com/t_ora_06512_tips.htm

 

Resolution

 

You need to report these two errors to your DBA and work with them to resolve the tablespace issue.