in place alters
Answered: green (solid confidence) — Art Kagel and Paul Watson both say dbexport/dbimport writes the current schema, so outstanding in-place alters need no fixing. Follow-ups establish that fixing them matters only for an in-place upgrade and for onrestorept reversion, and the asker accepted this.
Advisory only.
Posted in 2021
John Smith asked whether in-place alters must be fixed when moving from 11.70 to 14.10 using dbexport/dbimport. Art Kagel and Paul Watson said no, since the export flattens the schema. Paul added that outstanding in-place alters matter for in-place upgrades because they break onrestorept reversion. Mike Walker agreed and recommended a pre-upgrade backup. Solved.
Topics: Migration, Import/Export & Data Conversion
Hello
do we need to fix inplace alters when upgrading from 11.70 to 14.10 with dbexport from source 11.7 server / dbimport on target 14.1 server ?
Thanks
------------------------------
John Smith
------------------------------
#Informix
No, The dbexport will export the latest schema version of the DDL and the data so that is what dbimport will import. Checkout myexport/myimport, my dbexport/dbimport replacement utilities. They are considerably faster than dbexport & dbimport.
------------------------------
Art S. Kagel, President and Principal Consultant
ASK Database Management Corp.
www.askdbmgt.com
------------------------------
Thanks Art ------------------------------ John Smith ------------------------------
Nope, you are flat filing the system so there is no need Cheers Paul Paul Watson Oninit LLC +1-913-387-7529 www.oninit.com Oninit® is a registered trademark of Oninit LLC
I saw that we need to fix in place alters when upgrading to 14.1, but i don't remember it for upgrading to 12.1, do we need to fix it as well before upgrading to 12.1 ? Thanks ------------------------------ John Smith ------------------------------
If you are doing an in place upgrade then that is the recommendation My last 11.70 to 14.10 having outstanding in-place alters broke the onrestorept reversion. However, it had zero impact on the actual upgrade itself. The customer decided to rely on a restore if the upgrade failed rather than fix the in-place alters as the outstanding in-place alters where all on 1B+ row tables. As I have never reverted a production upgrade in my entire life I wasn't worried Cheers Paul Paul Watson Oninit LLC +1-913-387-7529 www.oninit.com Oninit® is a registered trademark of Oninit LLC
Thanks for your reply, OK that"s what i had understood, the inplace alters fixing is only needed when reverting from upgrade ( onrestorept). so we can also do a full backup (L0) and restore it if something went wrong and then no need to inplace alters am i right ? :) ------------------------------ John Smith ------------------------------
Yep but we had a snapshot to revert from so close enough to instant. Cheers Paul
You are right...but the biggest worry is if you need to revert days or weeks later (say you run into a bug or performance issues). Restoring from the "old" backup will mean that recent changes will be lost and need to be reapplied somehow. Saying that, just like Paul, I have not had to do this after a production upgrade...and I hope that I never have to! Taking a backup before the upgrade is best practice anyway. ------------------------------ Mike Walker ------------------------------
If you have to revert a production system then you haven't tested properly .... IMHO Cheers Paul