Results 1 to 2 of 2
  1. #1
    Join Date
    Jul 2004
    Posts
    2

    Unanswered: restoring the admin DB after a restore of DB.

    Dear all,

    We have a system on db2 7.2 / AIX 5.1 for SAP 4.6C database

    We have just restored our database from our TSM backup.

    The current state is:
    Rollforward Status

    Input database alias = EP1
    Number of nodes have returned status = 1

    Node number = 0
    Rollforward status = DB pending
    Next log file to be read = S0034826.LOG
    Log files processed = -
    Last committed transaction = 2004-07-07-17.00.16.000000

    My instructions say to rebuild the adminDB from the adminDB.xxxx.SAR file which i have extracted into a temp directory so that we may "brrestore" (extract the logs from tape) the logs files required for roll forward.

    when i do a db2 connect, the following error occurs:
    SQL1117N A connection to or activation of database "EP1" cannot be made
    because of ROLL-FORWARD PENDING. SQLSTATE=57019

    When rebuilding the adminDB from this command "sddb6ins -i", it finishes okay, but in the steps, the same step error occurs:
    "A connection to or activation of database "EP1" cannot be made
    because of ROLL-FORWARD PENDING."

    When applying this command:
    db2move ADMEP1 IMPORT -io INSERT_UPDATE
    i get these errors:
    ***** DB2MOVE *****

    Action: IMPORT

    Start time: Tue Jul 13 04:38:03 2004

    Server: DB2 Common Server V7.2.9

    IMPORT: -Rows read: 46185; -Rows committed: 46185; Table "SAPR3 "."DB6IDENTIFIER"
    IMPORT: -Rows read: 18; -Rows committed: 18; Table "SAPR3 "."DB6CONFIG"

    *** Table "SAPR3 "."DB6LOGFILE": ERROR -3306. Check message file tab3.msg!
    *** SQLCODE: -3306 - SQLSTATE:
    *** SQL3306N An SQL error "-964" occurred while inserting a row into the table.


    *** Table "SAPR3 "."DB6LOCATION": ERROR 3107. Check message file tab4.msg!
    *** SQL Warning! SQLCODE is 3107
    *** SQL3107W There is at least one warning message in the message file.


    *** Table "SAPR3 "."DB6BACKUP": ERROR 3107. Check message file tab5.msg!
    *** SQL Warning! SQLCODE is 3107
    *** SQL3107W There is at least one warning message in the message file.


    *** Table "SAPR3 "."DB6LFSTATE": ERROR -3005. Check message file tab6.msg!
    *** SQLCODE: -3005 - SQLSTATE:
    *** SQL3005N Processing was interrupted.

    In Summary, we want to roll forward after the restore, but its in a pending state and the Admin DB cannot be created because of this. But we need the adminDB to be restore as it contains the logs information we need to extract it from tape to allow us to roll forward.

    Does this make sense?

    Any ideas would be very appreciative.

    Cheers

  2. #2
    Join Date
    Jul 2004
    Posts
    2
    It's alright now, i have completed this issue.

    Cheers for the 2 viewings.

Posting Permissions

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