Clarity PPM1

Expand all | Collapse all

"Time Slicing Job" is failing constantly

Jump to Best Answer
  • 1.  "Time Slicing Job" is failing constantly

    Posted 01-19-2017 11:40 AM

    Hi all,

     

     

    Does any one has any idea about this issue? Also is it related with resource related reports? Where can I start to dig?

     

    I have check PRJ_BLB_SLICE_RESET_ALL_SP and does not have a sub query. 

     

    Regards

     

    ERROR 2017-01-18 08:28:15,108 [Dispatch Time Slicing : bg@S0134CAAPP01 (tenant=clarity)] niku.njs (clarity:admin:5644473__5369318E-9BE3-4519-BEBC-23528CFD2CBE:Time Slicing) Error executing job: 1030 error The timeslice job has failed.
    ERROR 2017-01-18 08:29:15,614 [Dispatch Time Slicing : bg@S0134CAAPP01 (tenant=clarity)] niku.blobcrack (clarity:admin:5644476__AFB37282-4E11-472C-B3D2-684F200B4606:Time Slicing) Exception during blobcrack process
    com.niku.union.persistence.PersistenceException:
    SQL error code: 512
    Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
    SQL error code: 3621
    Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer]The statement has been terminated.
    Executed:
    {call PRJ_BLB_SLICE_RESET_ALL_SP(?,?)}
    Derived from statement:
    <?xml version="1.0" encoding="UTF-8"?>
    <statement sortColumnPath="/data/header/sortInfo/@sortColumn" sortDirectionPath="/data/header/sortInfo/@sortDirection" slicePath="/data/header/pagination/sliceInfo/@slice" sliceSizePath="/data/header/pagination/sliceInfo/@sliceSize" inputSource="map" xmlns="http://schemas.niku.com/2002/pmd">
    <sql dbVendor="all">
    <text>
    {call PRJ_BLB_SLICE_RESET_ALL_SP(?,?)}
    </text>
    <param type="string" direction="IN" constantValue="PRJ_RESOURCES" expressionListDelimiter=","/>
    <param name="sliceStatusFlag" type="int" direction="IN" expressionListDelimiter=","/>
    </sql>
    </statement>

    Referenced by:
    <?xml version="1.0" encoding="UTF-8"?>
    <statementRef id="blobcrack.setAllResourcesModified_set_nested_0" inputSource="map" inputMapIndex="0" sortColumnPath="/data/header/sortInfo/@sortColumn" sortDirectionPath="/data/header/sortInfo/@sortDirection" slicePath="/data/header/pagination/sliceInfo/@slice" sliceSizePath="/data/header/pagination/sliceInfo/@sliceSize" defaultSliceSize="20" ignoreIfError="false" hideResultSets="false" xmlns="http://schemas.niku.com/2002/pmd"/>

    Using input:
    {sliceStatusFlag=3, parameters=[int:sliceStatusFlag:3:]}

    at com.niku.union.persistence.PersistenceController.createException(PersistenceController.java:2085)
    at com.niku.union.persistence.PersistenceController.handleSQLException(PersistenceController.java:2189)
    at com.niku.union.persistence.PersistenceController.processSql(PersistenceController.java:2823)
    at com.niku.union.persistence.PersistenceController.processStatement(PersistenceController.java:869)
    at com.niku.union.persistence.PersistenceController.processStatements(PersistenceController.java:769)
    at com.niku.union.persistence.PersistenceController.doProcessRequest(PersistenceController.java:577)
    at com.niku.union.persistence.PersistenceController.processRequest(PersistenceController.java:307)
    at com.niku.xql2.pmd.PMDDataSource.execute(PMDDataSource.java:213)
    at com.niku.blobcrack.BlobCrackDB.resetRequest(BlobCrackDB.java:306)
    at com.niku.blobcrack.BlobCrackDB.resetRequests(BlobCrackDB.java:336)
    at com.niku.blobcrack.BlobCrackDB.prepareSliceStatus(BlobCrackDB.java:1996)
    at com.niku.blobcrack.BlobCrackDB.sliceCurves(BlobCrackDB.java:1720)
    at com.niku.blobcrack.BlobCrackDB.createSlices(BlobCrackDB.java:1252)
    at com.niku.blobcrack.xql2.handlers.BlobCracker.processExpiredRequests(BlobCracker.java:233)
    at com.niku.blobcrack.xql2.handlers.BlobCracker.postProcess(BlobCracker.java:45)
    ...
    at java.lang.Thread.run(Thread.java:745)
    Caused by: java.sql.SQLException: [CA Clarity][SQLServer JDBC Driver][SQLServer]Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
    at com.ca.clarity.jdbc.sqlserverbase.ddcw.b(Unknown Source)
    ...
    at com.niku.union.persistence.PersistenceController.processSql(PersistenceController.java:2796)
    ... 31 more



  • 2.  Re: "Time Slicing Job" is failing constantly
    Best Answer

    Posted 01-19-2017 11:55 AM

    Hi - you don't need to keep reposting the same question (this is the third time in 3 days I think?).

     

    If your problem is urgent, then opening a support call will get better engagement than you are getting on here.

     

    --

     

    If the problem is in a custom database trigger than is firing on update of PRJ_RESOURCES then that might be being triggered by the code in PRJ_BLB_SLICE_RESET_ALL_SP - hence the error message, but obviously I am GUESSing since I can not see your database and any local customisations you may have. If your problem is due to a customisation then support might not be able to help either. (Obviously if you have a customisation then you are responsible for supporting it).



  • 3.  Re: "Time Slicing Job" is failing constantly

    Posted 01-19-2017 12:21 PM

    You are right on reporting may be a little bit boring for some of you. 2 of them are only to give extra info about the issue, and the last one is to distinguish between the with the explanation about LDAP.

     

    Any way you are right. Sorry for this.

     

    And thank you your helpful reply...

     

    Regards



  • 4.  Re: "Time Slicing Job" is failing constantly

    Posted 01-19-2017 01:11 PM

    I do not want to sound harsh - the problem with multiple questions asking the same thing is that the "conversation" gets confusing and no-one can tell what the latest position on the problem is nor whether a problem is fixed or not!

     

    So is your problem fixed? If so, what was the answer? - (adding this sort of information may be useful to someone in the future)



  • 5.  Re: "Time Slicing Job" is failing constantly

    Posted 01-20-2017 07:02 AM

    I can understand you.

     

    My problem is also ok by disabling the trigger.

     

    Regards.



  • 6.  Re: "Time Slicing Job" is failing constantly

    Posted 01-20-2017 07:32 AM

    ^ ah good - thanks for letting us know!