One comment I have to say…It is fast even on a 1 core VM with 8GB of RAM and two other app servers running on it.
Running EWA,IW, ES, ESE,EMA,EE,DD and Help
2 Likes
Just in case people were interested…
543 objects (147 Tables,395 Stored Procs) with alterations between 10.2.300.14 and 10.2.400.2
11 objects (3 table,1 Views, 7 Storred Procs) in 10.2.300.14 not in10.2.400.2
106 (33 Tables, 1 Function, 72 Stored Procs) new between 10.2.300.14 and 10.2.400.2
3059 Objects (658 Tables,2824 Stored Procs) with alterations between 10.1.600.6 and 10.2.400.2
156 Objects (81 table, 58 Views, 16 Storred Procs,1 FullTextSearchCatalog) in 10.1.600.6 not in 10.2.400.2
491 Objects (190 Tables, 297 Stored Procs,2 Functions,1 Schema (EcF), 1 xmlSchema collection) new between 10.1.600.6 and 10.2.400.2
4 Likes
The HF10.2.400.2.zip file contains 2 Hot Fixes - 115439 and 115583.
115583 should be installed after the Admin Console bits have been installed but before you actually do anything with the Admin Console. It is because of this timing that the installation instructions reference the Hot Fix package where it does even though that timing is too early for the installation of 115439.
115439 should be installed on each AppServer after the AppServer has been created/upgraded and before you run anything that will connect to the AppServer.
1 Like
Thanks for the clarification Rich…After reading the notes for each hot fix and putting 2n2 together that was the case.
I couldn’t find anything in the Release Notes, so, HotFix for ERPS-115583 is PRB0212766: Sessions are not cleared during an upgrade.
A new property was added to the Session Object for 10.2.400. If the old sessions cached to db are read after an upgrade, the error is not handled and the server is destabilized in numerous ways ranging from a simple UI issue in Admin Console Session List to poor performance due to Task Agent getting backlogged due to the corrupt Sessions.
The orphaned Sessions from 300 should be deleted during the upgrade process
The presence of a corrupt Session being deserialized from the db should be handled more gracefully with proper logging and removal from the db if corrupt.
