Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / July 2006

Tip: Looking for answers? Try searching our database.

error upgrading from DB2 7.2 to DB2 8.2

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Ivan - 05 Jul 2006 05:10 GMT
Hi, I experienced a problem while upgrading from DB2 UDB LUW Workgroup
edition 7.2 FixPak 10a to Workgroup Server edition 8.2 FixPak 12. The
install wizard said the upgrade was successful but none of the MIGRATE
commands worked due to authorization problems.
The install log showed the following message for each instance -

1: ERROR:An error occurred while creating the instance "DB2". The
return code is
"-1959". Create the instance manually using the command "db2icrt".
1: Creating/migrating DB2 instances:.......Failure

and this in turn caused more problems later -

1: ERROR:An error occurred while configuring the database "DDBDTOOL".
1: ERROR:UPDATE NOTIFICATION LIST ADD CONTACT 'DB2 DBA'
SQL1092N  "DUDBDSVC" does not have the authority to perform the
requested command.
1: Configuring health alert notifications:.......Success
ERROR:SQL1013N  The database alias name or database name
"DDBDTOOL" could not be

found.  SQLSTATE=42705

1: ERROR:An error occurred while running the command
"E:\SQLLIB\bin\db2.exe CREATE
TOOLS CATALOG SYSTOOLS USE EXISTING DATABASE DDBDTOOL FORCE" to
initialize
and/or migrate the DB2 tools catalog database. The return value is "4".

1: Creating DB2 tools catalog:.......Failure
1: Unable to find the string resource 3574:.......Failure
1: Starting all DB2 services:.......Success
1: WARNING:A minor error occurred while installing "DB2 Workgroup
Server Edition"
on this computer. Some features may not function correctly.

A GET DBM CFG for each instance shows -

Database manager configuration release level            = 0x0900

Which I believe means it is still at 7.2

I can't seem to find any indication of what a "-1959" is or what causes
it. Dropping and re-creating the instances and re-cataloging the
databases got us back working but I would like to avoid this on the
other servers.

Any ideas?
Darin McBride - 05 Jul 2006 13:40 GMT
> Hi, I experienced a problem while upgrading from DB2 UDB LUW Workgroup
> edition 7.2 FixPak 10a to Workgroup Server edition 8.2 FixPak 12. The
> install wizard said the upgrade was successful but none of the MIGRATE
> commands worked due to authorization problems.
> The install log showed the following message for each instance -

I highly suggest calling IBM for this and opening a PMR.  I don't think that
this is something that many here will have encountered, and you're best off
by contacting the experts.
Ivan - 06 Jul 2006 01:23 GMT
> I highly suggest calling IBM for this and opening a PMR.  I don't think that
> this is something that many here will have encountered, and you're best off
> by contacting the experts.

Sorry, I should have mentioned that I have already raised a PMR. A
couple of suggestions came out of it but were not applicable in our
case. I also tried to reproduce the problem on a test server with no
success. But Murphy being Murphy its bound to happen on the rest of the
servers I have to upgrade.
I suppose I was hoping someone might have seen and solved this without
involving IBM.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.