Clarity install.log contains message regarding invalid objects

book

Article ID: 37710

calendar_today

Updated On:

Products

Clarity PPM On Premise

Issue/Introduction

 

Clarity install.log reports few database objects as invalid during Clarity installation:

 This happens only when CA PPM is running on Oracle and the database schema name is not called niku.

 Steps to Reproduce:

  1. Complete an install to CA PPM 14.2 or upgrade from Clarity 14.1 running on Oracle where the Clarity database schema name is not niku.
  2. Once the upgrade/install completes review the install.log
  3. Optional step run the command "admin db compile"

Expected Result: There will be no objects marked as invalid

Actual Result: Following object(s) are invalid, SYS_PLSQL_1345803_89_1, SYS_PLSQL_57128_96_1 and SYS_PLSQL_24528_89_1

 

Cause

This issue is caused by CLRT-77574 and is currently in review with our development team.

Environment

Clarity PPM 14.x,15.x

Resolution

There will always be 3 objects that are invalid as they are used when the Oracle database is imported/refreshed, however it will not cause any issues with Clarity operation.

SYS_PLSQL_24528_89_1
SYS_PLSQL_57128_96_1
SYS_PLSQL_1345803_89_1

This happens only when Clarity is running on Oracle and the database schema name is not called niku.

 

Workaround:

Recreate the objects using the SQL syntax below with the correct schema name, changing from NIKU:

create or replace TYPE "SYS_PLSQL_1345803_89_1" as table of NIKU."SYS_PLSQL_1345803_50_1";

create or replace TYPE "SYS_PLSQL_24528_89_1" as table of NIKU."SYS_PLSQL_24528_50_1";

create or replace TYPE "SYS_PLSQL_57128_96_1" as table of NIKU."SYS_PLSQL_57128_50_1"

Attachments

1558723738800000037710_sktwi1f5rjvs16wzb.png get_app