db2 z/os upgrade vs v12 new install

Mark Vickers

db2 z/os upgrade vs v12 new install
These are very early thoughts and may get shot down before it even takes off…

Synopsis:

1. Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/ then upgrade toolsets and then upgrade DB2.
(toolset upgrade willy apply to either path)

2. Our DB2 was frozen by management in 2013 as it was going away and after two failed ERP attempts, we are suddenly back on the grid, so I have 4 years of PTFs to apply !

3. No skip level migration to v12.

4. Cloning objects across would save having to convert tablespaces to UTS and hopefully eliminate other depreciated possible issues etc.

5. User data is just over 1TB.

I do realize there are many reasons why this is probably not a good idea, especially since it is not supported by IBM, but I was curious
whether anyone had successfully done a new install and ported all the objects and data etc. instead of an upgrade ?
Feel free to shoot flak at this.

[Signature5]


Attachments

  • image001.png (21.5k)

Venkat Srinivasan

RE: db2 z/os upgrade vs v12 new install
(in response to Mark Vickers)

What exactly do you mean by cloning? V12 will be expecting pagesets to be in extended RBA format. V10 CM is in old format. your clone will have to be a unload and reload and not any other means.

How do you mitigate incompatibilities typical as part of the pre migration check. You will potentially miss v11 pre migration check.   

In terms of cost what do you save by skipping V11 that you desperately want to skip?   

I have not seen anyone doing this way.

Venkat

In Reply to Mark Vickers:

These are very early thoughts and may get shot down before it even takes off…

Synopsis:

1. Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/ then upgrade toolsets and then upgrade DB2.
(toolset upgrade willy apply to either path)

2. Our DB2 was frozen by management in 2013 as it was going away and after two failed ERP attempts, we are suddenly back on the grid, so I have 4 years of PTFs to apply !

3. No skip level migration to v12.

4. Cloning objects across would save having to convert tablespaces to UTS and hopefully eliminate other depreciated possible issues etc.

5. User data is just over 1TB.

I do realize there are many reasons why this is probably not a good idea, especially since it is not supported by IBM, but I was curious
whether anyone had successfully done a new install and ported all the objects and data etc. instead of an upgrade ?
Feel free to shoot flak at this.

[Signature5]


Joel Goldstein

db2 z/os upgrade vs v12 new install
(in response to Venkat Srinivasan)
Not a good idea to consider anything IBM does not support.



Like the old -- it’s not nice to fool mother nature -- butter vs. margarine commercials.

( for the dinos on here…)





Joel Goldstein
Responsive Systems
Buffer Pool Tool(R) for DB2, the worldwide industry standard

Predicts the IO rate/Sec for tuning changes
Performance software that works......
Predicts Group Buffer Pool performance too!
http://www.responsivesystems.com www.responsivesystems.com
tel. (732) 972-1261
fax.(732) 972-9416

[login to unmask email]



