ESE -> WSE?

[Roger Eriksson]

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple way
to perform this or how should it be done?

Thanks

--

Mvh

/RE

[Ian]

Roger Eriksson wrote:

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple way
to perform this or how should it be done?

Is this for licensing reasons? Does your database have more than one
partition, or is it just a single partition on ESE?

If you just want a non-partitionable (is that a word?) instance, db2icrt
has an option to indicate the type of instance you want.

db2icrt -s wse -u fenced_id instance_id

[Darin McBride]

Roger Eriksson wrote:

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple way
to perform this or how should it be done?

If this is for licensing reasons, the easiest way is to simply stop all your
instances (including the das), deinstall, install WSE, reapply whatever
fixpack you're on, update all your instances (including the das), and
restart everything.

There are less invasive methods where you can surgically uninstall the parts
that are unique to ESE and then install the parts that are unique to WSE,
but that gets to be less simple, and you asked for simple ;-)

Of course, if you have any partitioned database(s), they are no longer going
to work.

[Knut Stolze]

Darin McBride wrote:

Roger Eriksson wrote:

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple
way to perform this or how should it be done?

If this is for licensing reasons, the easiest way is to simply stop all
your instances (including the das), deinstall, install WSE, reapply
whatever fixpack you're on, update all your instances (including the das),
and restart everything.

Wouldn't it be sufficient to just remove the ESE license and roll-in the WSE
license?

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Ian]

Knut Stolze wrote:

Darin McBride wrote:

Roger Eriksson wrote:

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple
way to perform this or how should it be done?

If this is for licensing reasons, the easiest way is to simply stop all
your instances (including the das), deinstall, install WSE, reapply
whatever fixpack you're on, update all your instances (including the das),
and restart everything.

Wouldn't it be sufficient to just remove the ESE license and roll-in the WSE
license?

No, there is actually at least 1 RPM package that differs between the
WSE (IBM_db2wssg81) and ESE (IBM_db2essg81) products, not to mention the
additional packages that come with ESE (like IBM_db2pext81, IBM_db2conn81).

As Darin said, easiest is to uninstall ESE, reinstall WSE and update the
instances, AS LONG AS you don't have any partitioned databases.

[Darin McBride]

Knut Stolze wrote:

Darin McBride wrote:

Roger Eriksson wrote:

We are downgrading from DB2 8.2 ESE on Linux to WSE. Is there a simple
way to perform this or how should it be done?

If this is for licensing reasons, the easiest way is to simply stop all
your instances (including the das), deinstall, install WSE, reapply
whatever fixpack you're on, update all your instances (including the
das), and restart everything.

Wouldn't it be sufficient to just remove the ESE license and roll-in the
WSE license?

Excellent question.

It is not sufficient to solely do that without interacting with the OS
installer (rpm in this case) in some way.

The license manager relies on the product signatures (IBM_db2essg81 and
IBM_db2wssg81) to determine what licenses are checked. If you have the ESE
signature installed, the DB2 license manager will check for the ESE
license. If it is present, all is well with the world, but if it's
missing, you enter try&buy for that product. Of course, if try&buy is
expired, then ESE functionality is turned off.

If you are missing the WSE signature, the DB2 license manager will not even
check for the WSE license. I'm not even sure that the DB2 license manager
(db2licm) will even allow you to apply the WSE license without the WSE
signature installed - it may, but even if it does, that license won't be
looked at again without the WSE signature.

If you have both the ESE and WSE signatures installed, but only one license,
DB2 will continue to function with that license even after the try&buy of
the other signature runs out. However, you'll get a message during
db2start that your license has expired even as DB2 continues to operate
(with the other license).

Thus, the surgical method involves removing the ESE signature (and the one
other RPM that is ESE-specific, IBM_db2pext81) and adding the WSE
signature, reapplying the fixpack to get the signature at the right level
(you can just add the WSE signature straight from the Linux fixpack to get
it at the right level in a single step), and then applying your license
key. You still need to run db2iupdt against your instance(s) for the
license to be accepted.

Simpler is to uninstall/reinstall. A lot less to think about ;-)
Especially since the reinstall will install the WSE license automatically
if that's the WSE image you have (as opposed to a try&buy WSE image).
Hint: to convert a try&buy image to a fully-licensed image, you should just
have to put your license key in the db2/license directory and then the
installer will automatically pick it up during the install.

[Laurence]

Hi,

What's the key file name? Is db2licst.dat?
Laurence

[Darin McBride]

Laurence wrote:

Hi,

What's the key file name? Is db2licst.dat?

The license key that I was referring to is the .lic file that comes with a
licensed DB2 product, such as 'db2ese.lic' or 'db2wse.lic' for ESE and WSE,
respectively.

[Laurence]

Hi,

What's the key file name? db2licst.dat?
Laurence