Results 1 to 9 of 9

Thread: DB2 9.5 to 9.5

  1. #1
    Join Date
    Jan 2012
    Posts
    82

    Unanswered: DB2 9.5 to 9.5

    Hi all I have a DB2 9.5 instance running on a zlinux server. I have one db hosted on it.I need to upgrade that server to 9.7.

    First of all the stupidest question you may have heard but still. I can only find db2 enterprise edition of power system z . Will we use the same setup or is there a seperate setup for upgrading the server to 9.7?

    Also I have to upgrade the instance to 9.7 as well. I have read the Db2 publib but it is very confusing.

    Please reply asap. we have a production DB down.. And Everybody is yelling at me ..

  2. #2
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Don't upgrade without a proper migration plan.

    Do test the upgrade plan on a non-production environment first.

    I do not find the Infocenter to be confusing, but I do know that if you upgrade a zLinux production environment without adequate migration planning and rehearsals on non-production environments then they won't just be yelling at you...you just might deserve to be fired.

  3. #3
    Join Date
    Jan 2012
    Posts
    82
    We already have a migration plan in place. Not that stupid. The confusion is that will we be using the Db2 9.7 enterprise server installation media or will there be a seperate upgrade setup??

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by junaid377 View Post
    we have a production DB down.. And Everybody is yelling at me ..
    What's wrong with your prod db and why do you need to upgrade it? You need to test this migration process in your test env first and not in prod.


    To migrate from v9.5 to v9.7:

    - take offline db backup of your v9.5 db and make sure it complete successfully and it's a good image (db2ckbkp to check it)
    - capture v9.5 config info just in case [ie. db2support, dbm/db cfg, db2set -all, catalog info (db2cfexp can be use to collect some of it), etc...]
    - install v9.7 code
    - use db2ckmig to check your db is ok to migrate (db2imigr will call it as well)
    - stop the instance
    - db2imigr to migrate the instance
    - start the instance
    - migrate db to migrate the db

  5. #5
    Join Date
    Jan 2012
    Posts
    82
    well we will be doing it in test 1st. and production went down because during an load the db instance crashed. when we restarted the instance. The db is inconsistent state. When we try to restart the server the db recovary utility gets stuck at 99 % and we our db2diag log gets flooded with this error


    2012-05-22-16.52.56.469877-240 I50713470066A569 LEVEL: Warning
    PID : 28582 TID : 2199388154192PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : UAT1
    APPHDL : 0-7 APPID: *LOCAL.db2inst1.120522201233
    AUTHID : db2inst1
    EDUID : 20 EDUNAME: db2agent (UAT1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgWaitForLrecBufferLimit, probe:410
    MESSAGE : ZRC=0x870F0151=-2029059759=SQLO_WP_TERM
    "The waitpost area has been terminated"
    DATA #1 : String, 10 bytes
    Ignore rc.

    2012-05-22-16.52.56.469903-240 I50713470636A437 LEVEL: Severe
    PID : 28582 TID : 2199379765584PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000
    EDUID : 22 EDUNAME: db2loggw (UAT1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgwlp, probe:350
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
    DIA8414C Logging can not continue due to an error.

    2012-05-22-16.52.56.470055-240 I50713471074A438 LEVEL: Error
    PID : 28582 TID : 2199379765584PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000
    EDUID : 22 EDUNAME: db2loggw (UAT1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgasn2, probe:1820
    RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
    DIA8414C Logging can not continue due to an error.

    2012-05-22-16.52.56.470136-240 I50713471513A339 LEVEL: Severe
    PID : 28582 TID : 2199379765584PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000
    EDUID : 22 EDUNAME: db2loggw (UAT1) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgasn2, probe:4330
    MESSAGE : Logging can not continue.
    sqllib/db2dump/db2diag.log byte 50713471852/50713471852 (END)

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Don't attempt to migrate this db until the problem is resolved and the db is in consistent state. Open a pmr to address this problem.

    Check for disk errors in the OS logs (/var/log/messages*). Is this db using circular logging?

  7. #7
    Join Date
    Jan 2012
    Posts
    82
    Also anyone having the part number for the db29.7 for power system z???

  8. #8
    Join Date
    Jan 2012
    Posts
    82
    We tried ,open a pmr as well but we have not been able to recover it. And we are not migrating this db we have an old backup that we need to migrate to new server. We can't do that because backup is off 9.7 and instance is 9.5 so we can't restore it until we do an 9.7 upgrade on the instance


    and yes using circular logging
    Last edited by junaid377; 05-24-12 at 14:41. Reason: missed

  9. #9
    Join Date
    Mar 2012
    Location
    Canberra, Australia
    Posts
    38
    From what you are saying, you have no backups of the prod db at the 9.7 level except an "old" one and you run in circular logging mode. Surely you are doing daily full backups if you are in circular logging mode in which case restore the db from the last good daily backup

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •