2 of 2 people found this helpful
First thing you need to do is run arserver in -checkdb mode. it checks database consistency (validates all metadata tables and generate report)
It will provide you required information on what is incorrect and what needs to be corrected. meanwhile open ticket with BMC if you or your dba is not confident about how to fix such errors. these errors may crash your remedy server. so be careful.
After getting another set of eyes on this it turns out that Remedy had created a different view name for the form where it appended an integer and this newer view has the correct field information. I find it odd that importing the form definition brought in this baggage (which exists on the old system). The correct view has a different schema ID as well. Apparently this is a very old bug in AR System (like back to version 6) where if you have duplicate view names in the form it can cause this wackiness at the database tier.
An example is a form named IT24hr:ProductionChangeRequest where the expected database view name in Oracle is IT24HR_PRODUCTIONCHANGEREQUEST but that view had incorrect field data. However there is an Oracle view named IT24HR_PRODUCTIONCHANGEREQ3791 which has the correct field data. 3791 is the schema ID of the form while the bogus DB view is using T3798 which surprisingly exists also.