Clarity

  • 1.  XOG transactions failing

    Posted Oct 16, 2017 10:38 AM

     

    Hi, I am trying to xog in transactions and getting below error..

     

    <ErrorInformation>
    <Severity>FATAL</Severity>
    <Description>Inbound Transaction Object Insert failed</Description>
    <Exception><![CDATA[
    java.sql.SQLIntegrityConstraintViolationException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into ("CLARITYPPM"."IMP_TRANSACTIONIMPORT"."TRANSIMPORTKEY")

    at com.ca.clarity.jdbc.oraclebase.ddcr.b(Unknown Source)
    at com.ca.clarity.jdbc.oraclebase.ddcr.a(Unknown Source)
    at com.ca.clarity.jdbc.oraclebase.ddcq.b(Unknown Source)
    at com.ca.clarity.jdbc.oraclebase.ddcq.a(Unknown Source)

     

    Any idea how to fix this?

     

    Regards,

    Deepak



  • 2.  Re: XOG transactions failing

    Posted Oct 16, 2017 11:02 AM

    Check this:

     

    XOG transactions failing 

    https://communities.ca.com/message/241839033 

     

    NJ



  • 3.  Re: XOG transactions failing

    Posted Oct 16, 2017 11:05 AM

    Thanks NJ for post..

     

    Error i am facing is somewhat different then that of post..  

     

    Error is :- 

     

    <ErrorInformation>
    <Severity>FATAL</Severity>
    <Description>Inbound Transaction Object Insert failed</Description>
    <Exception><![CDATA[
    java.sql.SQLIntegrityConstraintViolationException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01400: cannot insert NULL into ("CLARITYPPM"."IMP_TRANSACTIONIMPORT"."TRANSIMPORTKEY")



  • 4.  Re: XOG transactions failing

    Posted Oct 16, 2017 01:06 PM

    How to XOG-in project subPage This thread might help. Same error.

     

    Could it be that something is missing in your XOG file?



  • 5.  Re: XOG transactions failing
    Best Answer

    Broadcom Employee
    Posted Oct 16, 2017 06:02 PM

    I worked on this issue together with Deepak and found the root cause.

    The problem was not only when creating the transactions by XOG, but also via timesheets.

     

    Turned out that the trigger IMP_TRANSACTIONIMPORT_TR was missing on the environment after a refresh. I suggested redoing the refresh to make sure no other objects are missing, and this resolved the issue.