Clarity

Expand all | Collapse all

Upgrade Clarity 13.3 to Clarity 15.3

Jump to Best Answer
  • 1.  Upgrade Clarity 13.3 to Clarity 15.3

    Posted 09-27-2017 08:07 AM

    Hi All,

     

    According to Upgrade Docs, one of the steps needed for our upgrade (from Clarity 13.3 -> 15.3), it's needed patch 14:

    Supported Patch Level for Upgrade
    Upgrade Patch Level ExceptionsHow to Download and Install the Patch
    Patch 13.3.0.14 on the base version 13.3.0NoneSee the CA Support Download Center.

    After downloaded and tried to install, we got errors (attached is full log). There are a lot of "java" errors don't know how they can be fixed, furthermore I've just 2 errors regarding DB:

     

    - one with DB Driver:

    9/27/17 9:05 AM (ExecTask) Loading DBDriver file: /home/clarity/niku/clarity/maintenance/database/schema/driver.xml
    9/27/17 9:05 AM (ExecTask) Current database version is database_20131128_0809
    9/27/17 9:05 AM (ExecTask) DBDriver for database_20151008_0600
    9/27/17 9:05 AM (ExecTask) Start installation of DBDriver ...
    9/27/17 9:05 AM (ExecTask) Note: Foreign Keys have been disabled
    9/27/17 9:05 AM (ExecTask) DBDriver failed to install!

     

    Q: How was this file created? Why there are tables, views and procedures and this date? (file is attached). 

    I suppose that file including other files under /maintenance folder were created during Patch 14 installation...

     

    - second with our custom DB trigger which is currently Disabled:

    9/27/17 9:05 AM (ExecTask) Exception in thread "main" java.lang.Exception: DBDriver failed to install
    9/27/17 9:05 AM (ExecTask) at com.niku.dbtools.DriverApp.installSchemaDriver(DriverApp.java:908)
    9/27/17 9:05 AM (ExecTask) at com.niku.dbtools.Utilities.run(Utilities.java:1836)
    9/27/17 9:05 AM (ExecTask) at com.niku.dbtools.Utilities.main(Utilities.java:954)
    9/27/17 9:05 AM (ExecTask) Caused by: java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-20000: Error: ORA-04080: trigger 'Z_HEN_ARCFIT_BPM_FLAG_OLD' does not exist
    9/27/17 9:05 AM (ExecTask) ORA-06512: at "NIKU.CMN_ENABLE_DISABLE_SP", line 67
    9/27/17 9:05 AM (ExecTask) ORA-06512: at line 1

     

    Q: How can it be caused by trigger 'Z_HEN_ARCFIT_BPM_FLAG_OLD' when it's Disabled? 

     

    Example of other java errors:

    9/27/17 9:05 AM (ExecTask) /home/clarity/niku/clarity/.setup/scripts/db.xml:1652: The following error occurred while executing this line:
    9/27/17 9:05 AM (ExecTask) /home/clarity/niku/clarity/.setup/scripts/db.xml:1789: The following error occurred while executing this line:
    9/27/17 9:05 AM (ExecTask) /home/clarity/niku/clarity/.setup/scripts/db.xml:527: The following error occurred while executing this line:
    9/27/17 9:05 AM (ExecTask) /home/clarity/niku/clarity/.setup/scripts/db.macros.xml:44: Java returned: 1
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:551)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:444)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
    9/27/17 9:05 AM (ExecTask) at com.niku.tools.taskdefs.xpath.Iter.executeTarget(Iter.java:294)
    9/27/17 9:05 AM (ExecTask) at com.niku.tools.taskdefs.xpath.Iter.execute(Iter.java:189)
    9/27/17 9:05 AM (ExecTask) at com.niku.tools.taskdefs.xpath.Iter.execute(Iter.java:145)
    9/27/17 9:05 AM (ExecTask) at com.niku.tools.taskdefs.XPath.execute(XPath.java:419)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
    9/27/17 9:05 AM (ExecTask) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
    9/27/17 9:05 AM (ExecTask) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    9/27/17 9:05 AM (ExecTask) at java.lang.reflect.Method.invoke(Method.java:606)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.Task.perform(Task.java:348)
    9/27/17 9:05 AM (ExecTask) at com.niku.tools.taskdefs.IfTask.execute(IfTask.java:219)
    9/27/17 9:05 AM (ExecTask) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
    9/27/17 9:05 AM (ExecTask) at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
    9/27/17 9:05 AM (ExecTask) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja

     

    Any help from the experts would be very appreciated. 

    Thanks

    Matej

    Attachment(s)

    zip
    install.log.zip   15K 1 version
    zip
    driver.xml.zip   614B 1 version


  • 2.  Re: Upgrade Clarity 13.3 to Clarity 15.3
    Best Answer

    Posted 09-29-2017 03:40 AM

    Hi, 

     

    I was able to resolve this by myself. It was just simple thought: it was enough to just delete mentioned trigger above and installation ended successfully.

     

    Matej



  • 3.  Re: Upgrade Clarity 13.3 to Clarity 15.3

    Posted 09-29-2017 10:03 AM

    Glad to hear that.

    I thought it was in the Change and Impact guide to delete all customizations, it is not.

    is from the "Joy" of upgrading webinar on June 15.

     

    Can't argue with a vanilla system being easier to upgrade, but then the head ache is finding all the customizations, removing them and finally reapplying (it that still can be done).



  • 4.  Re: Upgrade Clarity 13.3 to Clarity 15.3

    Posted 10-21-2017 03:29 PM

    That information is in the documentation after all (if you know how to look for that)

    CA PPM Installation Guide 14.1 - 15.3

    Disable any custom database triggers, custom unique restraints, or antivirus
    scanners that can interfere with the installation scripts.

     

    CA PPM Change Impact and Upgrade (Guide) 14.2 - 15.3

    3. Remove customer-added database triggers, stored procedures, indexes, views, and
    constraints before upgrading.
    Important! Due to the database schema changes for this release, most custom
    triggers, indexes, and constraints can cause the upgrade to fail. We recommend
    removing, not disabling, customer-added triggers.