Page 1 of 2 12 LastLast
Results 1 to 15 of 17

Thread: Mrs.

  1. #1
    Join Date
    Oct 2011
    Posts
    21

    Unanswered: db2 instance cannot be started after upgrade to Express-c 9.7

    Hi,

    My db2 database was corrupted after upgrade from Express-c 9.5.3.1.436 to Express-c 9.7.400.501 on Windows 2003 32-bit machine.

    To begin with, Windows cannot start db2 service DB2-DB2COPY1-DB2.

    Then I ran db2start in CLP, error "SQL1042C An unexpected system error occurred. SQLSTATE=58004" returned.

    In windows event viewer System log, there was an error message:
    "The DB2-DB2COPY1-DB2" service terminated with service-specific error 4294966254(0XFFFFFBEE)"

    The db2diag.log was no where to be seen, I have searched the entire disk.

    command db2set returned nothing on the screen.

    Issuing command "db2set" in CLP returned nothing. Issuing command "echo %db2instance%" in CLP returned "DB2".

    Please help, this is production.

    Thanks,
    Dixie
    Last edited by dixiefu; 10-19-11 at 06:35.

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    If you have a backup, then uninstall both copies of DB2 and reinstall the latest, and restore backup. I don't believe that you can upgrade DB2 Express-C 9.5 in the manner in which you attempted.

    If you don't have a backup of the databases (hard to believe you would attempt upgrade without a backup), then the databases should still remain after you unistall DB2, and then you will have to manually recatalog them on the path (see Catalog db on path in doc) after you reinstall DB2. Then you will have to run the update db program to bring it up to 9.7 (see instructions for the name of this program).
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    Oct 2011
    Posts
    21
    Hi Marcus,

    Thanks for the quick response. It is very much appreciated.

    I do have a backup, which was done in the V9.5.

    I did a New V9.7 install in anther machine and restored a database ("Jazz2" in this instance) from the V9.5 backup. It gave me this message:
    ================================================== =======
    "SQL2519N The database was restored but the restored database was
    not upgraded to the current release. Error "-980" with tokens
    "*N" is returned.

    Explanation:

    The database backup that you restored is from a previous release of DB2
    database product. After the database files were restored, an attempt was
    made to upgrade the database to the current release. The database
    upgrade failed.

    The database restore was completed but the database was not upgraded.

    User response:

    Review the SQLCODE (message number) returned for more information. Make
    any corrections and issue the UPGRADE DATABASE command before accessing
    the database. "

    =============================

    Then I did a "upgrade database Jazz2", below is the error:
    ----------------- Commands Entered ------------------------------
    upgrade database Jazz2;
    -------------------------------------------------------------------
    upgrade database Jazz2
    SQL0980C A disk error occurred. Subsequent SQL statements cannot be
    processed. SQLSTATE=58005

    SQL0980C A disk error occurred. Subsequent SQL statements cannot be processed.

    Explanation:

    A disk error occurred that prevented successful execution of the current
    and subsequent SQL statements. The application program is not permitted
    to issue additional SQL statements. For example, a recovery routine
    associated with the application program cannot issue additional SQL
    statements. The database is marked as needing recovery and all
    applications using the database are prevented from accessing the
    database.

    The statement cannot be processed.

    User response:

    Record all error information from the SQLCA, if possible. Terminate all
    applications using the database. Determine if the error is a hardware
    error. Restart the database. If recovery is not possible, restore the
    database from a backup copy.

    If installing the sample database, drop it and install the sample
    database again.

    sqlcode: -980

    sqlstate: 58005

    ************************************************** **

    Please see the attached db2diag.log for the error trace. Thank you very much for your help.

    Thanks,
    Dixie
    Attached Files Attached Files

  4. #4
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    I would try to create the sample database, and then post your issue on the DB2 Express-C Community Forum on the IBM website.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  5. #5
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    was it an online/offline backup
    verify in the doc if upgrade on this type of db2 is supported
    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

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    Quote Originally Posted by dixiefu View Post
    I do have a backup, which was done in the V9.5.

    I did a New V9.7 install in anther machine and restored a database ("Jazz2" in this instance) from the V9.5 backup. It gave me this message:
    ================================================== =======
    "SQL2519N The database was restored but the restored database was
    not upgraded to the current release. Error "-980" with tokens
    "*N" is returned.

    ...

    Then I did a "upgrade database Jazz2", below is the error:
    ----------------- Commands Entered ------------------------------
    upgrade database Jazz2;
    -------------------------------------------------------------------
    upgrade database Jazz2
    SQL0980C A disk error occurred. Subsequent SQL statements cannot be
    processed. SQLSTATE=58005

    It looks like the db2diag.log you attached is from the "upgrade db" attempt, not from the restore you performed before that (v9.5 -> v9.7 restore). You need to determine why restore failed with -980 (possibly some tablespace was not restored - ie. containers need to be redefined?) and redo it again. The db will be migrated during restore if everything gets restored correctly.

  7. #7
    Join Date
    Oct 2011
    Posts
    21
    The error in the db2diag.log with regards to the restore is:

    2011-10-26-22.57.19.247000+660 I586948F539 LEVEL: Error
    PID : 5020 TID : 2976 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 2976 EDUNAME: db2bm.1312.0 (JAZZ97)
    FUNCTION: DB2 UDB, buffer pool services, sqlbDMSAddContainerRequest, probe:805
    MESSAGE : ZRC=0x8002003C=-2147352516=SQLB_BAD_CONTAINER_PATH
    "Bad container path"
    DATA #1 : <preformatted>
    Error acquiring container 0 (E:\DB2\NODE0002\JAZZ\content_tablespace) for tbsp 3. Rc = 8002003C

    2011-10-26-22.57.19.247000+660 I587489F541 LEVEL: Severe
    PID : 5020 TID : 2976 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 2976 EDUNAME: db2bm.1312.0 (JAZZ97)
    FUNCTION: DB2 UDB, buffer pool services, sqlbSetPoolCont, probe:1360
    MESSAGE : ZRC=0x8002003C=-2147352516=SQLB_BAD_CONTAINER_PATH
    "Bad container path"
    DATA #1 : <preformatted>
    A severe error was encountered while trying to set new
    table space containers for table space CONTENTTS (3)

    =========================================

    (E:\DB2\NODE0002\JAZZ\content_tablespace) is the tablespace directory for the backuped (source) database, it is located in a remote machine A.

    I did a DB backup in machine A, then copy the backup file to machine B and did the restore there. The restore failed with the above error. During the restore process, machine A is inaccessible to machine B.

    The command I used to do the restore is:
    restore database Jazz2 user db2admin using TP$dbadmin$96 from "C:\Users\TestPro\Backups\Remote DB Backups" taken at 20111018212239
    into JAZZ301; and it ended up with the above error.

    Then I tried:
    restore database Jazz2 user db2admin using TP$dbadmin$96 from "C:\Users\TestPro\Backups\Remote DB Backups" taken at 20111018212239
    into JAZZ301 REDIRECT;
    set tablespace containers for 3 using (FILE "C:\DB2\NODE0000\JAZZ301_TS" 40000 );
    The problem is the set tablespace containers command frozen the session -- nothing happened.


    Any idea?


    Thanks,
    Dixie
    Last edited by dixiefu; 10-26-11 at 09:18.

  8. #8
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    -2147352516 maps to sql0289n:


    $ db2diag -rc -2147352516

    Input ZRC string '-2147352516' parsed as 0x8002003C (-2147352516).

    ZRC value to map: 0x8002003C (-2147352516)
    V7 Equivalent ZRC value: 0xFFFF813C (-32452)

    ZRC class :
    SQL Error, User Error,... (Class Index: 0)
    Component:
    SQLB ; buffer pool services (Component Index: 2)
    Reason Code:
    60 (0x003C)

    Identifer:
    SQLB_BAD_CONTAINER_PATH
    Identifer (without component):
    SQLZ_RC_BADCPATH

    Description:
    Bad container path

    Associated information:
    Sqlcode -298
    SQL0298N Bad container path.

    Number of sqlca tokens : 0
    Diaglog message number: 1



    It looks like you need to redefine some tablespace containers. Where (what drive) is the db stored on v9.5 server? Do you have the same drive available on the server with v9.7?

  9. #9
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    Just noted you edited you last update. Is drive E: available on the target server?

    Please provide the output from the following command from the source system (where this backup image was created):

    db2pd -d <db name> -tablespaces

  10. #10
    Join Date
    Oct 2011
    Posts
    21
    Hi,

    A quick sum up on the situation:
    1. Machine A is running with RTC2.0.0.2 using DB2 9.5 as repository DB. It is a Windows 2003 32 bit machine.
    2. Machine B is Windows 2008 R2 64 bit running with CLM3.0.1 using DB2 9.7 as repository DB.
    3. I need to migrate the Jazz source control to CLM3.0.1 in B machine. So I set out to restore a DB backup made in machine A to be restored in Machine B.
    4. In machine A, the tablesapce container is located in E:\DB2\NODE0002\JAZZ\content_tablespace. During restore process, machine A is inaccessible to machine B.
    5. The command used to restore is:
    restore database Jazz2 user db2admin using TP$dbadmin$96 from "C:\Users\TestPro\Backups\Remote DB Backups" taken at 20111018212239
    into JAZZ301 redirect;
    Then I was prompted the following message:
    "restore database Jazz2 user db2admin using from "C:\Users\TestPro\Backups\Remote DB Backups" taken at 20111018212239 into JAZZ97 redirect
    SQL1277W A redirected restore operation is being performed. Table space
    configuration can now be viewed and table spaces that do not use automatic
    storage can have their containers reconfigured.
    DB20000I The RESTORE DATABASE command completed successfully."
    6. So I run command:
    set tablespace containers for 3 using (FILE "C:\DB2\NODE0000\JAZZ301_TS" 40000 );
    7. Nothing came out from the Command Editor. The green triangle button turned grey. Clicking on the red square button has no response.
    8. error appeared in the db2diag.log exerted as follow:

    Thanks & Much Appreciated,
    Dixie


    2011-10-26-23.19.52.669000+660 E608496F1070 LEVEL: Warning
    PID : 5020 TID : 2416 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : JAZZ97
    APPHDL : 0-268 APPID: *LOCAL.DB2.111026121953
    AUTHID : DB2ADMIN
    EDUID : 2416 EDUNAME: db2agent (JAZZ97)
    FUNCTION: DB2 UDB, database utilities, sqludBMResponse, probe:310
    MESSAGE : SQL1277W A redirected restore operation is being performed. Table
    space configuration can now be viewed and table spaces that do not
    use automatic storage can have their containers reconfigured.
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: 1277 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqludBMR
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2011-10-26-23.25.19.778000+660 E609568F518 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage must be
    defined + Storage may be defined" on "table space" "DB2.JAZZ97
    .CONTENTTS".

    2011-10-26-23.25.20.825000+660 E610088F483 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .JAZZTMPSPACE".

    2011-10-26-23.25.21.653000+660 E610573F482 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .SYSCATSPACE".

    2011-10-26-23.25.22.497000+660 E611057F483 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .SYSTOOLSPACE".

    2011-10-26-23.25.23.325000+660 E611542F487 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .SYSTOOLSTMPSPACE".

    2011-10-26-23.25.24.153000+660 E612031F481 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .TEMPSPACE1".

    2011-10-26-23.25.24.981000+660 E612514F481 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Operational State"
    ("ts.ts_op_status") is in state "Restore pending + Storage may be
    defined" on "table space" "DB2.JAZZ97 .USERSPACE1".

    2011-10-26-23.25.25.840000+660 E612997F525 LEVEL: Warning
    PID : 6096 TID : 4840 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 4840
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10502W Health indicator "Table Space Container Operational State"
    ("tsc.tscont_op_status") is in state "Abnormal" on "table space
    container" "DB2.JAZZ97
    .CONTENTTS.E:\DB2\NODE0002\JAZZ\content_tablespace ".

  11. #11
    Join Date
    Oct 2011
    Posts
    21
    Quote Originally Posted by db2girl View Post
    Just noted you edited you last update. Is drive E: available on the target server?

    Please provide the output from the following command from the source system (where this backup image was created):

    db2pd -d <db name> -tablespaces
    Hi DB2Girl,

    Thanks for looking into this. Much appreciated.

    drive E: is not available on the target server. It is located in the source machine. For whatever reason, my restore keep trying write data into the old tablespace container path.

    Thanks,
    Dixie

  12. #12
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    You need to redefine tablespace containers during restore using REDIRECT / SET TABLESPACE CONTAINERS (for non-automatic storage tablespaces) and/or ON (for automatic storage tablespaces).

    Please see the last post here for more info:
    developerWorks : Information Management : IBM DB2 for Linux, Unix, and Windows Forum : Restore database to a different instance ...

  13. #13
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    Re-read your update. You did use SET TABLESPACE CONTAINERS during restore, but it got hung. Try redoing restore using DB2 Command Window.

    Also, check how your tablespaces are defined on the source system - automatic storage or not.

  14. #14
    Join Date
    Oct 2011
    Posts
    21
    Hi db2girl,

    Now I have a lot of other pressing problem, as show in db2diag.log
    What should I do?

    I am a Java developer happended to be responsible to upgrade ibm Team Concert from 2.0.0.2 to 3.0.1 and run into mountains of db2 trouble. There is no db2 admin in my company to help me out. Thanks for all your help.



    Thanks,
    Dixie

    2011-10-27-08.43.32.313000+660 E896188F636 LEVEL: Error
    PID : 6024 TID : 3724 PROC : db2fmp64.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 3724
    FUNCTION: DB2 UDB, Health Monitor, HealthIndicator::update, probe:500
    MESSAGE : ADM10500E Health indicator "Log Filesystem Utilization"
    ("db.log_fs_util") breached the "upper" alarm threshold of "85 %"
    with value "94 %" on "database" "DB2.QM ". Calculation:
    "((os.fs_used/os.fs_total)*100);" = "((59224264704 / 62807601152) *
    100)" = "94 %". History (Timestamp, Value, Formula): "()"

  15. #15
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,368
    This message indicates that the drive where your db logs are stored has ~3.3 GB of free space. Check db cfg for this db (db2 get db cfg for db qm) for location of db logs. Possibly, they're stored on the same drive as your tablespace containers. Free up some space on this drive or just ignore the message if you think the amount of free space is sufficient for now. You can also stop the message by disabling health monitor.

Tags for this Thread

Posting Permissions

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