DB2 prune transaction logs

Sort:
You are not authorized to post a reply.
Author
Messages
Phil Romov
Veteran Member
Posts: 44
Veteran Member
    I'm trying to clean up 2 gigs (sometimes more) worth of DB2 SQLOGDIR transaction logs (or is it just "logs"? not sure what db2 calls them) which has been one of the bigger nuisances of DB2

    Consulting db2 docs ( http://publib.boulder.ibm...2Fdoc%2Fr0001992.htm ), I've tried the prune (including with force and delete) command with no results.  The list history command shows no logs, but gigs worth of physical files are still there.

    My only conclusion would be that you have to manually relocate (and then delete) these files to free up disk space (although, again, I would think the "and delete" option is supposed to do that) but in the past this has caused db2 to catastrophically stop working (moving the files back makes everything work again)

    1) Does anyone have experience recovering the disk space these transaction logs take when they are no longer required?  (e.g after data reload)
    2) A lot of online advice goes along the lines of committing more often, etc, is there a way to do so when using lawson's impexp?
    3) Finally, does anyone know how to either a) turn off these logs during data lods or b) configure these logs to grow always (and never report "transaction log is full" even though plenty of disk space remains)?  Note: my primary and secondary parameters are already maxed out

    Thanks
    Phil
    You are not authorized to post a reply.