Hi all,

we're having problems upgrading a V9.1 to a v9.7

The scripts for compatibility checks pass but
/opt/ibm/db2/V9.7/instance/db2iupgrade -d -u db2fenc1 db2inst1
fails with the following error message:

db2: symbol lookup error: db2: undefined symbol: sqltGetCompTraceFlag
Update DBM cfg SYSADM_GROUP errcode = 127
DBI1281E The database manager configuration file could not be
initialized.
....

Tracking the script debug log it appears to choke on get_db2dir_ver()
from db2iutil
but if I manually run the command
/opt/ibm/db2/V9.7/bin/db2fupdt -f /home/db2inst1/sqllib/ctrl/.instuse -
p DB2DIR
I get
/opt/ibm/db2/V9.1

I have lost hope

On May 20, 8:35*am, Edoardo <edoardo... (AT) gmail (DOT) com> wrote:
Seems like you have mutiple instances with different versions of DB2
on this machine.
Check if you have a V9.1 instance, and then Proceed as required,
whether to use a different name,

db2rmln" command from /<install_path>/cfg ...etc

Cheers
Shashi Mannepalli

I don't know if it's related but we had some upgrade issues also.

Try the following

cd opt/ibm/db2/V9.7/instance
opt/ibm/db2/V9.7/instance/db2iupgrade -d -u db2fenc1 db2inst1

for some reason we had to be in the 9.7 directory tree before some
commands
from the 9.7 tree would resolve all files correctly.

On May 20, 7:31*pm, whatever <audheya2... (AT) gmail (DOT) com> wrote:
Hi Shashi,

thanks for the hint; tried running the rmln script and hunting down
any stray symlink but - unless I have missed any - the upgrade keeps
failing.
If there isn't anything else to try, I think I will create a V9.7
instance a do a dump/restore.

BTW, I tried following the steps suggested in
http://www.db2china.net/club/viewthr...table&tid=8425
but I don't get any.


Best,
Edoardo

On May 23, 8:52*am, Edoardo <edoardo... (AT) gmail (DOT) com> wrote:

Do a UNIX Find command on your machine for this file .instuse.

Then do a cat .instuse on that file. That way you can find any
instances lurking around.
Now once u get the path in that file something like this

cd /to the db2dir path /instance
db2ilist

And see what instance is there.

Lastly, try the db2icrt with DEBUG option and see what the output
says, it might help u identify the instance name it is failing with.

Cheers
Shashi Mannepalli