Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2002
    Location
    Hamilton
    Posts
    150

    Unanswered: DB2 system tables

    DB2 V7.2 on AIX

    For some reason one of our database backups failed on friday night because it was no longer enabled for online backups. This has been working for months on end and all of a sudden on friday it went bump in the night. I checked the system log for any su's to the id and the only id that did so was root (done during the backup process via a script).

    What system table can I query to find out when the configuration was changed? It has been changed back to fix the problem but I dont' know how it was changed in the first place.

    Thanks

    Mark

  2. #2
    Join Date
    Mar 2004
    Posts
    448
    can you post the message in db2diag.log file.
    did you check the history file.

    regards,

    mujeeb

  3. #3
    Join Date
    Feb 2002
    Location
    Hamilton
    Posts
    150
    This is from the db2diag.log file with the pertinent information

    Jul 9 22:30:32 archa99 DB2[48650]: DB2 (bnspa1.000) database_utilities sqlubIn
    itProcess reports: probe id 50 with error -2413 and alert num 0
    Jul 9 22:30:32 archa99 DB2[48650]: data: fffff693
    .
    Jul 9 22:30:32 archa99 root: BNSDB2_ALERT: BNSDB2 Online Backup Failure for DB
    - aridb to /archive/proda/symcor_custom/bnsdb2backup


    and the history file is fine because it shows all the successful online backups

    Mark

  4. #4
    Join Date
    Mar 2004
    Posts
    448
    The error is 2413 offcourse 'negative'

    so

    SQL2413N Online backup is not allowed
    because either logretain or
    userexit for roll-forward is not
    activated, or a backup pending
    condition is in effect for the
    database.
    Explanation: Online backup cannot be
    performed while the database is not logging for
    forward recovery as forward recovery will be
    required at restore time. Forward recovery is
    placed into effect by setting either the database
    configuration logretain parameter or the userexit
    parameter, and then performing an offline
    backup of the database.

    User Response: Execute an offline backup or
    reconfigure the database for roll-forward
    recovery and issue an offline backup so that
    subsequent online backups will be allowed.

    check if the logretain or userexit is on

    db2 get db cfg for <database_name>|grep -i LOG

    You will also find the state of the database from the above statement.

    try to connect to database(will give you an error, if the database is inconsistent mode).


    regards,

    mujeeb

  5. #5
    Join Date
    Feb 2002
    Location
    Hamilton
    Posts
    150
    i know what the problem is, I already fixed it but the problem is we had the database configured for online backups, it was working for 6 months and all of sudden on friday night it didn't work with the message you stated.

    Nothing was changed and I can't find any evidence of any tampering with the ID on the AIX server.

    I wanted to know if there was a way of querying the system tables to see when/what time the db cfg could have been changed to turn off the ability to perform online backups (like i stated above, I have already corrected the problem but my real dilemna is how do i find out when it was changed sometime after thursday night's backup (successful) and before friday nights (failed)

    thanks

    mark

Posting Permissions

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