Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2010
    Posts
    3

    Question Unanswered: Archive logs backup do not start automatically

    Db2 9.1
    My database name is =muk
    Database alias name is =mukl

    I am using backup software and I configured database backup using alias name mukl

    The online backup is working but archive logs do not start after the online backup.

    My question is can i use Alias name for database backup or do I need to use database name for backup so that my archive logs get started
    USEREXIT is set for database muk

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    How do you know your logs are not being archived? Are there any messages in the db2diag.log file? What are your database configuration settings?


    Andy

  3. #3
    Join Date
    Apr 2010
    Posts
    3
    can alias name be used for archive logs backup.
    I use backup software archive log bakcup should started automatically once online backup is completed.

    I have configured online backup using Alias name mukl and not the database name muk

    Archive logs are there and useexit

    ath to log files = /db2/muk/logs_dir1/NODE0000/
    Overflow log path (OVERFLOWLOGPATH) =
    Mirror log path (MIRRORLOGPATH) =
    First active log file = S0008769.LOG
    Block log on disk full (BLK_LOG_DSK_FUL) = YES
    Percent max primary log space by transaction (MAX_LOG) = 0
    Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0

    Group commit count (MINCOMMIT) = 1
    Percent log file reclaimed before soft chckpt (SOFTMAX) = 300
    Log retain for recovery enabled (LOGRETAIN) = RECOVERY
    User exit for logging enabled (USEREXIT) = ON

    HADR database role = STANDARD
    HADR local host name (HADR_LOCAL_HOST) =
    HADR local service name (HADR_LOCAL_SVC) =
    HADR remote host name (HADR_REMOTE_HOST) =
    HADR remote service name (HADR_REMOTE_SVC) =
    HADR instance name of remote server (HADR_REMOTE_INST) =
    HADR timeout value (HADR_TIMEOUT) = 120
    HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC

    First log archive method (LOGARCHMETH1) = USEREXIT
    Options for logarchmeth1 (LOGARCHOPT1) =
    Second log archive method (LOGARCHMETH2) = OFF

  4. #4
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    What do you mean by "archive logs backup"?

    When you set LOGARCHMETH1 to "userexit", you must place a userexit routine in the appropriate DB2 directory for this to work properly.

    I assume you are trying to have your logs archived to your backup software. To do this, the backup software must supply you with the userexit routine to do this.

    Are there any messages in the db2diag.log file about archiving logs (whether they are successful or not)?

    Andy

  5. #5
    Join Date
    Apr 2010
    Posts
    3
    I found the solution.
    We need to configure archuve logs backup with database name and Alias name.
    I used muk for archive logs backup and it worked.

Posting Permissions

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