Skip to end of metadata
Go to start of metadata

Problem

Whenever a Date Interval is created and this date interval has date attributes as <Start> and/or <End> assigned, it might happen that iteraplan does no longer respond and an error appears. This is only the case when the date attributes are not activated for the same Building Block Types as the Date Interval itself. 

Solution

You can use the following SQL statements to fix the problem

MySQL
UPDATE ATTR SET LAST_MOD_USER='-', LAST_MOD_TIME='2000-01-01 00:00:00' WHERE LAST_MOD_USER is NULL or LAST_MOD_TIME is NULL; 
Oracle
UPDATE "ATTR" SET LAST_MOD_USER = '-', LAST_MOD_TIME = TO_TIMESTAMP('2000-01-01 00:00:00.000000000', 'YYYY-MM-DD HH24:MI:SS.FF') WHERE LAST_MOD_TIME is NULL or LAST_MOD_USER is NULL;
MS SQL
UPDATE ATTR SET LAST_MOD_USER='-', LAST_MOD_TIME='2000-01-01 00:00:00' WHERE LAST_MOD_USER is NULL or LAST_MOD_TIME is NULL;


When iteraplan is running again, please check if the <End> date attribute of the Date Interval was set.