Clarity

Clarity 14.4 on oracle 12.1

When attempting to load the csk content, the script is generating several error messages when it tries to import the inv.xml file :

Applying objects/inv.xml

9/7/16 5:30 PM (admin) ERROR 07-09 17:30:10,880 - PortfolioInvestmentObject: error updating schema: com.niku.union.persisten

ce.PersistenceException:

9/7/16 5:30 PM (admin) SQL error code: 22859

9/7/16 5:30 PM (admin) Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-22859: Ungültige Änderung von Spalten

9/7/16 5:30 PM (admin) Executed:

9/7/16 5:30 PM (admin)  ALTER TABLE PFM_BASELINE_DETAILS MODIFY PREXTENSION BLOB

Loading the content on a copy on Oracle 11.2.0.4 doesn’t give any problem.

Anyone knows what’s the difference in Oracle version that could cause this behavior ?

Hi Frank,

interessting issue, I have just received a practically identical support request  from one of our customers :-)

The PFM_BASELINE_DETAILS table was added in CA PPM 13.2. Do you attempt to upgrade from 13.2 directly to 14.4? 

Can you upload the complete log file?

You could go through with the upgrade using Oracle 11.2.0.4 and switch to 12.1.0.2 after the upgrade is completed.

Kind Regards,

Sergiu Gavrila

Small update, after looking further into this issue:

"ALTER TABLE PFM_BASELINE_DETAILS MODIFY PREXTENSION BLOB" attempts to change the type of the PREXTENSION column to BLOB.

But the type of the PREXTENSION is already BLOB and Oracle does not allows changing BLOB columns over ALTER (you have to create a new column, transfer the content, delete the old column, rename new column).

This statement is failing with Oracle 12.1.0.2 AND also with Oracle 11.2.0.4 (SQL-Plus). 

What do you mean with "Loading the content on a copy on Oracle 11.2.0.4 doesn’t give any problem." ?

You have succesfully applied the csk content (admin content csk) on the same DB dump, after importing it in a 11.2 db?

Regards,

Sergiu

I have just received an analysis and workaround for this issue from CA:

The error only occurs on Oracle 12.1.0.2 when BLOB fields are stored separately outside the table rows: “DISABLE STORAGE IN ROW”.

In this case the field DATA_LENGTH of the view ALL_TAB_COLUMS  shows a number different than 4000 for BLOB fields.

As clarity is using this table to compare tables (for consistency checks when changing the INV_INVESTMENTS object) the check fails and the exception is occurring.

In Oracle Version 11.2.0.4 the view ALL_TAB_COLUMS shows a size of 4000 for all BLOB fields independent whether they are stored in row or not.

As the DATA_LENGTH field of the view ALL_TAB_COLUMS  does not make much sense for BLOB fields (according to the Oracle DB administrators), the consistency check should ignore the DATA_LENGTH for BLOB fields.

Additional problem on Oracle 12.1.0.2.0

The load of the csk content is hanging at the driver.xml script.

It seems that the script for creating the COP_USR_ACCESS_RIGHTS_V.xml is hanging because the size is more than 32k.  Reducing the file to less than 32k, makes the script to run successfully.