Any experiences of SAP R/3 customers using Informix 7.30 ?

Mario, whoever did that 7.3 class book probably misstated what is known about 7.3 upgrades with outstanding in-place alters. I.e., there are no known problems with outstanding alter tables when an upgrade from 7.2x to 7.3x is performed (at least no problems entered for this in any bug/problem database known to me). It is true though, that after an upgrade to 7.3 you cannot revert to any 7.2x version if there are any outstanding alter table commands. As long as you plan to stay on 7.3, there is no need to issue any dummy update commands. It would be nice to get the exact title of the book you are referring to, though. Heiko ------------ all standard disclaimers apply --------------- MOPSOMER@raychem.com wrote: > We are currently considering to upgrade all our SAP R/3 environments > from Informix 7.24.UC3 to 7.30.UC5. We run all systems on Solaris > (some on Solaris release 2.5.1, others already on Solaris 2.6). > > Are there amongst you SAP customers who already upgraded to 7.30 ? > Did you have problems (bugs) during or after the upgrade which were > caused by the new Informix release ? Did you encounter performance > issues or was SAP performance improved by the upgrade ? I did not > get any feedback from SAP regarding the findings of SAP customers who > participated in the 7.30 FPC program (First Productive Customer). > > I recently followed the "Informix 7.30 new features" course. The book > used in that 7.30 course mentions the following worrying sentence : > > "Any upgrade to 7.3 will fail if there are outstanding in-place alter > for a table. The only way to get around this is to perform a dummy > update on the table so as to force all pages to conform to the latest > version. Use oncheck -pT to obtain the version information." > > => Is the previous statement true - has anyone got such problems? > > I already checked a couple of big SAP tables (> 10 GB) and some of > these indeed contain pages/rows of different versions (we recently did > an SAP R/3 upgrade from 3.0D to 4.0B). If above statement is really > true, I have to plan a lot of SAP R/3 downtime in the coming weeks for > doing all these "dummy updates", before I can start with the Informix > upgrades. I can't do these "dummy updates" while SAP is available as > I probably need to go in NOLOGGING mode (to avoid long transaction > aborts). Even if we could stay in the normal UNBUFFERED LOGGING mode, > we would probably have to stop the SAP application anyway to avoid > Informix locking issues during the "dummy updates" on big tables. > > Kind regards, > Mario Opsomer > Raychem N.V.

We are currently considering to upgrade all our SAP R/3 environments from Informix 7.24.UC3 to 7.30.UC5. We run all systems on Solaris (some on Solaris release 2.5.1, others already on Solaris 2.6). Are there amongst you SAP customers who already upgraded to 7.30 ? Did you have problems (bugs) during or after the upgrade which were caused by the new Informix release ? Did you encounter performance issues or was SAP performance improved by the upgrade ? I did not get any feedback from SAP regarding the findings of SAP customers who participated in the 7.30 FPC program (First Productive Customer). I recently followed the "Informix 7.30 new features" course. The book used in that 7.30 course mentions the following worrying sentence : "Any upgrade to 7.3 will fail if there are outstanding in-place alter for a table. The only way to get around this is to perform a dummy update on the table so as to force all pages to conform to the latest version. Use oncheck -pT to obtain the version information." => Is the previous statement true - has anyone got such problems? I already checked a couple of big SAP tables (> 10 GB) and some of these indeed contain pages/rows of different versions (we recently did an SAP R/3 upgrade from 3.0D to 4.0B). If above statement is really true, I have to plan a lot of SAP R/3 downtime in the coming weeks for doing all these "dummy updates", before I can start with the Informix upgrades. I can't do these "dummy updates" while SAP is available as I probably need to go in NOLOGGING mode (to avoid long transaction aborts). Even if we could stay in the normal UNBUFFERED LOGGING mode, we would probably have to stop the SAP application anyway to avoid Informix locking issues during the "dummy updates" on big tables. Kind regards, Mario Opsomer Raychem N.V.