Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2013
    Posts
    6

    Smile Unanswered: Cannot open database, losing connection

    Hi all,
    Newbie to db2 here. We have a database that was open, during backups, we think, when we lost power long enough for the ups to die. So we ended up with a hard crash. After that, we cannot get into the database. Anytime we attempt to enter it, it kills the connection between the application and the database. We can restart the connection, but when try to attach, the same thing happens.

    We created a new database and was able to restore data from backups for the main company into it. We are able to access this 2nd database with no problems. However, there is crucial data in the 1st database we do not have access to. I downloaded the Stellar Phoenix Recovery software. It gives me a 'Database Folder not found" error.

    This database is being accessed thru 3rd party software.
    I have the following info:
    Product Name: DB2 Express Edition
    License Type: Unwarranted
    Expiry date: Permanent
    Product identifier: db2exp
    Version Information: 9.1
    Max # CPU: 2
    Annotation: 6;<_uw>


    Instance "DB2" uses 32 bits and DB2 code release "SQL09012" "
    with identifier "01030107.

    Informational tokens are "DB@ v9.1.200.166", "special_17369", "WR21380_17639", and Fix Pack "2".


    If this is not sufficient information, please let me know what else to include.

    Thanks for helping!
    boss1b

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by boss1b View Post
    Anytime we attempt to enter it, it kills the connection between the application and the database. We can restart the connection, but when try to attach, the same thing happens.
    ...
    If this is not sufficient information, please let me know what else to include.
    You might want show the exact commands you're entering and the exact error message you are receiving.

    Also, delete or rename db2diag.log, attempt a connection, then post the new db2diag.log contents. Since you managed not to mention the server operating system, I can't tell you where to find it.
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Jan 2013
    Posts
    6
    Sorry, Op system is Windows Server 2003 R2 Std Ed. SP2.

    I will get the other data posted asap...

    Thanks!

Posting Permissions

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