Status report fails with AutoNumber Limit Reached SCHEME_EXHAUSTED in logs
search cancel

Status report fails with AutoNumber Limit Reached SCHEME_EXHAUSTED in logs

book

Article ID: 49008

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

When Project managers try to create a New instance of Status Report from Project - Properties - 'Status Report' page the following error message is generated: 'Error 500 - Internal Server Error'

The Clarity app-ca.log file does contain the following error messages;

ERROR ...(clarity:user:....odf.subObjectProperties)

AutoNumber Limit Reached when generating the next number for object 'cop_prj_statusrpt' + attribute 'name' using scheme defined in partition
'NIKU.ROOT'com.niku.union.persistence.PersistenceApplicationException:

java.sql.SQLException: [CA Clarity][Oracle JDBC Driver]
[Oracle]ORA-20001: SCHEME_EXHAUSTED
ORA-06512: at "CLARITY DB.CMN_AUTONUM_GET_NEXT_SP", line 194
ORA-06512: at line 1

Environment

Clarity 15.9.3

Resolution

The Alphanumeric auto number segment in the attribute 'Name' - Auto Numbering tab of the 'Status Report' object was not set to auto-extend = true and value was set to "00". This value had reached to its maximum i.e. "ZZ".


Because auto-extend was false, when system tried to fetch next value it reported AUTONUMBER SCHEME EXAUSTED error which is an expected behavior from product.