PLS-00114: identifier 'MAX_CHANNEL_PER_BLUEPRINT_EXIS' too long When upgrading from 15.9.0.1 to 15.9.1

book

Article ID: 208393

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

Unable to upgrade Clarity ppm to version 15.9 from 15.9.0.1.

The admin.log reports error

2/09/21 3:09 PM (ExecTask) Current database version is database_20201228_1103
2/09/21 3:09 PM (ExecTask) DBDriver for database_20210123_1319
2/09/21 3:09 PM (ExecTask) Start installation of DBDriver ...
2/09/21 3:09 PM (ExecTask) 
2/09/21 3:09 PM (ExecTask) Note: Foreign Keys have been disabled
2/09/21 3:09 PM (ExecTask) Process - pre-upgrade: GOVERNOR_LIMIT.xml
2/09/21 3:09 PM (ExecTask) 
2/09/21 3:09 PM (ExecTask) SQL Text:
2/09/21 3:09 PM (ExecTask) 
2/09/21 3:09 PM (ExecTask)     DECLARE
2/09/21 3:09 PM (ExecTask)         MAX_CHANNEL_PER_BLUEPRINT_EXISTS INTEGER;
2/09/21 3:09 PM (ExecTask)         MAX_COUNT INTEGER;
2/09/21 3:09 PM (ExecTask)     BEGIN
2/09/21 3:09 PM (ExecTask)         SELECT COUNT(*) INTO MAX_CHANNEL_PER_BLUEPRINT_EXISTS FROM cmn_gov_limits WHERE code = 'MAX_CHANNEL_PER_BLUEPRINT';
2/09/21 3:09 PM (ExecTask)         
2/09/21 3:09 PM (ExecTask)         IF MAX_CHANNEL_PER_BLUEPRINT_EXISTS != 1 THEN
2/09/21 3:09 PM (ExecTask)             SELECT COUNT(*) INTO MAX_COUNT FROM cmn_gov_limits;
2/09/21 3:09 PM (ExecTask)             
2/09/21 3:09 PM (ExecTask)             insert into CMN_GOV_LIMITS( id, name, code, description, active, def_limit, critical_limit, current_limit, created_date, created_by, last_updated_date, last_updated_by )
2/09/21 3:09 PM (ExecTask)             values( MAX_COUNT + 1, 'Channels Max Per Blueprint Instance', 'MAX_CHANNEL_PER_BLUEPRINT','Maximum number of channels per blueprint instance', 1, 15 ,15 ,15 , sysdate, 1, sysdate, 1 );
2/09/21 3:09 PM (ExecTask)         END IF;
2/09/21 3:09 PM (ExecTask)     END;
2/09/21 3:09 PM (ExecTask)     
2/09/21 3:09 PM (ExecTask)   
2/09/21 3:09 PM (ExecTask) 
2/09/21 3:09 PM (ExecTask) com.ca.clarity.jdbc.oraclebase.ddc: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-06550: line 2, column 9:
2/09/21 3:09 PM (ExecTask) PLS-00114: identifier 'MAX_CHANNEL_PER_BLUEPRINT_EXIS' too long
2/09/21 3:09 PM (ExecTask) ORA-06550: line 5, column 30:
2/09/21 3:09 PM (ExecTask) PL/SQL: ORA-00972: identifier is too long
2/09/21 3:09 PM (ExecTask) ORA-06550: line 5, column 9:
2/09/21 3:09 PM (ExecTask) PL/SQL: SQL Statement ignored
2/09/21 3:09 PM (ExecTask) ORA-06550: line 7, column 12:
2/09/21 3:09 PM (ExecTask) PLS-00114: identifier 'MAX_CHANNEL_PER_BLUEPRINT_EXIS' too long
2/09/21 3:09 PM (ExecTask) 
2/09/21 3:09 PM (ExecTask)  at com.ca.clarity.jdbc.oraclebase.dder.l(Unknown Source)
2/09/21 3:09 PM (ExecTask)  at com.ca.clarity.jdbc.oraclebase.dder.a(Unknown Source)

Cause

The upgrade was being was being attempted using Oracle 12.1.0.2

Environment

Release : 15.8.1,15.9, 15.9.1

Component : CA PPM APPLICATION

Resolution

  • You are hitting a hard limit for identifiers in Oracle 12.1.0.2 of 30 characters. This limit was increased to 128 characters 12.2.0.1 as per the following thread:

    https://oracle-base.com/articles/12c/long-identifiers-12cr2

  • Upgrade Oracle 12.1 to supported database version mentioned in our documentation.

 

If you are already on Oracle 12.2, ensure the compatibility level is set to 12.2 and restart the upgrade