Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2007
    Posts
    265

    Unanswered: Restore of backup image hanging

    Hi,


    I have this command running on a 64-bit 8.1 FP 18 version of Db2 UDB on one of our linux systems --


    db2 restore db DBNAME from /home/db2inst1 taken at 20110403050002 logtarget /home/db2inst1/logs/ REPLACE EXISTING COMPRLIB /home/db2inst1/sqllib/lib/libdb2compr.so


    I left the command running overnight and noticed that even after many many hours it never came back to the prompt. I checked the db2diag.log file and see a bunch of severe errors with ZRC=0xFFFFFBA1... which says --- SQL1119N A connection to or activation of database "" cannot be made because a previous restore is incomplete.

    2011-04-20-13.48.40.422568-300 I7770058E360 LEVEL: Severe
    PID : 27121 TID : 140691328726784PROC : db2agent (DBNAME)
    INSTANCE: db2inst1 NODE : 000 DB : DBNAME
    APPHDL : 0-55 APPID: *LOCAL.nrg1.110420184844
    FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:10
    RETCODE : ZRC=0xFFFFFBA1=-1119

    2011-04-20-13.48.40.423159-300 I7770419E405 LEVEL: Error
    PID : 27038 TID : 140433740670720PROC : db2hmon
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 UDB, Health Monitor, HmonMainCB::refreshDbAutonomicSwitches, probe:160
    MESSAGE : Failed connecting to database "DBNAME "
    DATA #1 : Hexdump, 4 bytes
    0x00007FB94739EF0C : A1FB FFFF


    I don't have any programs connecting to the db so don't why it's complaining. Any idea how I can figure out what source is trying to connect to the db again and again? Thanks!!
    Last edited by db2user24; 04-20-11 at 15:51.

  2. #2
    Join Date
    Nov 2007
    Posts
    265
    Also, thought I'd mention that the backup image that I'm restoring from is a compressed image from one of our 32-bit systems.

  3. #3
    Join Date
    Nov 2007
    Posts
    265
    Also, after dropping the db and restarting, I saw these in db2diag.log -- what does this mean?

    2011-04-20-13.29.25.115288-300 E7734413E460 LEVEL: Warning (OS)
    PID : 27043 TID : 140691328726784PROC : db2agent (instance)
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-7 APPID: *LOCAL.db2inst1.110420182924
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    CALLED : OS, -, unspecified_system_function OSERR: EISDIR (21)
    DATA #1 : File name, 44 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0000.0

    2011-04-20-13.29.25.171008-300 E7734874E460 LEVEL: Warning (OS)
    PID : 27043 TID : 140691328726784PROC : db2agent (instance)
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-7 APPID: *LOCAL.db2inst1.110420182924
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    CALLED : OS, -, unspecified_system_function OSERR: EISDIR (21)
    DATA #1 : File name, 44 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0001.0

    2011-04-20-13.29.25.171189-300 E7735335E460 LEVEL: Warning (OS)
    PID : 27043 TID : 140691328726784PROC : db2agent (instance)
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-7 APPID: *LOCAL.db2inst1.110420182924
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    CALLED : OS, -, unspecified_system_function OSERR: EISDIR (21)
    DATA #1 : File name, 44 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SQLT0002.0

    2011-04-20-13.29.25.175725-300 E7735796E462 LEVEL: Warning (OS)
    PID : 27043 TID : 140691328726784PROC : db2agent (instance)
    INSTANCE: db2inst1 NODE : 000
    APPHDL : 0-7 APPID: *LOCAL.db2inst1.110420182924
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    CALLED : OS, -, unspecified_system_function OSERR: EISDIR (21)
    DATA #1 : File name, 46 bytes
    /home/db2inst1/db2inst1/NODE0000/SQL00001/SYSTOOLSPACE

Posting Permissions

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