I would start by doing a describe on the database table v2_MASRLineItemTab directly to see what columns are defined. The task sees database level fields / tables that have built up historically through the various versions of Ariba and various customizations even if they are not used anymore within the application or visible. You may be able to see what data is stored in those fields. I would also compare to another instance of Ariba to see if one of the columns is not needed and can be dropped.................but I would make sure I have a backup of the DB beforehand.
Thanks very much for your suggestions. They worked great and we were able to delete the offending records and get through the task harness successfully. Thanks again for your help and quick response!
This happens when duplicate columns exits in the migratemetadatatab.
You can run the attached query to find out all such occurrences:
select distinct m1.tablename, m1.columnname, m1.parenttablename, m1.parentcolumnname, m1.fieldname
from metalayouttab m1,
(select count(*), fieldname, tablename, parentcolumnname
from MetaLayoutTab where fieldname is not null
group by fieldname, tablename, parentcolumnname
having count(*)>1) m2
where m1.fieldname = m2.fieldname
and m1.tablename = m2.tablename
and nvl(m1.parentcolumnname,' ') = nvl(m2.parentcolumnname,' ')
order by m1.tablename, m1.columnname
Once you figure out all the duplicates then you have to manually go into those tables to check which column is obsolete by checking for null data and have to delete them from the migratemetadatatab.
Let me know in case you have any further queries.
Sorry for the delay in responding, but your help/guidance was very helpful to our team in figuring out the root cause.