From: Venkat Srinivasan [mailto:[login to unmask email]
Sent: Monday, March 20, 2017 6:27 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: db2 z/os upgrade vs v12 new install



What exactly do you mean by cloning? V12 will be expecting pagesets to be in extended RBA format. V10 CM is in old format. your clone will have to be a unload and reload and not any other means.

How do you mitigate incompatibilities typical as part of the pre migration check. You will potentially miss v11 pre migration check.

In terms of cost what do you save by skipping V11 that you desperately want to skip?

I have not seen anyone doing this way.

Venkat

In Reply to Mark Vickers:

These are very early thoughts and may get shot down before it even takes off…

Synopsis:

1. Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/ then upgrade toolsets and then upgrade DB2.
(toolset upgrade willy apply to either path)

2. Our DB2 was frozen by management in 2013 as it was going away and after two failed ERP attempts, we are suddenly back on the grid, so I have 4 years of PTFs to apply !

3. No skip level migration to v12.

4. Cloning objects across would save having to convert tablespaces to UTS and hopefully eliminate other depreciated possible issues etc.

5. User data is just over 1TB.

I do realize there are many reasons why this is probably not a good idea, especially since it is not supported by IBM, but I was curious
whether anyone had successfully done a new install and ported all the objects and data etc. instead of an upgrade ?
Feel free to shoot flak at this.

[Signature5]





-----End Original Message-----

Isaac Yassin

db2 z/os upgrade vs v12 new install
(in response to Venkat Srinivasan)
During the years I did "jump" migrations like that (4 to 7, 7 to 9, 7 to
10). Needs very careful planning and execution. I don't recommend it unless
no other choice.

Isaac Yassin
Sent from my Galaxy Note 5

בתאריך 21 במרץ 2017 03:27,‏ "Venkat Srinivasan" <[login to unmask email]> כתב:

> What exactly do you mean by cloning? V12 will be expecting pagesets to be
> in extended RBA format. V10 CM is in old format. your clone will have to be
> a unload and reload and not any other means.
>
> How do you mitigate incompatibilities typical as part of the pre migration
> check. You will potentially miss v11 pre migration check.
>
> In terms of cost what do you save by skipping V11 that you desperately
> want to skip?
>
> I have not seen anyone doing this way.
>
> Venkat
>
> In Reply to Mark Vickers:
>
> These are very early thoughts and may get shot down before it even takes
> off…
>
> Synopsis:
>
> 1. Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/
> then upgrade toolsets and then upgrade DB2.
> (toolset upgrade willy apply to either path)
>
> 2. Our DB2 was frozen by management in 2013 as it was going away and after
> two failed ERP attempts, we are suddenly back on the grid, so I have 4
> years of PTFs to apply !
>
> 3. No skip level migration to v12.
>
> 4. Cloning objects across would save having to convert tablespaces to UTS
> and hopefully eliminate other depreciated possible issues etc.
>
> 5. User data is just over 1TB.
>
> I do realize there are many reasons why this is probably not a good idea,
> especially since it is not supported by IBM, but I was curious
> whether anyone had successfully done a new install and ported all the
> objects and data etc. instead of an upgrade ?
> Feel free to shoot flak at this.
>
> [Signature5]
>
>
>
> -----End Original Message-----
>

Aurora Emanuela Dellanno

RE: db2 z/os upgrade vs v12 new install
(in response to Mark Vickers)

Hey Mark,

 

the main issue as I can see it is that you say time is short, and due to extended RBA and UTS you actually have a long way ahead of you.

 

If you have no continuous availability requirement, then a fresh install is probably going to be your "quickest" option - you will still have to go to 10 NFM to be able to convert all the catalog objects with the extended RBA and LRSN.

 

Then you can "simply" create your new environment version 12 with all the appropriate names and so on, and load the data that you will have unloaded from your DB2 10 install.

 

This does not need to be supported by anyone, and it is not a skip level migration, it is a very lengthy and complex procedure that should not go wrong so long as, as I mentioned, you have no issues with being offline with your user data for the entire length of time it takes to load the data and verify the new install.

 

Migrating to 10 NFM and then 11 NFM is 3 (hopefully short) outages, creating a new DB2 12 install would take you out for possibly a week or longer, methinks.

 

Aurora

James Campbell

db2 z/os upgrade vs v12 new install
(in response to Mark Vickers)
"Time is short" - for what?

If it is to get to a version of DB2 that will be supported in October then you really only need
to apply the compatibility/fallback PTFs for V10 (were you were frozen before they came
out?), migrate to NFM, and then V11 CM. Probably doable, if you get the appropriate
outages.

I did a skip level migration from V7 to V10 using DSN1COPY. Because of the differences in
the internals of tablespaces created in CM8* and before and V12, I would only attempt this
one by an unload/reload strategy. As was mentioned, can your site afford the outage
window?

James Campbell


On 20 Mar 2017 at 19:42, Vickers, Mark wrote:

>
> These are very early thoughts and may get shot down before it even takes off...
>  
> Synopsis:
> 1.      Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/ then
> upgrade toolsets and then upgrade DB2.
> (toolset upgrade willy apply to either path)
> 2.      Our DB2 was frozen by management in 2013 as it was going away and after two failed
> ERP attempts, we are suddenly back on the grid, so I have 4 years of PTFs to
> apply !
> 3.      No skip level migration to v12.
> 4.      Cloning objects across would save having to convert tablespaces to UTS and
> hopefully eliminate other depreciated possible issues etc.
> 5.      User data is just over 1TB.
>  
> I do realize there are many reasons why this is probably not a good idea, especially
> since it is not supported by IBM, but I was curious
> whether anyone had successfully done a new install and ported all the objects and data
> etc. instead of an upgrade ?
> Feel free to shoot flak at this.
>  
> Signature5
>  

Mark Vickers

db2 z/os upgrade vs v12 new install
(in response to James Campbell)
Thanks everyone, I knew it was a bad idea, so didn't get too deep.

Now you have woken me up from my dream, I will get back to upgrading !

Mark Vickers

-----Original Message-----
From: James Campbell [mailto:[login to unmask email]
Sent: Tuesday, March 21, 2017 7:43 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: db2 z/os upgrade vs v12 new install

"Time is short" - for what?

If it is to get to a version of DB2 that will be supported in October then you really only need to apply the compatibility/fallback PTFs for V10 (were you were frozen before they came out?), migrate to NFM, and then V11 CM. Probably doable, if you get the appropriate outages.

I did a skip level migration from V7 to V10 using DSN1COPY. Because of the differences in the internals of tablespaces created in CM8* and before and V12, I would only attempt this one by an unload/reload strategy. As was mentioned, can your site afford the outage window?

James Campbell


On 20 Mar 2017 at 19:42, Vickers, Mark wrote:

>
> These are very early thoughts and may get shot down before it even takes off...
>  
> Synopsis:
> 1.      Time is short and being at DB2 v10 CM8* means apply maintenance/NFM/ then
> upgrade toolsets and then upgrade DB2.
> (toolset upgrade willy apply to either path) 2.      Our DB2 was
> frozen by management in 2013 as it was going away and after two failed
> ERP attempts, we are suddenly back on the grid, so I have 4 years of PTFs to
> apply !
> 3.      No skip level migration to v12.
> 4.      Cloning objects across would save having to convert tablespaces to UTS and
> hopefully eliminate other depreciated possible issues etc.
> 5.      User data is just over 1TB.
>  
> I do realize there are many reasons why this is probably not a good
> idea, especially since it is not supported by IBM, but I was curious
> whether anyone had successfully done a new install and ported all the
> objects and data etc. instead of an upgrade ?
> Feel free to shoot flak at this.
>  
> Signature5
>  

-----End Original Message-----

Russell Peters

RE: db2 z/os upgrade vs v12 new install
(in response to Mark Vickers)

You only need to get to v11 NFM. I apply db2 maintenance twice each year and usually find that most of the hold data items either don't apply in our shop or are things that require bouncing db2, rebinds, etc. which you'll have to do anyway. I would just apply the maintenance, run the pre-migration checks and move on to db2 11. I've never found the migrations to be all that difficult once I go through it in a sandbox and make good notes. Seems to me that the next six months should be plenty of time to get to v11 NFM from where you are now and may be easier/faster than trying to get around it.

Mark Vickers

db2 z/os upgrade vs v12 new install
(in response to Russell Peters)
Appreciate the comments Russell, v11 skip on our own was on a wing and a prayer, and now successfully annihilated.

Thanks,
Mark.

From: Russell Peters [mailto:[login to unmask email]
Sent: Wednesday, March 22, 2017 8:01 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: db2 z/os upgrade vs v12 new install


You only need to get to v11 NFM. I apply db2 maintenance twice each year and usually find that most of the hold data items either don't apply in our shop or are things that require bouncing db2, rebinds, etc. which you'll have to do anyway. I would just apply the maintenance, run the pre-migration checks and move on to db2 11. I've never found the migrations to be all that difficult once I go through it in a sandbox and make good notes. Seems to me that the next six months should be plenty of time to get to v11 NFM from where you are now and may be easier/faster than trying to get around it.

-----End Original Message-----