This is a discussion on Moving a DB/2 instance within the DB2 forums, part of the Database Server Software category; --> We currently have DB/2 8.1 running on z/OS 1.5. I need to move it to DB/2 8.1 on z/OS ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| We currently have DB/2 8.1 running on z/OS 1.5. I need to move it to DB/2 8.1 on z/OS 1.8. Not knowing much about DB/2 admin, I'm at a loss as where to start. Can someone point me to a resource that will help migrate a DB/2 system between OS releases? Regards, Kevin Kinney |
| |||
| You're not changing DB2 releases at all so a simple BACKUP and RESTORE should be the simplest approach.. You should be doing this anyway if you are building your new Z/OS on a separate set of disk drives. Philip Sherman mvsguy wrote: > We currently have DB/2 8.1 running on z/OS 1.5. I need to move it to > DB/2 8.1 on z/OS 1.8. Not knowing much about DB/2 admin, I'm at a > loss as where to start. > > Can someone point me to a resource that will help migrate a DB/2 > system between OS releases? > > Regards, > Kevin Kinney > |
| |||
| I can only wish it was that simple. While DB/2 is the same version (8.1), z/OS 1.8 is at a different DB/2 8.1 put level. As I don't know enough about DB/2 yet, my inclination is to unload all the app tables to flat files and then do the same for the system tables. Am I on the right track? Regards, Kevin Kinney |
| |||
| I still think you're making a mountain out of a molehill. Backup/restore is one of the standard ways to "upgrade" a database and should easily handle an upgrade to a higher put level. Check the put documentation between the level you're at and the one you're going to. If there's any issues with a backup not being restorable, it will be noted there. This is a critical issue for data recovery and will be documented. You could also call IBM support and verify that backup/restore won't be a problem. Phil Sherman mvsguy wrote: > I can only wish it was that simple. > > While DB/2 is the same version (8.1), z/OS 1.8 is at a different DB/2 > 8.1 put level. > > As I don't know enough about DB/2 yet, my inclination is to unload all > the app tables to flat files and then do the same for the system > tables. > Am I on the right track? > > Regards, > Kevin Kinney > |
| |||
| In article <1175258028.095912.245590@d57g2000hsg.googlegroups .com>, kkinney@fuse.net says... > I can only wish it was that simple. > > While DB/2 is the same version (8.1), z/OS 1.8 is at a different DB/2 > 8.1 put level. > > As I don't know enough about DB/2 yet, my inclination is to unload all > the app tables to flat files and then do the same for the system > tables. > Am I on the right track? > > Regards, > Kevin Kinney > So if you are talking about DB2 z/OS why are you talking about moving an instance? Db2 z/OS doesn't know what in instance is AFAIK. Am I missing something? |
| |||
| Gert van der Kooij wrote: > In article <1175258028.095912.245590@d57g2000hsg.googlegroups .com>, > kkinney@fuse.net says... >> I can only wish it was that simple. >> >> While DB/2 is the same version (8.1), z/OS 1.8 is at a different DB/2 >> 8.1 put level. >> >> As I don't know enough about DB/2 yet, my inclination is to unload all >> the app tables to flat files and then do the same for the system >> tables. >> Am I on the right track? > > So if you are talking about DB2 z/OS why are you talking about moving an > instance? Db2 z/OS doesn't know what in instance is AFAIK. Am I missing > something? No, you are not missing anything. DB2 z/OS doesn't have instances. The closest thing would be a subsystem. -- Knut Stolze DB2 z/OS Utilities Development IBM Germany |
| |||
| mvsguy wrote: > My apologies for using incorrect semantics. > > Is there some resource I can use to learn more about moving/migrating/ > merging a z/OS DB/2 subsystem/image/instance to another existing DB/2 > system at a higher DB/2 put level? I'm a bit confused. What's the problem with backup/restore? Note that you take a DB2 backup and do not use operating system commands for that. Maybe it would even be possible to tell the new DB2 subsystem to use the disks of the first one (pretty much like uncatalog/catalog on LUW). But I don't know if that is supported. If it isn't, I wouldn't try it. p.s: It's DB2 - not DB/2. -- Knut Stolze DB2 z/OS Utilities Development IBM Germany |
| ||||
| Mr. Kinney, you sound like you're in a tight spot. The best answer to your question would be to look in the Data Sharing: Planning & Admin manual. (SC18-7417-03) In there, you'll find a heading called "Procedure for moving data." Read that (several times if necessary) and you'll have a rough map for your move. To do this, you need to learn about utilities including LOAD, UNLOAD, etc from the Utilities manual. (SG18-7427-03) In addition, depending on which of the 3 move methods, you'll need to know about unload/reloads, offline image copies or a lot about z/OS. It sounds like you're well suited for the third method. And by the way, call it DB/2 or DB2, database or instance, whatever you want. People who truly want to help are very able to overlook such little matters. Regards, mvsguy |