Clarity PPM1

Expand all | Collapse all

Error running XOG

Jump to Best Answer
  • 1.  Error running XOG

    Posted 11-06-2017 10:11 AM

    Hello everybody!

    I try to extract the mapping code with XOG Client  from non-production environment. This mapping code help us to convert the idea to other work, but when I try to execute to xml on XOG Client, the browser show me a error, and I don´t know referred to. 

    The sintaxys is: 

     

    <?xml version="1.0" encoding="UTF-8"?>
    <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_read.xsd">
    <Header version="8.0" action="read" objectType="contentPack" externalSource="NIKU">
    <!-- the contentType is used to determine which filter goes where -->
    <args contentType="job_definition" name="order_by_1" value="code"/>
    <args contentType="menu" name="order_by_1" value="code"/>
    <args contentType="view" name="order_by_1" value="code"/>
    <args contentType="process" name="order_by_1" value="code"/>
    <args contentType="object" name="order_by_1" value="code"/>
    </Header>
    <ObjectMappingQuery>
    <Filter name="mappingCode" criteria="EQUALS">pac_map_idea_other</Filter>
    </ObjectMappingQuery>
    </NikuDataBus>

     

    And error message is: 

     

    <XOGOutput>
    <Object type="contentPack"/>
    <Status state="SUCCESS"/>
    <Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="385" updatedRecords="0"/>
    <Records>
    <Record>
    <KeyInformation/>
    <ErrorInformation>
    <Severity>FATAL</Severity>
    <Description>XOG-3370: Failed to export object mapping.</Description>
    <Exception><![CDATA[SQL Exception with error code : 0]]></Exception>
    </ErrorInformation>
    </Record>
    </Records>
    </XOGOutput>

     

    What could have happened?

    Regards, 

     

    Saulo



  • 2.  Re: Error running XOG
    Best Answer

    Posted 11-06-2017 10:57 AM

    Can you check if this is the cause?

     

    XOG fails when migrating Custom Objects from one environment into another environment

    https://support.ca.com/us/knowledge-base-articles.tec1459218.html  

     

     

    Document ID:  TEC1459218
    Last Modified Date:  10/02/2015

     

     

    Problem:

    When migrating custom object instances from one environment to another, XML Open Gateway (XOG) updates some parts of the Sql query and adds single quotes which caused XOG to fail.

    Steps to Reproduce:

    1. Create a custom object
    2. Create a lookup type custom attribute on above object
    3. Add the above custom attribute into create and edit views
    4. Create an instance for above custom object
    5. Give the custom attribute value as "test'test", add a single quote in the string
    6. XOG out the custom object instance
    7. XOG in same custom object instance without any change in the XOG file 

    Expected Result: Custom attribute value should be "test'test"

    Actual Result: Custom attribute value is "test''test", getting extra single quote for the attribute  

    Environment:

    Applies to all supported PAS environments for the specified releases. 

    Cause:

    Caused by CLRT-78427

    Resolution:

    Resolved in CA PPM 14.2 Generic Patch #5

    Resolved in CA PPM 14.3

     

     

    NJ



  • 3.  Re: Error running XOG

    Posted 11-06-2017 12:43 PM

    Could you please check the app-ca logs to see if the XOG operation produced an error at this time (and maybe also gave more details about the query that failed)?

     

    I have only (but recently) seen this one time previously, and it happened to be with a customer that had added custom attributes to the portfolio object back before portfolio management was re-written in 13.2 and up.  Part of the current XOG entity read code around OBS permissions can fail against it with the SQL Exception code 0 but I very much doubt it is going to regularly be that and more likely to have additional causes too.

     

    If there are no outputs to reference in the app-ca log then you will probably want to open a support ticket to check further, if you have entitlement to do so.