Page 1 of 2 12 LastLast
Results 1 to 15 of 17
  1. #1
    Join Date
    Mar 2014
    Posts
    26

    Unanswered: Log archive failed with rc 8

    Hi All
    im newbie in db2 especially on reading db2 log. i have have an issue where when i check on db2diag log have and error as below.
    what causes this error ? before this i check database was stopped. now, i bring up back databases .
    can someone help me on this.

    DB -DB2v 8.1
    OS - AIX 5.3




    2016-09-21-08.08.27.486974+480 I3356C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

    2016-09-21-08.08.34.669185+480 I3666C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030422.LOG to USEREXIT from
    prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.08.34.669316+480 I4050C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

    2016-09-21-08.08.41.751553+480 I4360C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030423.LOG to USEREXIT from
    /prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.08.41.751699+480 I4744C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

    2016-09-21-08.08.48.740675+480 I5054C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030424.LOG to USEREXIT from
    prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.08.48.740803+480 I5438C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

    2016-09-21-08.08.55.823186+480 I5748C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030421.LOG to USEREXIT from
    prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.08.55.823316+480 I6132C371 LEVEL: Warning
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgRetryFailedArchive, probe:4780
    MESSAGE : Still unable to archive log file 30421 due to rc 8 for LOGARCHMETH1
    using method 4 and target .

    2016-09-21-08.09.02.094483+480 I6504C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030425.LOG to USEREXIT from
    /prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.09.02.094611+480 I6888C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

    2016-09-21-08.09.09.442383+480 I7198C383 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160
    MESSAGE : Failed to archive log file S0030426.LOG to USEREXIT from
    /prdinst1/NODE0000/SQL00001/SQLOGDIR/ with rc = 8.

    2016-09-21-08.09.09.442516+480 I7582C309 LEVEL: Error
    PID : 778378 TID : 1 PROC : db2logmgr
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchivePendingLogs, probe:1500
    MESSAGE : Log archive failed with rc 8 for LOGARCHMETH1.

  2. #2
    Join Date
    Jul 2016
    Location
    Germany
    Posts
    32
    Provided Answers: 2

    sentimental journey

    Hi amynarco,

    the good old days...

    the 20th Century, when there where tape stations
    and operators manually mounting tapes...

    and USEREXIT's requesting Operator intervention...

    please check your LOGARCHMETH1 :

    db2 get db cfg for <your database> | grep -i LOGARCHMETH1

    Good luck
    db2dp

  3. #3
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Your USEREXIT is failing for some reason, but the reason for it failing is not recorded in db2diag. Instead you must find your user exit program and discover where it writes its diagnostics (if it has any). Also you should determine where the USEREXIT sends the archived logs. If it sends the archive to tape (for example via TSM) then the client-library for the tape-subsystem will also have diagnostics in a separate location so you can check those.
    So your issue is not caused by DB2, it is instead caused by whatever system is the target for archived sent by your USEREXIT program.

    To find your userexit, use:
    db2 get db cfg for $your-database-name
    and pipe the output to grep USEREXIT
    Last edited by db2mor; 09-21-16 at 03:27.

  4. #4
    Join Date
    Mar 2014
    Posts
    26

    log archive failed with rc 8

    hi db2bp

    As below , setting for LOGRARCH and log file location
    Path to log files = /prdinst1/NODE0000/SQL00001/SQLOGDIR/
    First log archive method (LOGARCHMETH1) = USEREXIT

    i check from log file folder, still have yesterday log and today log. Usually this log purged into disk when backup completed right ?


    Thank you

  5. #5
    Join Date
    Mar 2014
    Posts
    26
    hi db2nor

    is it means USEREXIT program refer to Netbackup ( example ) ?

    correct command, as below ?
    db2 get db cfg for XX_DB | USEREXIT


    thank you

  6. #6
    Join Date
    Jul 2016
    Location
    Moscow
    Posts
    108
    Provided Answers: 13
    Hi,

    RC=8 from USEREXIT means:
    #define RC_OPATTN 8 /* operator/user attention required*/

    Look at the Automating log file archiving and retrieval with user exit programs topic.
    There is a couple of sample USEREXIT programs: ~db2instonwer/sqllib/samples/c/db2uext2.c*
    Probably you have some customized program based on one of these examples. So, you must look into the logic of your program, try to find some logs of it (if any) with more details on a root cause.
    Regards,
    Mark.

  7. #7
    Join Date
    Jul 2016
    Location
    Germany
    Posts
    32
    Provided Answers: 2

    sentimental journey

    Hi amynarco,

    Usually this log purged into disk when backup completed right ? Right !

    db2mor asked for db2 get db cfg for <your database> | grep USEREXIT

    You already answered this : First log archive method (LOGARCHMETH1) = USEREXIT

    We all seem to agree that you have to check your USEREXIT program.

    There seems to be a problem with your USEREXITs target system.

    Good luck
    db2dp

  8. #8
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    If your USEREXIT is sending archived-log files to NetBackup, then you should ask your NetBackup support person for help. But you first should verify exactly what the Userexit program is doing. There may be documentation or source-code.

  9. #9
    Join Date
    Mar 2014
    Posts
    26
    Quote Originally Posted by db2mor View Post
    If your USEREXIT is sending archived-log files to NetBackup, then you should ask your NetBackup support person for help. But you first should verify exactly what the Userexit program is doing. There may be documentation or source-code.
    hi db2mor
    how to confirm activity on USEREXIT program ?
    yes, userexit sending archived log file to netbackup, now verified have some delay purged archive log to netbackup .


    thank you

  10. #10
    Join Date
    Mar 2014
    Posts
    26
    Quote Originally Posted by db2dp View Post
    Hi amynarco,

    Usually this log purged into disk when backup completed right ? Right !

    db2mor asked for db2 get db cfg for <your database> | grep USEREXIT

    You already answered this : First log archive method (LOGARCHMETH1) = USEREXIT

    We all seem to agree that you have to check your USEREXIT program.

    There seems to be a problem with your USEREXITs target system.

    Good luck
    db2dp


    hi db2bp
    how to confirm an activity from USEREXIT program / target system ?
    yes, log purged into media tape when bakcup completed.


    Thank you

  11. #11
    Join Date
    Mar 2014
    Posts
    26
    Hi db2bp and db2nor


    from ps -ef USEREXIT program doing archiving , as below

    db2uext2 -OSAIX -RLSQL08021 -RQARCHIVE -DBXX_DB -NNNODE0000 -LP/xxx/prdinst1/NODE0000/SQL00001/SQLOGDIR/ -LNS0030603.LOG

    now , i can see log successfully archive no rc 9 error found form latest diag.log . actually what causes this issue ?


    from diag.log found few warning, is it normal ?

    2016-09-22-11.12.46.281016+480 I132309C293 LEVEL: Warning
    PID : 1319048 TID : 1 PROC : db2loggr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
    MESSAGE : DB2 is waiting for log files to be archived.

    2016-09-22-11.12.57.416706+480 I132603C377 LEVEL: Warning
    PID : 848024 TID : 1 PROC : db2logmgr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Successfully archived log file S0030584.LOG to USEREXIT from
    /DB/prdinst1/NODE0000/SQL00001/SQLOGDIR/.

    2016-09-22-11.12.57.553827+480 I132981C323 LEVEL: Warning
    PID : 766090 TID : 1 PROC : db2loggr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgLoggrInitDelOldLog, probe:1440
    MESSAGE : Cleaning up logs from RenameArchNum 30584 to delLimit 30585

    2016-09-22-11.12.57.782289+480 I133305C334 LEVEL: Warning
    PID : 766090 TID : 1 PROC : db2loggr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1390
    MESSAGE : ExtNum 31088, state 401, baselsn 0000003AEF864000 nextlsn
    0000003AEF86424C

    2016-09-22-11.13.52.786622+480 I133640C293 LEVEL: Warning
    PID : 766090 TID : 1 PROC : db2loggr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpghck, probe:1780
    MESSAGE : DB2 is waiting for log files to be archived.

    2016-09-22-11.14.06.042182+480 I133934C377 LEVEL: Warning
    PID : 970886 TID : 1 PROC : db2logmgr (CC_DB)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3180
    MESSAGE : Successfully archived log file S0030585.LOG to USEREXIT from
    /XXX/prdinst1/NODE0000/SQL00001/SQLOGDIR/.

    2016-09-22-11.14.06.183681+480 I134312C323 LEVEL: Warning
    PID : 766092 TID : 1 PROC : db2loggr (XXX)
    INSTANCE: prdinst1 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgLoggrInitDelOldLog, probe:1440
    MESSAGE : Cleaning up logs from RenameArchNum 30585 to delLimit 30586


    Thank you
    Last edited by amynarco; 09-22-16 at 00:44.

  12. #12
    Join Date
    Sep 2016
    Location
    11 Thai ha, Hanoi, Vietnam 100000
    Posts
    1
    you first should verify exactly what the User Exit program is doing

  13. #13
    Join Date
    Mar 2014
    Posts
    26
    how to verify User Exit program is doing ?

  14. #14
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    As previously advised, find the source-code or the documentation for your user-exit - the user exit was written *for your site* , that is what is meant by "user exit" - written by or for the customer(=DB2 customer). Search for db2uext2.c or db2uext2.cpp or db2uext2.sqc etc on your systems , or on the intranet at your site.

    If the above is beyond your skill level, did you follow up with NetBackup people? Did you check if this installation uses the NetBackup-Agent-For-DB2 or not ?

  15. #15
    Join Date
    Mar 2014
    Posts
    26
    Hi All

    Im understand now after follow up and check with net backup guy and check on database.
    to summarize this, when netbackup job disable. dbdiag log trace and error rc8 . But, when netbackup enable no error related with rc8. That mean now netbackup open 24H windows to trigger log backup suppose have schedule time for this and i think this ridiculous.this might impact on db performance, right ? if media tape full, or backup pending. Correct me if im wrong .

    but, im confuse, is it correct by using USSEREXIT parameter log in folder queue before been archive into media ?
    and when ps -ef |grep db2 i found that have process db2uext2 running archive the log. is it this process trigger by netbackup to archive log and save archvied log into media tape ?

    im verify appreciate with all feedback and advice


    thank you
    amy

Tags for this Thread

Posting Permissions

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