Results 1 to 5 of 5
  1. #1
    Join Date
    Jan 2003
    Posts
    1,605

    Unanswered: Still unable to archive log file 109840 ... LOGARCHMETH1 using method 1 and target /p

    Hi,
    on DB2 v9.5 Enterprise on Linux I have tons of errors in db2diag.log file like:

    "Still unable to archive log file 109840 due to rc -2029060079 for
    LOGARCHMETH1 using method 1 and target /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/."

    There are actually blocks of messages that are constantly repeating. See bellow db2diag.log what messages are reappearing.

    Regards

    Code:
    2009-08-16-04.02.14.911859+120 E2501292729A607    LEVEL: Error
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3160
    MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
              DIA8514C An invalid file path, "", was specified.
    DATA #1 : <preformatted>
    Failed to archive log file S0109840.LOG to /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/ from /db2/db2baza/db2inst1/NODE00
    00/SQL00001/SQLOGDIR/.
    
    2009-08-16-04.02.14.912115+120 I2501293337A502    LEVEL: Warning
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgRetryFailedArchive, probe:4780
    MESSAGE : Still unable to archive log file 109840 due to rc -2029060079 for
              LOGARCHMETH1 using method 1 and target
              /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/.
    
    2009-08-16-04.02.33.999148+120 I2501293840A363    LEVEL: Warning
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0109840.LOG.
    
    2009-08-16-04.02.34.232296+120 I2501294204A516    LEVEL: Error
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogDisk, probe:2530
    RETCODE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
              DIA8514C An invalid file path,
              "/db2/db2baza/db2inst1/NODE0000/SQL00001/SQLOGDIR/S0109840.LOG", was
              specified.
    
    2009-08-16-04.02.37.038844+120 E2501294721A507    LEVEL: Warning
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
    MESSAGE : ADM1848W  Failed to archive log file "S0109840.LOG" to
              "/db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/" from
              "/db2/db2baza/db2inst1/NODE0000/SQL00001/SQLOGDIR/".
    
    2009-08-16-04.02.37.075363+120 E2501295229A607    LEVEL: Error
    PID     : 3576                 TID  : 2199383959888PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 467                  EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3160
    MESSAGE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
              DIA8514C An invalid file path, "", was specified.
    DATA #1 : <preformatted>
    Failed to archive log file S0109840.LOG to /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/ from /db2/db2baza/db2inst1/NODE00
    00/SQL00001/SQLOGDIR/.

    db2 get db cfg for <db_name> | grep LOG
    Code:
     Catalog cache size (4KB)              (CATALOGCACHE_SZ) = 812
     Log buffer size (4KB)                        (LOGBUFSZ) = 124
     Log file size (4KB)                         (LOGFILSIZ) = 1024
     Number of primary log files                (LOGPRIMARY) = 10
     Number of secondary log files               (LOGSECOND) = -1
     Changed path to log files                  (NEWLOGPATH) =
     Path to log files                                       = /db2/db2baza/db2inst1/NODE0000/SQL00001/SQLOGDIR/
     Overflow log path                     (OVERFLOWLOGPATH) =
     Mirror log path                         (MIRRORLOGPATH) =
     First active log file                                   = S0110554.LOG
     Block log on disk full                (BLK_LOG_DSK_FUL) = NO
     Percent max primary log space by transaction  (MAX_LOG) = 0
     Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
     Log retain for recovery enabled             (LOGRETAIN) = OFF
     First log archive method                 (LOGARCHMETH1) = DISK:/db2/on_line_logs/
     Options for logarchmeth1                  (LOGARCHOPT1) =
     Second log archive method                (LOGARCHMETH2) = OFF
     Options for logarchmeth2                  (LOGARCHOPT2) =
     Log pages during index build            (LOGINDEXBUILD) = OFF
    LOGARCHMETH1=DISK:/db2/on_line_logs/
    Executing: cd /db2/on_line_logs/
    works fine, so directory exists.

    Any idea why DB2 can't archive files to path /db2/on_line_logs/?
    Regards

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    There are three possibilities that I can think of:

    1) The disk is full
    2) the directory does not exist
    3) the permissions are wrong for the directory.

    Andy

  3. #3
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    I have checked:
    1. disk is not full, df command shows it is 62 GB of free disk space, which is 57% of disk size. Database size is 15 GB (backup file size), so disk should not be the problem.
    2. directory /db2/on_line_logs exists.
    cd /db2/on_line_logs works fine
    3. File prermissions
    cd /db2
    ls -l
    drwxr-xr-x 2 db2inst1 db2iadm1 4096 2009-08-18 04:21 archive
    drwxr-xr-x 3 db2inst1 db2iadm1 4096 2009-01-15 18:33 on_line_logs

    There are two dirs /db2/archive where backups are done without any problems at all. And /db2/on_line_logs where LOGARCHMETH1 saves file has the same permissions.

    By the way, I have v9.5 fixpack 2a installed. Is there maybe some kind of bug that I am not aware of?
    Regards

  4. #4
    Join Date
    May 2005
    Location
    Bangalore, India
    Posts
    35
    Did you try any other name like /db2/onlinelogs

    Sometimes changing the name works, when there are no obvious reasons for failures

  5. #5
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    I haven't try to change the dir name for LOGARCHMETH1, so this parameter is still DISK:/db2/on_line_logs/

    But I now have created directory by command:
    mkdir -p /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/

    Now errors stopped appearing, but instead Warning are displayed like:
    Code:
    2009-08-18-08.25.49.305630+120 I2531362539A363    LEVEL: Warning
    PID     : 3210                 TID  : 2199379765584PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 21                   EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3108
    MESSAGE : Started archive for log file S0110815.LOG.
    
    2009-08-18-08.25.49.419191+120 I2531362903A495    LEVEL: Warning
    PID     : 3210                 TID  : 2199379765584PROC : db2sysc 0
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 21                   EDUNAME: db2logmgr (ISQ) 0
    FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Completed archive for log file S0110815.LOG to
              /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/ from
              /db2/db2baza/db2inst1/NODE0000/SQL00001/SQLOGDIR/.
    Don't quite understand why I needed to create this directory and also don't understand why are there still Warnings if file is successfully written.

    I have checked there are 78 log files written to above created directory.
    Command: ls -l /db2/on_line_logs/db2inst1/ISQ/NODE0000/C0000005/ | wc -l
    returns 78.

    Why Warning?

    P.S. dbm cfg parameter DIAGLEVEL is set to: 3
    Regards

Posting Permissions

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