dbimport/dbexport

Hi, We are planning on migrating our IDS 11.70 to IDS 12.10 and migrate the IBM machine as well from P7 to P8. We have a plan in place which will use a storage type cloning procedure but also looking in a scenario wherein rolling back to the old version (when all else fails) using a manual unload/load command. Upon testing the unload/load command execute properly but had a runtime of 13 hours!!! so we want to try if dbimport/export is much faster. Since I am not using this command I would like to ask for your inputs regarding dbimport/export 1. assuming we will rollback from new to old using dbimport/dbexport can I db export data only since the table schema,indexes, fragments for 11.70 and 12.10 would just be the same. The process we would like would be truncate data on all tables for lower version, dbexport from higher version (data only) and dbimport on our lower version machine 2. if unload/load runtime is 13 hours do you think the dbexport/dbimport will cut the process drastically? Thanks and more power to all of you GOD bless

Hi Lester. I would suggest you to separare this into two steps: 1) do your box migration first. This could be easily done with you actual machine running (via ifxclone, or even using ER). 2) After sync is complete, you can stop both boxes, and proceed to the in place upgrade of the new one. This will speed up things, you can change your actual schema if you need to optimize things, and let your old instance in a consistent state for recovery. Hope this helps. Best regards. Alexandre Marini

Hi Alexandre, Thanks for taking time to answer my question and sorry for not being concise on my explanation. let me expound further 1. We have 2 machines, 1 running P7 and IDS 11.7 the other one would be the updated version P8 and IDS 12.10 2. Our sysads will do cloning of P7 (IDS 11.7) then apply it in P8 then upgrade the IDS version from there. 3. We will do parallel batch process on 11.7 and 12.10 and if equal counts of data we will change the prod from 11.7 to 12.10 machine 4. The problem would be the transactions AFTER the switch of prod and testing server, if there will be any problems with the new server the only way to rollback is to backup/restore per table data from 12.10 to 11.7 (correct me if I'm wrong and there are any other way) 5. Tried doing manual unload/load for 13 hours, if we do dbexport can I only export data since both machines (P7 and P8) will have same db,table schema as well as fragments and index location.

ER the two servers for the migration ? Paul Watson Oninit www.oninit.com Tel: +1 913 674 0360 Cell: +1 913 387 7529 Oninit® is a registered trademark of Oninit LLC Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. > On Feb 11, 2018, at 18:45, LESTER POLICARPIO <lpolicarpio2009@yahoo.com> wrote: > > Hi, > > We are planning on migrating our IDS 11.70 to IDS 12.10 and migrate the IBM > machine as well from P7 to P8. We have a plan in place which will use a > storage type cloning procedure but also looking in a scenario wherein rolling > back to the old version (when all else fails) using a manual unload/load > command. Upon testing the unload/load command execute properly but had a > runtime of 13 hours!!! so we want to try if dbimport/export is much faster. > Since I am not using this command I would like to ask for your inputs > regarding dbimport/export > > 1. assuming we will rollback from new to old using dbimport/dbexport can I db > export data only since the table schema,indexes, fragments for 11.70 and 12.10 > would just be the same. The process we would like would be truncate data on > all tables for lower version, dbexport from higher version (data only) and > dbimport on our lower version machine > > 2. if unload/load runtime is 13 hours do you think the dbexport/dbimport will > cut the process drastically? > > Thanks and more power to all of you GOD bless > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. --Apple-Mail-5252D38C-B768-4FC2-845B-EE87FE93FEF8

Hi Paul, It's not the migration we are worried about but the rollback from new version to old version. Since new data will go thru the new server (assuming the switch of test and prod server was done) we think the only way to go to the lower version will be to unload/load or dbexport/dbimport data from new to old server. unloading will not be much of an option since it was too long to process (13 hrs). Can I dbexport the data only? or schema will alwasy be included? the schema of the new and old server will be the same it's the data I want to transfer from new to old server

ER will keep the data in sync so you can roll back new to old If ER is not broken, or if ER is broken you can revert to the as was data However, if you need to roll back after 13 hours IMHO i would say you had inadequate testing. I have never reverted a production migration ever. Reverted many test systems thought Cheers Paul Paul Watson Oninit www.oninit.com Tel: +1 913 674 0360 Cell: +1 913 387 7529 Oninit® is a registered trademark of Oninit LLC Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. > On Feb 11, 2018, at 20:58, LESTER POLICARPIO <lpolicarpio2009@yahoo.com> wrote: > > Hi Paul, > > It's not the migration we are worried about but the rollback from new version > to old version. Since new data will go thru the new server (assuming the > switch of test and prod server was done) we think the only way to go to the > lower version will be to unload/load or dbexport/dbimport data from new to old > server. unloading will not be much of an option since it was too long to > process (13 hrs). Can I dbexport the data only? or schema will alwasy be > included? the schema of the new and old server will be the same it's the data > I want to transfer from new to old server > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. --Apple-Mail-CD0B4E8B-B458-4B88-AE87-EB5887B2C9B8

Hi, sadly we do not use ER since we replicate via third party application and thru the storage mounted on the server. We are still in testing phase and we are just covering some ideas of worst case scenario if ever the migration was successful but along the way encountered an error. I am just thinking if unload/load execution time is 13 hrs would dbexport/dbimport will just be close to that time frame?

Assuming you are parallel unloads/loads I would expect them to be quicker than dbimport/dbimport Paul Watson Oninit www.oninit.com Tel: +1 913 674 0360 Cell: +1 913 387 7529 Oninit® is a registered trademark of Oninit LLC Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. > On Feb 11, 2018, at 22:06, LESTER POLICARPIO <lpolicarpio2009@yahoo.com> wrote: > > Hi, > > sadly we do not use ER since we replicate via third party application and thru > the storage mounted on the server. We are still in testing phase and we are > just covering some ideas of worst case scenario if ever the migration was > successful but along the way encountered an error. I am just thinking if > unload/load execution time is 13 hrs would dbexport/dbimport will just be > close to that time frame? > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. --Apple-Mail-073D8BC0-9803-41D8-BA02-D417697328E1

This certainly is a brutal way of reverting back. You also have to consider the time to rebuild indexes and update statistics etc. Its best to setup ER between the two servers so in the event you do have to revert back it will be a much simplier to accomplish. Mark