Clarity: Creation of a new instance of Status Report generates an 'Error 500 - Internal Server Error' on Clarity UI and AutoNumber limit in app-ca.cog

book

Article ID: 49008

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL CA Identity Manager CA Identity Governance CA Identity Portal Clarity PPM SaaS - Application Clarity PPM On Premise

Issue/Introduction

Description:

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 2012-11-22 17:53:39,286 [http-14001-57] niku.odf (clarity:vinny.Jones:
5727752__D8B25E69-AAA4-460F-9664-62CAD79FDE31: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 "MUN758P.CMN_AUTONUM_GET_NEXT_SP", line 194
ORA-06512: at line 1

Solution:

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 it tried to fetch next value it reported AUTONUMBER SCHEME EXAUSTED error which is an expected behavior
from product.

KEYWORD: CLARITY13OPEN.

Environment

Release: ESPCLA99000-13.1-Clarity-Extended Support Plus
Component: