Results 1 to 6 of 6
  1. #1
    Join Date
    Jan 2012
    Posts
    82

    Unanswered: DB2 migration error

    Hi I took a Database backup residing on a zlinux server on db2 9.5 and restored in on a new zlinux server with db2 9.7.

    After the restore command I got the following output..

    SQL2517W The database was restored and then upgraded to the current release.
    The database upgrade returned sqlcode "1243" and tokens "sqledrpdb2lk ".

    whats wrong.. the db itself seems to work fine.. but its a new production system and I want to find out if this error will cause any issues before getting this server online..

  2. #2
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    try to execute db2updv97
    check db cfg and compare with source db cfg
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  3. #3
    Join Date
    Aug 2011
    Posts
    45
    have u ran the command:
    db2iupdt inst_name
    db2 migrate database dbname

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    I received the same warning yesterday when migrating a v9.1 db to v9.7 via a restore. You need to check what sql1243 means:
    IBM DB2 9.7 Information Center for Linux, UNIX, and Windows

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    As per the above link, db2 failed to drop SYSTOOLS.DB2LOOK_INFO during migration. Ignore what it says about v8, db2 is calling sqledrpdb2lk when migrating from v8 and from v9.x. I confirmed that this table exists and is accessible.

    > db2 list tables for schema SYSTOOLS | grep DB2LOOK_INFO
    DB2LOOK_INFO SYSTOOLS T 2009-11-19-10.14.54.807688
    DB2LOOK_INFO_V SYSTOOLS V 2009-11-19-10.14.54.977315


    It says that ALTER TABLE and COPY SCHEMA will fail if not dropped. I understand we use this table during ADMIN_COPY_SCHEMA, but I don't see why we need to make use of this table during ALTER TABLE... I tried a very simple ALTER TABLE and it worked:


    > db2 "create table test (c1 int)"
    DB20000I The SQL command completed successfully.

    > db2 "alter table test add c2 int"
    DB20000I The SQL command completed successfully.

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,369
    Relevant errors in the db2diag.log:

    2012-04-05-09.52.15.334272-240 I293623A308 LEVEL: Warning
    PID : 13369428 TID : 1 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    APPID : *LOCAL.db2inst1.120405135212
    EDUID : 1
    FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:90
    MESSAGE : Begin sqledrpdb2lk

    2012-04-05-09.52.15.383402-240 E293932A447 LEVEL: Warning
    PID : 13369428 TID : 1 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    APPID : *LOCAL.db2inst1.120405135212
    EDUID : 1
    FUNCTION: DB2 UDB, base sys utilities, sqledrpdb2lk, probe:0
    MESSAGE : ZRC=0xFFFFFFFF=-1
    DATA #1 : <preformatted>
    Error dropping db2look operation table/view SYSTOOLS.DB2LOOK_INFO/SYSTOOLS.DB2LOOK_INFO_V, rc = -1, sqlcode = 0

    2012-04-05-09.52.15.383619-240 I294380A339 LEVEL: Warning
    PID : 13369428 TID : 1 PROC : db2bp
    INSTANCE: db2inst1 NODE : 000
    APPID : *LOCAL.db2inst1.120405135212
    EDUID : 1
    FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:100
    MESSAGE : End sqledrpdb2lk: with rc = 1243, sqlcode = 1243

Posting Permissions

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