upgrading 11.70 to 12.10

I want to upgrade 11.70tc3 to 12.10tc2 on a Windows server 2008R2 machine. I did this on my development server by using dbexport and then uninstalling 11.70 and then installing 12.10 and then dbimporting data. (As I recall, the installer would not do an upgrade over the top of the old installation) Would it work if I 1. move the old informixdir someplace 2. install 12.10 with default dbspaces on another disk than the current dbspaces and use same informixdir as before. 3. change the onconfig ROOTPATH and ROOTSIZE to where the data is and any tuning parameters from the old onconfig file. 4. restart ids. The servernum, servicename, servername, and port would be different so connect strings would change. I could rename the server in Instance Manager before the install so could use the same one as before. Are there differences inside the rootspace that would make the installation corrupt? Should I uninstall the old service first and use dbimport as I did on my dev server?

Hi, not very familiar with windows installations, but generally, an inplace upgrade should work on the dbspaces of the 11.70 instance. You should take a full archive before and check the recommended size of physical log, because the conversion usually uses much physical log space. Just backup the old informixdir, make sure all logfiles have been backed up, shutdown old instance. Then install the new version, start new version with same onconfig/sqlhosts file. The conversion should be done automatically and should not be interrupted. Normally, the sysmaster DB is rebuild during the upgrade process. Keep a look at online.log to see what happens. The system will walk through all the tablespaces and convert the structures. In case you want to re-organize your data, dbexport/dbimport could make sense, but is not really necessary. Also, after starting the new instance, execute "update statistics low drop distributions" over all databases and rebuild the distributions with the new binaries using update statistics low/medium/high, as recommended, preferably using the do_stats package from Art Kagel, available in the IIUG repository. Maybe you should copy the instance to a test machine first and try the conversion without interfering production to see if the space requirements are sufficient and the conversion really succeeds. There is a conversion guide somewhere in the docs of IBM. Also, check if the values of system parameters have changed (release notes for your platform). Hope this helps. Marcus Haarmann ----- Ursprüngliche Mail ----- Von: "BillHatVerizon" <garage_dba@verizon.net> An: ids@iiug.org Gesendet: Montag, 24. Februar 2014 19:46:32 Betreff: upgrading 11.70 to 12.10 [32590] I want to upgrade 11.70tc3 to 12.10tc2 on a Windows server 2008R2 machine. I did this on my development server by using dbexport and then uninstalling 11.70 and then installing 12.10 and then dbimporting data. (As I recall, the installer would not do an upgrade over the top of the old installation) Would it work if I 1. move the old informixdir someplace 2. install 12.10 with default dbspaces on another disk than the current dbspaces and use same informixdir as before. 3. change the onconfig ROOTPATH and ROOTSIZE to where the data is and any tuning parameters from the old onconfig file. 4. restart ids. The servernum, servicename, servername, and port would be different so connect strings would change. I could rename the server in Instance Manager before the install so could use the same one as before. Are there differences inside the rootspace that would make the installation corrupt? Should I uninstall the old service first and use dbimport as I did on my dev server? ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

================================================================================ == ================================================================================ == Link - http://www.ibm.com/developerworks/data/library/techarticle/dm-1304overview/ Migration to Informix 12.10 Following are the migration paths to Informix 12.10: If you are on version 11.70, 11.50, 11.10, or 10.00, you can upgrade directly to Informix 12.10 on the same operating system. If you are on earlier versions of the database server that do not support direct upgrade, consider these options: Upgrade to an earlier, interim version of the database server that supports direct upgrade to 12.10 before you upgrade to Informix 12.10. Refer to the migration information that is included in the documentation set for the interim version of the database server. Migrate to Informix 12.10, installing it in a new location, and then use the dbexport and dbimport utilities or distributed SQL to move your data into the new database server. If necessary, you can revert to the version of the database server from which you upgraded; however, you cannot revert to any other version of the database server. If you have a high-availability cluster or if you use Enterprise Replication, you must coordinate the migration of all servers involved in high-availability clusters or Enterprise Replication. Follow additional procedures to upgrade your servers from the IBM Informix Migration Guide. See Resources for a link. After successful migration to Informix 12.10, you must complete a series of post-migration tasks to prepare the new version of the server for use. For further details, see the IBM Informix Migration Guide. See Resources for a link. Note: Starting with Informix 12.10, the support to directly upgrade from versions 7.31 and 9.40 to the new Informix 12.10 was removed. ================================================================================ == ================================================================================ == Link - http://informix-technology.blogspot.com.br/2014/01/f-format-date-strings-formata cao-de.html This article should be read by customers planning the upgrade to versions 12.10.xC2+ or 11.70.xC8+. IBM made a change in the default behavior for the %F placeholder used in to_char() and to_date() functions as well as GL_DATETIME and DBTIME environemnt variables. In previous versions, if we used %F in these scenarios, it would include a dot (.) in the output (when we're converting DATE/DATETIME values to text) or would expect the dot in the input when we're loading/reading text into a DATE or DATETIME variable or field. It's easy, from my point of view, to accept that this should not work like it did. In other words, the behavior was wrong (why would we get a dot if we don't get a ":" by default to separate hours from minutes or minutes from second?) But, as usual with the defaults, changing it means we can break existing usage. So I'm glad I didn't have to decide on this. If I had to, I'd probably prefer to create a new placeholder that would not produce nor expect the dot. But that was not the decision, and I really think this will impact some customers. Let's see some examples: ================================================================================ == ================================================================================ ==