our institution is using SungardHE Banner with ODS 3.1. recently we upgraded to the latest version of the ODS(3.1). when i recreated several MFDs in Developer Studio 5.3 and ran reports, the reports returned 0 rows. I replaced the MFD with the MFD in effect prior to the upgrade the report returns data. I did rewrite(totally) the report using the newly created MFD and it ran successfully. with many, many reports in production this is not an option.
We are using WF 5.3.3 with Apache 2.0.48/Tomcat 4.1 on HPUX 11.0.
does anyone have any thoughts on what may be causing this and how we get existing reports to recognize/utilize the newly created MFDs?
thanks.

Boy, Patti, that is a puzzler. I don't know anything about Sungard but since it is an upgraded ODS, it is possible that it is using a later version of whatever the underlying data base is? Have you tried going to the Web Console for WebFOCUS and checking the adapter? Have you tried re-creating the masters from the console instead of Dev. Studio.

And, finally, if the old masters work, why are you re-creating them?

Just a couple of ideas............. Good luck!

Patti, have you compared the old and new masters? When we migrated from FOCUS for HP-UX (Unix) to WebFOCUS (Linux) we found that the master generator was treating fields diffently. For example, a field that was describe in Oracle as a NUMBER(5) was generated with an I5 format and I4 internal in FOCUS but the WebFocus generator defined the same field with a P6 format and P3 internal. That will cause problems with JOIN.

Thanks for the responses. It is indeed related to MFD generation. Several of the fields in the warehouse have extremely long lengths. During synonym creation those fields are intrepreted as TX format with a truncated length of 50. I modifed those fields to A50 and the reports are working correctly. I am told that we will be much happier after moving to 7.x. I am hoping this problem will be resolved also.

You will be happier after upgrading. Manually editing relational masters is not a good thing. If your ODS sits on top of SQL Server, you probably had to do quite a bit. We did. After upgrading and switching to the native SQL Server driver and 7.6, we didn't have to modify any.

However, I would suggest that you read the Data Adminstration manual for your platform and data source. There are lots of engine commands that you can put in your edasprof to control the way that synonyms are created. When you get to 7.6, you will most definitely want to look at the VARCHAR one.