wmsorrell
Member
Good Morning,
we are currently in the process of upgrading to EO 8.10 and I wanted to make people aware of some of the issues we are seeing, hopefully I can prevent some other people fro hitting the same brick wall we hit.
First issue - Table conversions. During the YC process we ran into several table conversion errors, which seemed to die for no reson. Unfortunately there were valid logs to look for so PS wasn't much help. It seemd that if we ran the TC again it would get through more, but the F42199 would convert. What do you know I ran it on the deployment server and it ran perfectly. Well that is after I copied the spec from the planner path code to the PY pathcode (not documented, but instructed by PS)
Well on to the UNICODE conversion. If you read through the upgrade manual it mentions deleting 88 and 89 files before running the conversion. DO NOT DELETE THEM!!!!!! Unfortunately there are 235 BSFN't that still reference them in the include file. If you remove them the server build will not complete. We had to re-add them in order to get our server build to work.
Save location - If you plan on using it, be sure to load ESU PG398 otherwise you will not be able to see the save location eventhough it exists.
Debug errors - We are seeing a lot of errors in our debugs "Right Character Data Truncation" and "Invalid Cursor" After sending oodles of ODBC traces and logs to bot IBM and PS, they are looking into it, but they continue to blame each other, so if we ever see a resolution it will be surprising.
Client Access level (CWBODBC.Dll) we were finding several of our custom versions with processing options were corrupt (greek characters) Well it seems if you use client access V5R2 and your version of CWBODBC.dll is 9.0.8.0 you get this corruption. Be sure to upgrade to 9.0.8.1. Unfortunately we had a lot of cleanup because of this.
Misc errors - We have several calls in to PS about programs not working as designed, or changed in EO 8.10 tha tjust don't make sense so I will post up more info as I see it come along. There is also an issue with task views that if you put a value in the country code for a custom task you will run into problems with them not showing up. We has a call open on that as well.
Please feel free to add to this list, I would like to keep it alive for all the people moving to 8.10
Bill
we are currently in the process of upgrading to EO 8.10 and I wanted to make people aware of some of the issues we are seeing, hopefully I can prevent some other people fro hitting the same brick wall we hit.
First issue - Table conversions. During the YC process we ran into several table conversion errors, which seemed to die for no reson. Unfortunately there were valid logs to look for so PS wasn't much help. It seemd that if we ran the TC again it would get through more, but the F42199 would convert. What do you know I ran it on the deployment server and it ran perfectly. Well that is after I copied the spec from the planner path code to the PY pathcode (not documented, but instructed by PS)
Well on to the UNICODE conversion. If you read through the upgrade manual it mentions deleting 88 and 89 files before running the conversion. DO NOT DELETE THEM!!!!!! Unfortunately there are 235 BSFN't that still reference them in the include file. If you remove them the server build will not complete. We had to re-add them in order to get our server build to work.
Save location - If you plan on using it, be sure to load ESU PG398 otherwise you will not be able to see the save location eventhough it exists.
Debug errors - We are seeing a lot of errors in our debugs "Right Character Data Truncation" and "Invalid Cursor" After sending oodles of ODBC traces and logs to bot IBM and PS, they are looking into it, but they continue to blame each other, so if we ever see a resolution it will be surprising.
Client Access level (CWBODBC.Dll) we were finding several of our custom versions with processing options were corrupt (greek characters) Well it seems if you use client access V5R2 and your version of CWBODBC.dll is 9.0.8.0 you get this corruption. Be sure to upgrade to 9.0.8.1. Unfortunately we had a lot of cleanup because of this.
Misc errors - We have several calls in to PS about programs not working as designed, or changed in EO 8.10 tha tjust don't make sense so I will post up more info as I see it come along. There is also an issue with task views that if you put a value in the country code for a custom task you will run into problems with them not showing up. We has a call open on that as well.
Please feel free to add to this list, I would like to keep it alive for all the people moving to 8.10
Bill