Skip to Content
author's profile photo Former Member
Former Member

FAILARCHPATH parameter type - dynamic or not?

DB2 documentation says FAILARCHPATH is "Configurable Online" (version 8 & 9) but in my tests I find it requires the database to be recycled. We are using DB2 v8 FP12 from SAP.

FP12 is supposed to include the fix "IY82855: UPDATE FAILARCHPATH MAY RETURN SUCCESS, BUT NOT TAKE EFFECT ALL APPLICATIONS DISCONNECT".

Does anyone know if FP12 from SAP does actually include the fix or if there are other problems with FAILARCHPATH.

I would leave FAILARCHPATH set permanently except that it generates a ton of useless log entries, which I find annoying to scan through. I would therefore rather set it dynamically when I need to.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Dec 19, 2006 at 07:30 PM

    Hi Chris, could be another phenomenon:

    I had this once with auto_runstats, which also should be configurable online according to the docu, but returned SQL1363W (activation after all applications disconnect).

    This occured when running the "update db cfg .." statement against an activated database (=running SAP system) without issuing an explicit "db2 connect" before the "db2 update db .." statement.

    Just give it a try:

    (1) db2 connect

    (2) <your update db statement>

    (3) db2 terminate

    Hope this already solves your problem.

    Hans-Juergen

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      We are on FP12. I have opened a PMR with IBM myself and they are looking at it (I hope).

      It seems to me there is some kind of bug in parsing the new parameter. Notice in the error message that the failed archive path is incorrect, but after restarting the database the path is correct and the archive is successful.

      > db2 connect to prj

      > db2 update db cfg for prj using FAILARCHPATH /db2/PRJ/log_archive/failed/

      DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.

      > db2 archive log for db prj

      ...

      2006-12-19-12.37.17.797550-420 I666153A408 LEVEL: Error

      PID : 311462 TID : 1 PROC : db2logmgr (PRJ) 0

      INSTANCE: db2prj NODE : 000

      FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3160

      MESSAGE : Failed to archive log file S0016522.LOG to db2prj/PRJ/NODE0000/C0000012/ from /db2/PRJ/log_dir/NODE0000/ with rc = -2029060079.

      ...

      > db2 terminate

      > db2 deactivate db prj

      > db2 activate db prj

      ....

      2006-12-19-13.06.47.283016-420 I1102343A420 LEVEL: Warning

      PID : 377032 TID : 1 PROC : db2logmgr (PRJ) 0

      INSTANCE: db2prj NODE : 000

      FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogFile, probe:3180

      MESSAGE : Successfully archived log file S0016522.LOG to /db2/PRJ/log_archive/failed/db2prj/PRJ/NODE0000/C0000012/ from

      /db2/PRJ/log_dir/NODE0000/.

      ....

      Cheers,

      Chris

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.