dbTalk Databases Forums  

Upgrade from DB2 LUW 9.5 to 9.7 failed

comp.databases.ibm-db2 comp.databases.ibm-db2


Discuss Upgrade from DB2 LUW 9.5 to 9.7 failed in the comp.databases.ibm-db2 forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
oddbande
 
Posts: n/a

Default Upgrade from DB2 LUW 9.5 to 9.7 failed - 06-17-2010 , 08:01 AM






When trying to migrate a system from DB2 Enterprise Edition for LUW
9.5 fixpack 4 to 9.7 fixpack 2 on Windows we got an error. I did all
the steps without error until the command "db2 upgrade database db1"
returned error message ADM0501C. From the explanation to this message
it seems that one can use the db2hdr utility to change the default
stack size for db2syscs.exe like this: 'db2hdr \sqllib\bin
\db2syscs.exe /s:<stackreserve>[,<stackcommit>]'. But there is no
explanation to what the parameters mean (stackreserve/stackcommit) or
what the default stack size for db2syscs.exe is. I would also
appreciate if some decent examples could be provided in the
documentation.

Has anyone encountered an error like this before and how were they
able to solve it?

I have now returned to version 9.5 but will give it another try as
soon as possible. I'm thinking of opening a PMR with IBM but if there
is an easy way to solve this, that should not be necessary.

Regards
Odd Bjørn Andersen,
ErgoGroup AS, Oslo, Norway

Reply With Quote
  #2  
Old   
hsn_
 
Posts: n/a

Default Re: Upgrade from DB2 LUW 9.5 to 9.7 failed - 06-17-2010 , 10:54 AM






Its bogus error message nothing to do with db2hdr, but i dont remember
how we did solved it, something was wrong with database configuration
before migration (log space, agent stack size, freespace in system
catalog) are my guesses

Reply With Quote
  #3  
Old   
Helmut Tessarek
 
Posts: n/a

Default Re: Upgrade from DB2 LUW 9.5 to 9.7 failed - 06-17-2010 , 03:16 PM



This is a known issue. Please change the agent stack size to 128. Recycle the
instance and you are done.

db2 update dbm cfg using AGENT_STACK_SZ 128

On 17.6.2010 10:54, hsn_ wrote:
Quote:
Its bogus error message nothing to do with db2hdr, but i dont remember
how we did solved it, something was wrong with database configuration
before migration (log space, agent stack size, freespace in system
catalog) are my guesses

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.