By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,280 Members | 1,601 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,280 IT Pros & Developers. It's quick & easy.

Installation mess

P: n/a
Hello people,

I have an AIX system with the following characteristics:

- OS Level : AIX 5.3.0.0
- DB2 Level :
DB21085I Instance "dwinst1" uses "64" bits and DB2 code release
"SQL08023"
with level identifier "03040106".
Informational tokens are "DB2 v8.1.1.96", "s050811", "U803920", and
FixPak
"10".
Product is installed at "/usr/opt/db2_08_01".

We have already installed DB2 V8 ESE with fixpak 10 on this machine.
The installation path for ESE is /usr/opt/db2_08_01 filesystem. I tried
to install DB2 V8 WSE on the same machine. I created an additional
filesystem /usr/opt/db2_08_01_wse so that i can install WSE on this
filesystem. I initiated the installation and by mistake i choose
"Typical" installation and it proceeded to install the binaries of WSE
into the filesystem of ESE. The installation finished successfully. Now
when i start again the installation of WSE it says that it is already
installed. The current instances are not affected. The only difference
i can see in filesets is an additional fileset db2_08_01.wssg with
version 8.1.1.0. How can i delete the installation of WSE and reinstall
it on a new filesystem? Can i delete only the extra fileset??

Thank you

Apr 16 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
DM***@laiki.com wrote:
Hello people,

I have an AIX system with the following characteristics:

- OS Level : AIX 5.3.0.0
- DB2 Level :
DB21085I Instance "dwinst1" uses "64" bits and DB2 code release
"SQL08023"
with level identifier "03040106".
Informational tokens are "DB2 v8.1.1.96", "s050811", "U803920", and
FixPak
"10".
Product is installed at "/usr/opt/db2_08_01".

We have already installed DB2 V8 ESE with fixpak 10 on this machine.
The installation path for ESE is /usr/opt/db2_08_01 filesystem. I tried
to install DB2 V8 WSE on the same machine. I created an additional
filesystem /usr/opt/db2_08_01_wse so that i can install WSE on this
filesystem. I initiated the installation and by mistake i choose
"Typical" installation and it proceeded to install the binaries of WSE
into the filesystem of ESE. The installation finished successfully. Now
when i start again the installation of WSE it says that it is already
installed. The current instances are not affected. The only difference
i can see in filesets is an additional fileset db2_08_01.wssg with
version 8.1.1.0. How can i delete the installation of WSE and reinstall
it on a new filesystem? Can i delete only the extra fileset??

Uh.... did you install the second version as "alternate fixpack"?
In DB2 V8 on a unix system you can a have a primary install and an
alternate. (In DB2 Viper this is all simplified).

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Apr 16 '06 #2

P: n/a
Hmm i have never heard of an "alternate fixpack"! The second
installation was performed as a normal first time installation. My
objective (actually my management's objective) is to install both
versions, the ESE and the WSE editions.

Thank you

Apr 16 '06 #3

P: n/a
<DM***@laiki.com> wrote in message
news:11**********************@z34g2000cwc.googlegr oups.com...
Hmm i have never heard of an "alternate fixpack"! The second
installation was performed as a normal first time installation. My
objective (actually my management's objective) is to install both
versions, the ESE and the WSE editions.

Thank you


You can create WSE instances with an ESE install, so I am not sure why you
are doing that.
Apr 16 '06 #4

P: n/a
I am doing that because ... (now i want to swear on my management...).
It is a matter of licencing and what our company bought.

So my issue now is how do i rectify this installation mess and install
again the WSE.

thanks

Apr 17 '06 #5

P: n/a
<DM***@laiki.com> wrote in message
news:11********************@v46g2000cwv.googlegrou ps.com...
I am doing that because ... (now i want to swear on my management...).
It is a matter of licencing and what our company bought.

So my issue now is how do i rectify this installation mess and install
again the WSE.

thanks


If you are not licensed for ESE, then why don't you uninstall it?
Apr 17 '06 #6

P: n/a
Because i have already create 4 instances on that and i do not have the
time (due to management pressure) to recreate them using the WSE.
I have an additional task which has a higher priority. This task
involves the installation of WSE and migration of a DB2 database from
windows to unix.

thank you

Apr 17 '06 #7

P: n/a
DM***@laiki.com wrote:
Because i have already create 4 instances on that and i do not have the
time (due to management pressure) to recreate them using the WSE.
I have an additional task which has a higher priority. This task
involves the installation of WSE and migration of a DB2 database from
windows to unix.


Hmm - you *are* in a bit of a pickle. The problem is, except for the
alternate fixpacks, WSE and ESE both install to the same directory. To
make matters just a bit more fun, alternate fixpacks only support ESE.

In an ideal world, you would just simply uninstall ESE, install WSE, apply
FP10 (or later), run db2iupdt, and you'd be done. I get the distinct
impression that your world isn't so ideal ;-)

The next best solution I can think of is quite a bit more involved.
* download and install ESE alternate fixpack 10.
* Using the new install path, run db2iupdt on each instance to "move" the
instance to your alternate path. The path for FP10 will
be /usr/opt/db2_08_FP10, I think.
* Uninstall your original ESE.
* Install WSE (there is no "alternate" WSE, so there's only one choice
here)
* Create your new instance(s).

Note all the restrictions of alternate fixpacks, though:
* Only ESE is supported. If you have Data Warehouse or Information
Integrator or Net Search Extenders installed as well, these won't migrate
to your alternate path, and you'll lose their functionality.
* You can't apply a regular fixpack to ESE in the alternate path. This is
somewhat mitigated by the fact you can install FP11 to yet another
path, /usr/opt/db2_08_FP11, I believe, and then update your instances to
the new path and then uninstall the old path.
* Anything else that may be documented in the fixpack readmes.

As Serge mentioned, Viper should have a much better story here.
Apr 17 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.