SMS/DMS relocation

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

aj - 24 Jan 2008 21:40 GMT

DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2

I will soon, in order to gain some disk space in my DB2
file systems:

1. Shut down DB2
2. Move all SMS/DMS files/folders to a new spot (with same
exact name and paths as old spot). All attributes/ownership
will also be exactly the same.
3. Start up DB2.

Assuming I take these steps, are there any potential gotchas
here?

Any advice appreciated..

aj

Reply to this Message

Lennart - 26 Jan 2008 16:23 GMT

> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>
[quoted text clipped - 11 lines]
>
> Any advice appreciated..

I'm not sure on how you are going to move the tablespaces and inform
db2 about the new position. Wouldnt it be easier to:

1) take backup
2) drop database
2) do redirected restore

/Lennart

Reply to this Message

Tapio Oikarinen - 28 Jan 2008 08:22 GMT

>> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>>
[quoted text clipped - 11 lines]
>>
>> Any advice appreciated..

If the paths to containers remain the same and databases are cleanly
taken down this will work fine.

> I'm not sure on how you are going to move the tablespaces and inform
> db2 about the new position. Wouldnt it be easier to:
[quoted text clipped - 4 lines]
>
> /Lennart

No.

tapsa

Reply to this Message

Knut Stolze - 28 Jan 2008 11:03 GMT

>>> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>>>
[quoted text clipped - 12 lines]
> If the paths to containers remain the same and databases are cleanly
> taken down this will work fine.

There is a difference between "will work fine" and "supported". Unless the
manuals state that you can do what has been proposed here (I don't know), I
would not even dream about basing a mission critical system on this
approach.

Signature

Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

Reply to this Message

aj - 28 Jan 2008 16:49 GMT

This worked just fine. I used the rsync utility (which will do binary
differential updates) to copy all the files/paths over. I also ensured
that ownership, chmod bits, modification dates, etc.... were all
**exactly** (and I do mean exactly) the same.

DB2 was none the wiser, and I got 50% more file system space...

aj

>>>> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>>>>
[quoted text clipped - 16 lines]
> would not even dream about basing a mission critical system on this
> approach.

Reply to this Message

Tapio Oikarinen - 28 Jan 2008 22:34 GMT

>>>> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>>>>
[quoted text clipped - 17 lines]
> would not even dream about basing a mission critical system on this
> approach.

Hmm.

I guess this approach would be "supported" with v9 if you just ran
"db2relocatedb" with dummy config file?

tapsa

Reply to this Message

Tapio Oikarinen - 28 Jan 2008 22:50 GMT

>>>> DB2 LUW v8.2 FP 14 Red Hat EL 3.4.6-2
>>>>
[quoted text clipped - 17 lines]
> would not even dream about basing a mission critical system on this
> approach.

Hmm.

I guess this approach would be "supported" with v9 if you just ran
"db2relocatedb" with dummy config file?

tapsa

Reply to this Message