AnsweredAssumed Answered

Datamart job failing now...

Question asked by TomConnery on Jun 26, 2008
Latest reply on Jul 1, 2008 by TomConnery
Our original entity setup was deleted and now datamart jobs fail every night. Please see below.. +++  Datamart is failing - what error? - manual or immediate datamart jobs won't run at all.  The error during the scheduled datamart job returns the output below on its failure. com.niku.union.persistence.PersistenceException: SQL error code: 50000 Error message: [CA Clarity][SQLServer JDBC  Driver][SQLServer]NBI_CFG_NO_FISCAL_PERIOD - No fiscal periods have been set up SQL error code: 50000 Error message: [CA Clarity][SQLServer JDBC Driver][SQLServer] Executed:  {call nbi_extract_sp()} Derived from statement: sortColumnPath="/data/header/sortInfo/@sortColumn" sortDirectionPath="/data/header/sortInfo/@sortDirection" slicePath="/data/header/pagination/sliceInfo/@slice" sliceSizePath="/data/header/pagination/sliceInfo/@sliceSize" inputSource="none" xmlns="' target='_blank'>http://schemas.niku.com/2002/pmd">             {call nbi_extract_sp()}        Referenced by: sortColumnPath="/data/header/sortInfo/@sortColumn" sortDirectionPath="/data/header/ ++++     Was it running previously and just stopped? - yes, it was running...  not sure when the last successful one was, the clarity log goes back to June 16th and it's been failing since then.  I'm guessing it's been failing for a couple of months. ++++     Has anything changed in the environment between when it worked and when it did not? (ie - upgraded sql server, installed a fixpack, installed a security patch, etc..) - The Entity "company name" established in the initial install was deleted.  so the entity name in the datamart setting is reflecting an entity that does not exist.  This field is read only once the first datamart extract is run, and cannot be changed. - As ##### stated above, the original financial entity was deleted.  He recreated the entity but it doesn't look like it's helping.  We have applied FP03 recently but I don't think that had anything to do with this issue. ++++     Are other scheduled jobs running without error? - yes

Outcomes